SKILLEMALL.ai

CF audit-tests

Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests, investigating implementation coupling or test-only production hooks, reviewing the value of proposed coverage, or auditing an entire subsystem. Use write-tests to implement the resulting test changes.

dzhng/jevgrep Agent Skills author: dzhng 1 file body ≈ 2 267 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Audit whether tests earn their maintenance cost and which suite owns each contract.

As a process F 33/100 · No process to follow — References files that are not bundled: ../write-tests/SKILL.md, ../review/SKILL.md

AnalyzerSoftware developmentData and analyticsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
F
33/100
No process to follow
References files that are not bundled: ../write-tests/SKILL.md, ../review/SKILL.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

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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../write-tests/SKILL.md
  • warning missing-ref reference to a missing file: ../review/SKILL.md

Process rating: all ten parameters 33/100

Will not run. References files that are not bundled: ../write-tests/SKILL.md, ../review/SKILL.md
  • 0Tools and files. 2 referenced file(s) missing: ../write-tests/SKILL.md, ../review/SKILL.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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2267 tokens

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 318: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 23 items

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