CD cline-pilot
Proxy Cline CLI coding tasks: dispatch, monitor background runs via hard evidence, relay decision points in a fixed format, verify against a checklist, and learn per-tag preferences over time.
Proxy Cline CLI coding tasks: dispatch, monitor background runs via hard evidence, relay decision points in a fixed format, verify against a checklist, and…
As a process D 43/100 · Unfinished process — References files that are not bundled: references/local-config.md, references/project-profiles.md, references/decision-log.md
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 192 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: references/local-config.md - warning
missing-refreference to a missing file: references/project-profiles.md - warning
missing-refreference to a missing file: references/decision-log.md - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_repo" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "license_source"
Process rating: all ten parameters 43/100
- 0Tools and files. 3 referenced file(s) missing: references/local-config.md, references/project-profiles.md, references/decision-log.md
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4845 tokens
- 85Steps. 102 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 24 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 4)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.