SKILLEMALL.ai
GitHub ↗ RU Sign in

CC coverage-audit

Takes a curriculum framework and a statutory or accreditation requirement list; produces a coverage table, gap summary, and CSV showing which framework content covers each requirement and where gaps exist.

GarethManning/education-agent-skills Claude Code author: GarethManning 1 file body ≈ 3 692 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Takes a curriculum framework and a statutory or accreditation requirement list; produces a coverage table, gap summary, and CSV showing which framework…

As a process C 62/100 · Has gaps — weak spots: result and completion, failures and branches, progress reporting

AnalyzerData and analyticsWriting and documentsLearningtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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.
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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "effort"
  • note frontmatter-key unknown frontmatter key "skill_id"
  • note frontmatter-key unknown frontmatter key "skill_name"
  • note frontmatter-key unknown frontmatter key "domain"
  • note frontmatter-key unknown frontmatter key "evidence_strength"
  • note frontmatter-key unknown frontmatter key "evidence_sources"
  • note frontmatter-key unknown frontmatter key "input_schema"
  • note frontmatter-key unknown frontmatter key "output_schema"
  • note frontmatter-key unknown frontmatter key "chains_well_with"
  • note frontmatter-key unknown frontmatter key "teacher_time"

Process rating: all ten parameters 62/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 21 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3692 tokens
  • 100Running it twice. No mutating operations

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 205: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (2 code blocks)

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