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.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| kvb-skill-auto | Turn an instruction, correction or prompt pattern the operator repeats thrice into a skill, also when they say they keep repeating themselves. |
Its objective is the kvb-skill-tune skill's Objective section: a skill is
worth creating only when it cuts tokens or time and raises quality; judge
every candidate against its three axes and rules.
When the operator repeats the same kind of instruction, correction or prompt pattern (about three times, wording may vary):
- Finish the current task first; never interrupt work in progress.
- Then propose in one short paragraph: the observed pattern, a skill name, the trigger phrasing and what the skill would do. Ask whether to create it.
- On approval, persist it exactly as the
kvb-skill-tuneskill's Persistence section specifies: writeskills/<name>/SKILL.mdin the operator's skills repository (or the current project for project-specific behavior), then mirror the skill directory into~/.claude/skills/and~/.agents/skills/, plus the project's.claude/skills/and.agents/skills/when project-specific. Follow the local naming conventions; keep the skill thin and single-purpose, routing to an authoritative doc instead of duplicating it. Its deterministic steps become a script through thekvb-skill-compileskill, not prose. - No skill for one-off work, secrets, or repetition an existing skill already covers; when one almost fits, propose extending it instead.