SKILLEMALL.ai

BD diff-skill

Compare two versions of a skill's instructions to detect degradations and complexity increases. TRIGGER when: user asks to diff, compare, or review changes to a skill's markdown instructions. Asymmetric check — only regressions count. Additions, clarifications, and strengthenings are not degradations. Compares HEAD → working tree by default. Walks the full reachable file set from SKILL.md via markdown links. Produces a report file under docs/reviews/diff-skill/ and an inline summary.

serpro69/claude-toolbox Agent Skills author: serpro69 NOASSERTION 4 files body ≈ 463 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Compare two versions of a skill's instructions to detect degradations and complexity increases.

As a process D 39/100 · Unfinished process — References files that are not bundled: shared-capy-knowledge-protocol.md

AnalyzerData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: shared-capy-knowledge-protocol.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: diff-skill (serpro69/claude-toolbox)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: shared-capy-knowledge-protocol.md

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: shared-capy-knowledge-protocol.md
  • 0Tools and files. 1 referenced file(s) missing: shared-capy-knowledge-protocol.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 6 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 463 tokens
  • low The response is described with custom markup (4 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 488: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 6 items
  • +4Has examples (1 code blocks)

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