Content
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is largely a meta-template with boilerplate sections rather than actionable, concrete guidance for API mocking. It lacks any executable code examples, specific tool recommendations, or concrete mock definitions. The content tells Claude what to do at a high level but doesn't provide the specific knowledge or patterns that would make Claude more effective at the task.
Suggestions
Add concrete, executable code examples showing how to set up a mock server (e.g., using MSW, WireMock, or Express with sample route definitions and fixture data).
Replace vague instructions like 'Clarify the API contract' with specific templates or schemas showing what a mock definition looks like (e.g., a sample OpenAPI spec mapped to mock responses).
Remove boilerplate sections that don't add value ('Use this skill when', 'Do not use this skill when', 'Context', 'Limitations') or condense them to 1-2 lines maximum.
Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the most critical patterns and examples directly in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows. Sections like 'Use this skill when', 'Do not use this skill when', 'Context', and 'Limitations' are padded with obvious guidance that doesn't add actionable value. The 'Safety' section states obvious best practices. Much of this is meta-instruction rather than substantive content. | 1 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. Instructions like 'Clarify the API contract' and 'Define mock routes' are vague directives without specific implementation guidance. There are no code snippets, no example mock definitions, no sample server configurations—everything is abstract description. | 1 / 3 |
Workflow Clarity | The Instructions section provides a rough sequence of steps (clarify contract → define routes → provide fixtures → document), but there are no validation checkpoints, no feedback loops, and no concrete verification steps. The sequence is present but lacks the specificity needed for reliable execution. | 2 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed implementation, which is a good progressive disclosure pattern. However, no bundle files are provided, so the reference is unverifiable. The main file itself contains too much boilerplate that could be trimmed rather than properly structured content that warrants splitting. | 2 / 3 |
Total | 6 / 12 Passed |