Kevin Veen-BirkenbachandClaude Opus 5.5
8b0c287ada
The skill listing stood at 1498 of 1500 words; the trimmed descriptions bring it to 1420, so the new kvb-check-ansible description fits without pushing others out. 🎯 Fix: 95 % 💥 Break: 1 % 💸 Cost: 99 % ⏱️ Time: 100 % 🛡️ Security: 100 % 🏆 Score: 95 🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
name, description
| name | description |
|---|---|
| kvb-help | List and explain every session skill. Trigger on "welche skills gibt es", "skill übersicht", or questions on what skills exist or do. |
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, compressing the description instead of pasting 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. kvb-git-commit-next → kvb-git-commit-no-verify → kvb-code-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.