SKILLEMALL.ai
GitHub ↗ RU Sign in

BB API Design Reviewer

The API Design Reviewer skill provides comprehensive analysis and review of API designs, focusing on REST conventions, best practices, and industry standards. This skill helps engineering teams bui...

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

The API Design Reviewer skill provides comprehensive analysis and review of API designs, focusing on REST conventions, best practices, and industry standards.

As a process B 70/100 · Nearly there — weak spots: when it triggers, consistency, progress reporting

IntegrationSoftware developmentInfrastructureWriting and documentstype 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
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
B
70/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Consistency w 8
40
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: 10. 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 70/100

  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (API Design Reviewer) differs from the folder (api-design-reviewer)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 113 steps
  • 100Execution cost. Instruction body is 3075 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 19 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)
  • -43 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 200: enough signal without eating the budget
  • +4Structure: 59 headings
  • +3Step-by-step instructions: 113 items
  • +3Output format is stated explicitly
  • +4Has examples (21 code blocks)
  • +3All 3 scripts are documented

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