91b9845c1b
comments-clean purges explanatory comments before every operator-requested stage or commit and penalizes own violations into persistent memory; commit-no-verify commits the exact staging index with hooks skipped, the invocation itself being the per-commit authorization; commit-next chains both and stages the next logical bundle with an explain and confidence briefing; explain walks code and its collaborators in execution order and offers a Mermaid schema in the affected README; help-skills lists every project, global and plugin skill with triggers and composition. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description
| name | description |
|---|---|
| help-skills | List and explain every skill available in the current session. Trigger on /help-skills, "welche skills gibt es", "skill übersicht", or when the operator asks what skills exist or what a skill does. Portable across projects. |
Produce a one-shot overview of every skill the session can invoke:
- Sources, in this order: the session's available-skills listing, the
project's own skills (
skills/and.claude/skills/in the repo), the user-global skills (~/.claude/skills/), and plugin-provided skills. Deduplicate by name; note when a project skill shadows a global one. - Output one table per origin (project, global, plugin): skill name, trigger (slash command or phrasing), one-line purpose in your own words — compress the description, do not paste it.
- When the operator names a specific skill or topic, explain only the matching skills in more depth: what they do, when they fire on their own, and how they compose (e.g. commit-next → commit-no-verify → comments-clean).
- End with the activation hint: project installers or
make installin the skills repository refresh the live copies; a restart loads renamed or new skills.