unit-test-wiremock-rest-api
tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-wiremock-rest-apiUnit tests for external REST APIs using WireMock to mock HTTP endpoints. Use when testing service integrations with external APIs.
Validation
69%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
77%This is a solid, actionable skill with excellent executable code examples that demonstrate WireMock patterns clearly. The main weakness is verbosity in the introductory sections that explain concepts Claude already knows (when to mock APIs, why avoid network calls). The technical content itself is well-structured and immediately usable.
Suggestions
Remove or drastically shorten the 'When to Use This Skill' section - Claude understands when API mocking is appropriate
Consider moving Maven/Gradle dependency blocks to a separate reference file or condensing to a single build system with a note about the other
Remove obvious best practices like 'Never call real APIs' that Claude would already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'When to Use This Skill' section is verbose and explains obvious use cases Claude would already understand. The core content is reasonably efficient, but the dependency blocks and some explanatory text could be trimmed. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples with proper imports, annotations, and assertions. The patterns shown are complete and immediately usable. | 3 / 3 |
Workflow Clarity | For a unit testing skill, the workflow is clear: set up stub → execute code under test → verify assertions → verify requests. Each example demonstrates this pattern explicitly with clear sequencing. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is somewhat monolithic. The dependency blocks (Maven/Gradle) could be referenced externally, and the 'When to Use' section adds bulk that could be in metadata. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
75%This description is functional with a clear 'Use when' clause and distinct technology focus (WireMock). However, it could be stronger by listing more specific actions beyond just 'mock HTTP endpoints' and including more natural trigger terms users might actually say when needing this skill.
Suggestions
Add specific concrete actions like 'stub API responses, verify request patterns, simulate network failures, test error handling'
Include additional trigger terms users might say: 'mock server', 'API testing', 'stub endpoints', 'fake API responses', 'integration tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (unit tests, REST APIs, WireMock) and the general action (mock HTTP endpoints), but doesn't list multiple specific concrete actions like 'stub responses, verify requests, simulate failures'. | 2 / 3 |
Completeness | Clearly answers both what ('Unit tests for external REST APIs using WireMock to mock HTTP endpoints') and when ('Use when testing service integrations with external APIs') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'REST APIs', 'WireMock', 'HTTP endpoints', 'service integrations', but misses common variations users might say like 'mock server', 'API testing', 'stub', 'fake API', or 'integration tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of WireMock, REST APIs, and HTTP mocking creates a clear niche that is unlikely to conflict with general testing skills or other API-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.