SKILLEMALL.ai

CD ccsn-no-comments

Use in the cc-safety-net repo when `bun run lint:comments` or `bun run check` reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and before writing a code comment there. Moves what each comment says into code, a test, or the PR description instead of deleting it and losing it.

kenryu42/cc-safety-net Agent Skills author: kenryu42 2 files body ≈ 819 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Use in the cc-safety-net repo when bun run lint:comments or bun run check reports a comment, a stale comment-allowlist entry, or a file it cannot parse, and…

As a process D 37/100 · Unfinished process — References files that are not bundled: scripts/comment-allowlist.json, scripts/check-comments.ts

AnalyzerSoftware developmentData and analyticstype 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
D
37/100
Unfinished process
References files that are not bundled: scripts/comment-allowlist.json, scripts/check-comments.ts
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/comment-allowlist.json
  • warning missing-ref reference to a missing file: scripts/check-comments.ts

Process rating: all ten parameters 37/100

Will not run. References files that are not bundled: scripts/comment-allowlist.json, scripts/check-comments.ts
  • 0Tools and files. 2 referenced file(s) missing: scripts/comment-allowlist.json, scripts/check-comments.ts
  • 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
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 819 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • high The skill tells the model to perform an irreversible action with no human approval
  • low The response is described with custom markup (8 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 305: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 11 items

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