Files
skills/skills/kvb-think-explain/SKILL.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 8b0c287ada fix(skills): trim 22 descriptions back under the listing budget
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>
2026-11-07 10:47:08 +00:00

27 lines
1.3 KiB
Markdown

---
name: kvb-think-explain
description: >
Explain on request what code does, how a mechanism works or why
components interact.
---
Explain the named code so an engineer who has never seen it can follow it:
1. Read the code and every collaborator it touches (callers, callees,
templates, configs) before explaining; never explain from the name alone.
Explore through the codebase-memory-mcp graph first (`search_graph`,
`trace_path`, `get_architecture`; the `kvb-agent-optimize` skill sets it
up), grep and read after.
2. Lead with the purpose in one sentence, then walk the flow in execution
order: inputs, transformations, side effects, outputs, with real files
and line references.
3. Make the interactions explicit: which component induces, triggers or
consumes which, and where the single source of truth lives. Point out
trip-wires (non-obvious ordering, escaping, caching, permission edges) in
the flow, not in an appendix.
4. Afterwards ask whether to persist a Mermaid diagram of the explained
mechanism under a `## Schema` heading in the README.md next to the
affected code (create the heading if missing, replace its previous
diagram if present). On approval, keep the diagram to the explained
scope: components as nodes, induction and data flow as labeled edges.