help-me
Skill9 starsChanged 3 months agoMITView on GitHub
Natural language skill discovery — describe what you want to do and get matched to the right skill.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- sh4wty1/fassi-skillstheir own version, first seen Oct 9, 2026
- hereinthehive/kickstarttheir own version, first seen May 27, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- lalulali/vespyr★ 11same name
- hereinthehive/kickstart★ 4same name
- sh4wty1/fassi-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- ideateSkill
- lanesSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 107
If the user's intent is ambiguous, present options using AskUserQuestion with descriptions explaining the workflow implications of each …
- Distinctive: line 109
If no skill matches, suggest:
- Distinctive: line 117
Always explain WHY a skill is recommended, not just WHAT it does
- Distinctive: line 118
If the user describes a multi-step workflow, suggest the sequence (e.g., "/brainstorm → /ideate → /sprint-start → /story-cycle")
- Distinctive: line 119
Prefer specific skills over generic advice
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
help-me
Finding the right skill for: $ARGUMENTS
Intent Matching
Map the user's natural language request to the most appropriate skill(s):
Development Workflow
| User Says | Skill | Why |
| "start working", "begin", "new sprint" | /sprint-start | Creates a clean feature branch |
| "build", "implement", "add feature", "create", "deliver" | /story-cycle <description> | Full story delivery with TDD |
| "ship", "finish sprint", "create PR", "merge" | /sprint-end | Quality gates → PR → merge |
| "resume", "pick up where I left off", "continue" | /continue | Smart session resumption |
| "done for today", "end session", "save progress" | /handoff | Structured session handoff |
Planning & Design
| User Says | Skill | Why |
| "plan", "break down", "decompose", "stories" | /ideate <idea> | Decompose into backlog stories |
| "explore design", "compare approaches", "architect" | /brainstorm <idea> | Design exploration with alternatives |
| "research", "investigate", "compare technologies" | /research <topic> | Deep online research with citations |
Testing & Quality
| User Says | Skill | Why |
| "test plan", "prepare for testing" | /manual-test | Generate test plan from changes |
| "found a bug", "test feedback", "this doesn't work" | /testing-cycle <feedback> | Classify and process test findings |
| "run UAT", "acceptance test" | /UAT-cycle <test-case-id> | Execute formal UAT test case |
| "verify UAT logic", "sense check" | /claude-sense-check | Batch UAT code verification |
| "check code quality" | /code-quality | Complexity, duplication, patterns |
| "security review", "audit security" | /security-audit | CWE checklist, secrets, injection |
| "check architecture" | /architecture-check | Module boundaries, drift |
Debugging & Recovery
| User Says | Skill | Why |
| "debug", "error", "broken", "fix bug" | /debug-session <error> | 5-phase structured debugging |
| "fix issue", "fix #42", "github issue" | /fix-issue <number> | GitHub issue → TDD fix → PR |
| "undo", "revert", "go back", "start over" | /undo-work | Safe rollback (3 levels) |
Maintenance & Review
| User Says | Skill | Why |
| "health check", "is framework ok" | /doctor | Framework health validation |
| "weekly check", "maintenance" | /weekly-maintenance | Comprehensive weekly review |
| "retrospective", "what worked" | /retrospective | Sprint review with 4Ls |
| "backlog health", "review stories" | /backlog-review | Backlog quality analysis |
| "PR status", "check PRs" | /pr-status | Open PR status + actions |
| "upgrade framework" | /framework-upgrade | Update to newer version |
Utility
| User Says | Skill | Why |
| "commit" | /commit | Conventional commit |
| "parallel", "worktree", "multiple stories" | /parallel-work | Manage concurrent worktrees |
| "improve iteratively", "refine" | /refine-loop "<task>" | Iterative self-improvement |
| "optimize metric", "increase coverage" | /optimize "<goal>" | Metric-driven optimization |
| "create skill" | /skill-create | Generate tech-specific skills |
| "test a skill" | /skill-eval | Skill testing and comparison |
| "remove framework" | /uninstall | Clean framework removal |
| "status", "dashboard" | /dashboard | Sprint status overview |
Prompt Snippets (lightweight, no workflow)
| User Says | Skill | Why |
| "review security of file" | /review-security <file> | Quick security review |
| "explain this pattern" | /explain-pattern <pattern> | Code pattern explanation |
| "suggest tests for file" | /suggest-tests <file> | Test case suggestions |
Presentation
Based on the user's input, present the top 1-3 matching skills:
### Recommended
**`/skill-name <arguments>`** — [one-line description of what it does and when to use it]
### Also Consider
- `/other-skill` — [why this might also apply]If the user's intent is ambiguous, present options using AskUserQuestion with descriptions explaining the workflow implications of each choice.
If no skill matches, suggest:
- Direct conversation for simple questions
/brainstormfor complex open-ended exploration/researchfor information gathering
Rules
- This skill is READ-ONLY — it recommends, it doesn't execute
- Always explain WHY a skill is recommended, not just WHAT it does
- If the user describes a multi-step workflow, suggest the sequence (e.g., "/brainstorm → /ideate → /sprint-start → /story-cycle")
- Prefer specific skills over generic advice
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

