Content
50%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-sectioned with sensible scope boundaries (Use/Do not use, Safety) and lean instruction bullets, but it is padded with redundant restatements of the description (persona intro, Context, Requirements), offers no executable specifics, and its single progressive-disclosure reference points to a nonexistent file, leaving the skill without its detailed implementation layer. Workflow steps lack any validation checkpoint such as verifying mocks against the contract.
Suggestions
Add the missing resources/implementation-playbook.md (or fix the path to wherever the code samples, checklists, and templates actually live) — both the Instructions and Resources sections currently point to a file that does not exist in the bundle.
Remove the redundant Context and Requirements sections and the restating persona intro, and use the reclaimed space for concrete guidance such as a recommended mock tool or a minimal example of defining a route with scenarios.
Add a validation checkpoint to the workflow, e.g., verify generated mock responses against the agreed API contract (auth flows, error shapes, latency) before delivering the solution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quotes: "You are an API mocking expert specializing in creating realistic mock services... facilitate thorough testing" and "The user needs to create mock APIs for development, testing, or demonstration purposes. Focus on creating flexible, realistic mocks..." — the persona intro, Context section, and Requirements section ("Take the requirements, target, and scope from the user's request") largely restate the description, and the "Use this skill when" list duplicates the frontmatter triggers; the core instruction bullets are lean, so it is mostly efficient but could be tightened rather than noticeably verbose. | 3 / 5 |
Actionability | Quotes: "Define mock routes, scenarios, and state transitions", "Provide deterministic fixtures with optional randomness toggles", "Document how to run the mock server and how to switch scenarios" — the bullets name specific deliverables (more than minimal high-level hints), but there is no code, command, or tooling example anywhere in the body, and the implementation specifics are deferred to a reference file, so guidance is concrete but incomplete. | 3 / 5 |
Workflow Clarity | Quotes: "Define mock routes, scenarios, and state transitions before generating responses" — a rough design-before-implement sequence is present across the instruction bullets, but there are no validation checkpoints (e.g., verifying mock responses against the API contract before delivery), matching the anchor of steps listed with checkpoints missing or implicit. | 3 / 5 |
Progressive Disclosure | Quotes: "If detailed implementation is requested, open `resources/implementation-playbook.md`" and "`resources/implementation-playbook.md` for code samples, checklists, and templates" — the reference is clearly signaled and one level deep by design, but the file does not exist anywhere in the bundle (no resources/ directory is present), so the disclosure path is broken and the promised detailed content is simply absent; this is more than the 'minor organization gaps' of the 4 anchor. | 3 / 5 |
Total | 12 / 20 Passed |