DC skillify
The meta skill. Turn any raw feature into a properly-skilled, tested, resolvable unit of agent capability. Idempotent: running on an existing skill improves it (bug fix, new input, quality pass) instead of starting from scratch. Every skill declares an EVAL CONTRACT (its goal + skill-specific dimensions + hard-fails) so the cross-modal eval judges THIS skill's real purpose, not generic slop. Cross-modal eval runs BEFORE tests: 3 frontier models from different providers critique the output against the contract, you iterate to quality, THEN write/update tests that lock in the proven-good behavior. NO-REGRESSION LAW: any edit to a skill must score >= the previous iteration's eval — forward only, never back. For skills that back a scheduled job, an edit MUST re-run a representative task and eval it before shipping.
The meta skill. Turn any raw feature into a properly-skilled, tested, resolvable unit of agent capability. Idempotent: running on an existing skill improves…
As a process C 54/100 · Has gaps — References files that are not bundled: ../conventions/agent-operator-protocol.md, scripts/*.ts, scripts/<slug>.mjs
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 7152 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../conventions/agent-operator-protocol.md - warning
missing-refreference to a missing file: scripts/*.ts - warning
missing-refreference to a missing file: scripts/<slug>.mjs - note
frontmatter-keyunknown frontmatter key "eval_contract" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "mutating" - note
frontmatter-keyunknown frontmatter key "upstream"
Process rating: all ten parameters 54/100
- 0Tools and files. 3 referenced file(s) missing: ../conventions/agent-operator-protocol.md, scripts/*.ts, scripts/<slug>.mjs
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 7152 tokens
- 100Steps. 89 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 18 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (16 tags): a typed call is more reliable
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)
- +3Description length 822: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 38 headings
- +3Step-by-step instructions: 89 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 40.