AC api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
IntegrationSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: api-design (ClawHub)
How to improve
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-password-literalSKILL.md:306Hard-coded password / key literal (may be an example)X-API-Key: sk_l…123
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "origin"
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (api-design) differs from the folder (npjames-api-design)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 18 steps
- 100Execution cost. Instruction body is 3219 tokens
- 100Running it twice. Mutating operations check current state
- low 11 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)
- +1No license
- +2Single-language instructions
- +3Description length 156: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (24 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.
External checks
ClawHub: clean
This is a documentation-only REST API design guide with no executable behavior or hidden data access.
LLM: benign (high) · VirusTotal: · 29 May 2026