SKILLEMALL.ai

CD maintain-verification-skill

Keep a project's verification skill and product/agent access maps aligned with current source and real evidence. Use for /maintain-verification-skill, auditing the verify skill, or reconciling feature and agent access coverage.

The skillemall take

Promises to keep agent access maps in sync with source code and real evidence. In practice, it's a folder with audit instructions, no ready scripts.

Grade C with quality_score 68 signals trouble. Broken references mean instructions point to missing files. Process_score 45 reveals weak structure—either logic is scattered or steps are incomplete. No critical findings, but that's not reassuring; it suggests no tests ran rather than clean code. No model run, no sandbox test.

Install only if you'll fix broken links yourself and fill in logic gaps. For automated audit coverage, it's incomplete.

paperclipai/paperclip Agent Skills author: paperclipai MIT 3 files body ≈ 1 909 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Keep a project's verification skill and product/agent access maps aligned with current source and real evidence.

As a process D 45/100 · Unfinished process — References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
68
Run on models
none yet
Process rating
D
45/100
Unfinished process
References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../maps/README.md
  • warning missing-ref reference to a missing file: ../../../maps/feature-map/README.md
  • warning missing-ref reference to a missing file: ../../../maps/agent-access-map/README.md
  • warning missing-ref reference to a missing file: ../create-verification-skill/references/feature-map-example/
  • warning missing-ref reference to a missing file: scripts/check-maps.mjs
  • warning missing-ref reference to a missing file: scripts/check-maps.test.mjs
  • note edit-residue the text marks something as outdated (lines 74, 98): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
  • 0Tools and files. 6 referenced file(s) missing: ../../../maps/README.md, ../../../maps/feature-map/README.md, ../../../maps/agent-access-map/README.md
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 10 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1909 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 227: enough signal without eating the budget
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 10 items

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