← ClaudeAtlas

which-skilllisted

Recommend which pau-skills skill, or sequence of skills, fits the user's situation, what the installed hooks already do, and which skills the user actually starts. Use when the user asks 'which skill should I use', 'what can these skills do', 'where do I start', 'is there a skill for this', 'help me pick', 'which skills do I actually use', or seems unsure how to approach a task.
paureis/pau-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill paureis/pau-skills
# Which Skill A router over every skill in this marketplace. Read the user's situation, pick the smallest set of skills that fits, and say in what order to run them. Do not run them yourself unless the user asks. ## How to answer 1. **Find out what the user is trying to do**, in one sentence. If it is unclear, ask one question, not five. 2. **Match it to a flow below.** Most work follows the main flow; problems come in through an on-ramp; a run that already went wrong goes to "Fix a run that went wrong". 3. **Recommend one starting skill** with its full invocation, then the next one or two after it. Explain in a line why each one fits this situation, not what it does in general. 4. **Check it is installed.** Skills are namespaced by plugin: `/verification:tdd` from the individual plugin, or `/pau-skills:tdd` from the bundle. If the skill's plugin is missing, give the install command (`claude plugin install <plugin>@pau-skills`). 5. **Mention a hook only if it matters here**, for example that `verify-before-done` will send the agent back if it claims to be done without running checks. Check the project's state only when it changes the answer, and mention it only then. For example: whether a `.claude/skills/verify-<app>/` skill exists matters when the question is about proving a change in the running app (without one, `verify-app` comes first); whether `PROJECT.md` and a contract exist matters when the question is about `methodology`. Do not inspect the repos