SKILLEMALL.ai
GitHub ↗ RU Sign in

BC SpecKit Coding Agent

A complete Spec-Driven Development (SDD) workflow that transforms how you build software. Start with an idea → Create specifications → Generate plans → Execute tasks. Powered by spec-kit and OpenCo...

modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 4 814 tokens Open the sourcegithub.com↗ analyzed 3 d ago

A complete Spec-Driven Development (SDD) workflow that transforms how you build software.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

ProcedureGitHubSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Running it twice w 4
30
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 12 mutating operations with no state check
  • 40Consistency. Frontmatter name (SpecKit Coding Agent) differs from the folder (speckit-coding-agent)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4814 tokens
  • 100Steps. 55 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Progress reporting. Reports progress
  • low 17 top-level sections: this looks like several domains in one skill

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

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