AF codebase-explainer
Produce a durable onboarding artifact for a codebase — writes ONBOARDING.md covering a "read this first" minimum, system overview, dependency map, startup flow, auth flow, and 5-15 important files, every claim backed by file:line citations; refreshes an existing onboarding doc instead of rewriting it. Use this skill whenever the user says "explain this codebase", "explain the codebase", "onboard me", "give me a tour", "tour this repo", "what does this repo do", "where do I start", "codebase overview", "read this first", "I haven't looked at this in months", or "/codebase-explainer" — even if they don't name the skill.
Produce a durable onboarding artifact for a codebase — writes ONBOARDING.md covering a "read this first" minimum, system overview, dependency map, startup…
As a process F 39/100 · Will not run — References files that are not bundled: ../improve-codebase-architecture/SKILL.md, ../task-executor/SKILL.md, ../diagnose/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../improve-codebase-architecture/SKILL.md - warning
missing-refreference to a missing file: ../task-executor/SKILL.md - warning
missing-refreference to a missing file: ../diagnose/SKILL.md - warning
missing-refreference to a missing file: ../code-review/SKILL.md - warning
missing-refreference to a missing file: ../handoff/SKILL.md
Process rating: all ten parameters 39/100
- 0Tools and files. 5 referenced file(s) missing: ../improve-codebase-architecture/SKILL.md, ../task-executor/SKILL.md, ../diagnose/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 85Steps. 49 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2443 tokens
- 100Running it twice. Mutating operations check current state
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +3Description length 625: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.