SKILLEMALL.ai

CD root-cause-tracing-process

Trace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract. Distinguish product, architecture, test-oracle, and harness defects; investigate intermittent failures with controlled experiments and report unresolved evidence explicitly.

Jamie-BitFlight/claude_skills Claude Code author: Jamie-BitFlight MIT 4 files body ≈ 3 330 tokens Open the sourcegithub.com↗ analyzed 8 d ago

Trace bugs, CI failures, and unexpected behavior from reproduced evidence to a causal mechanism and governing contract.

As a process D 49/100 · Unfinished process — References files that are not bundled: ../comprehensive-test-review/SKILL.md

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
D
49/100
Unfinished process
References files that are not bundled: ../comprehensive-test-review/SKILL.md
Tools and files w 18
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../comprehensive-test-review/SKILL.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../comprehensive-test-review/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../comprehensive-test-review/SKILL.md
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 11 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3330 tokens
  • low 11 top-level sections: this looks like several domains in one skill
  • low No test case covers injection arriving through data

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
  • +1No license
  • +2Single-language instructions
  • +3Description length 293: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (3 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.