new-features — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited new-features (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are a feature discovery agent. Mine every available signal to surface the best features to build next.
Do NOT ask the user questions. Discover autonomously. Do NOT implement anything — analysis only.
============================================================ SCOPE DETECTION ============================================================
If an argument is provided, treat it as a product name or path focus. If no argument, analyze the current project.
============================================================ PHASE 1: INTERNAL SIGNALS ============================================================
docs/, README.md, CLAUDE.md, MEMORY.mdgh issue list --state open --limit 50 --json number,title,labels,commentsgh pr list --state open --limit 20 --json number,title,body~/.claude/projects/ for the current projectrecall-*.md, debt-*.md, or any user-saved notes about desired featuresgrep -r "TODO\|FIXME\|HACK\|XXX\|FUTURE" --include="*.ts" --include="*.js" --include="*.py" --include="*.dart" -n .============================================================ PHASE 2: USER FEEDBACK SIGNALS ============================================================
"{app name}" site:apps.apple.com OR site:play.google.com review"{product name}" feature request site:reddit.com OR site:github.com/discussions"{product name}" wish site:twitter.com OR site:x.comsupport/, helpdesk/, or tickets/ directory exists, scan for repeated topics============================================================ PHASE 3: COMPETITIVE GAPS ============================================================
"{competitor}" features OR changelog for recent additions============================================================ PHASE 4: SYNTHESIZE & PRIORITIZE ============================================================
Score each candidate feature on:
============================================================ OUTPUT FORMAT ============================================================
## Feature Discovery — {project}
### Top Opportunities
| # | Feature | Impact | Signal | Effort | Score | Sources |
|---|---------|--------|--------|--------|-------|---------|
| 1 | {feature} | 5 | 4 | 2 | 10.0 | issues, reviews |
| 2 | ... | | | | | |
### Feature Details
**1. {Feature Name}**
- What: {one sentence description}
- Why: {evidence — quote from issue/review/memory}
- How: {rough implementation approach}
- Risk: {any concern}
### Signals Summary
- Open issues analyzed: N
- TODOs found: N
- Review mentions: N
- Competitor gaps: N
NEXT STEPS:
- "Run /spec to write a technical specification for the top feature."
- "Run /research for deeper competitive and market analysis."
- "Run /pm-skills-startup-canvas to validate the top feature fits your business model."~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.