AB skill-governance
Govern the real Claude Code and Codex Skill surface without losing cold capability. Use when users ask how many Skills are loaded, why the catalog is huge or descriptions are truncated, want only routers visible while gstack/Lark/IMA/UiPath stay on disk, or need to reconcile source/install/cache drift, `.agents/skills`/`.claude/skills`/legacy `.codex/skills`, loose or duplicate Skills, discovery policy, marketplace sources, suite migrations, superseded plugins, or old cache versions. Verifies the fresh host catalog and router resources; filesystem counts or completed cleanup are not success.
Govern the real Claude Code and Codex Skill surface without losing cold capability.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 46): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1721 tokens
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 598: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.