SKILLEMALL.ai
GitHub ↗ RU Sign in

BB developmental-progression-synthesis

Synthesise completed KUD charts into a developmental progression matrix and per-competency narrative sections. Use when you need a programme-level view of how knowledge, understanding, and performance develop across bands.

GarethManning/education-agent-skills Claude Code author: GarethManning 2 files body ≈ 6 918 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Synthesise completed KUD charts into a developmental progression matrix and per-competency narrative sections.

As a process B 68/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting

ProcedureSoftware developmentDesigntype 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
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
B
68/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 body-long SKILL.md body ≈ 6918 tokens (recommended < 5000); move details to references/
  • 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"

Process rating: all ten parameters 68/100

  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 6918 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 222: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 19 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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