DC create-hook
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
As a process C 54/100 · Has gaps — References files that are not bundled: /en/skills, /en/sub-agents, /en/plugins
The same skill appears in 1 more place: context-engineering-kit
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 ≈ 27560 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: /en/skills - warning
missing-refreference to a missing file: /en/sub-agents - warning
missing-refreference to a missing file: /en/plugins - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/memory - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/headless - warning
missing-refreference to a missing file: /en/hooks - warning
missing-refreference to a missing file: /en/hooks-guide - warning
missing-refreference to a missing file: /en/settings - warning
missing-refreference to a missing file: /en/settings - warning
missing-refreference to a missing file: /en/mcp - warning
missing-refreference to a missing file: /en/plugins-reference - warning
missing-refreference to a missing file: /en/hooks-guide - warning
missing-refreference to a missing file: /en/permissions - warning
missing-refreference to a missing file: /en/hooks-guide - warning
missing-refreference to a missing file: /en/hooks-guide - warning
missing-refreference to a missing file: /en/hooks-guide - note
edit-residuethe text marks something as outdated (lines 1682): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 0Tools and files. 26 referenced file(s) missing: /en/skills, /en/sub-agents, /en/plugins
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 27560 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 70Failures and branches. 13 branches
- 85Steps. 146 steps, 2 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 21 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (99 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 100: 120–800 characters recommended
- -5TODO / placeholder text left in the skill
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +4Structure: 109 headings
- +3Step-by-step instructions: 146 items
- +3Output format is stated explicitly
- +4Has examples (73 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 41.