702-technologies-wiremock — Claude Code skill: setup guide
702-technologies-wiremock delivers framework-neutral WireMock guidance for HTTP stub design, dynamic ports, and stable test isolation.
Apache-2.0 318 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a claude-codeWhat 702-technologies-wiremock does
Part of the Plinth Toolkit, this skill guides coding agents through building and debugging HTTP stubs with WireMock. It covers Java DSL and JSON mappings, header and query matching, response fault simulations, and classpath body fixtures using bodyFileName.
Flaky test prevention takes priority here. The instructions direct the agent to handle stub lifecycle with resetAll(), eliminate leaked state across runs, and configure dynamic base URLs for the system under test. It also provides steps to inspect unmatched request journals when calls fail.
Scope stays strictly at the HTTP mock level. The rules prevent the model from generating test harness extensions or annotations like @SpringBootTest directly, offloading them to framework-specific integration skills instead. Running ./mvnw compile remains mandatory before proposing Java changes.
What it helps with
- design WireMock stubs via Java DSL or JSON mapping files
- debug flaky test suites caused by dirty stub state between runs
- verify outbound HTTP requests against simulated endpoints
- configure fault injection and dynamic port assignment in test suites
Example prompts for the agent
- Review my WireMock mappings and help me verify outbound HTTP calls
- Create a WireMock stub simulating slow responses with dynamic port configuration
- Fix flaky test isolation by resetting all stub mappings after each run
How to install 702-technologies-wiremock
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a claude-code2Manually: put the files in place
~/.claude/skills/702-technologies-wiremock/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/702-technologies-wiremock/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a codex2Manually: put the files in place
.agents/skills/702-technologies-wiremock/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a cursor2Manually: put the files in place
.cursor/skills/702-technologies-wiremock/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/702-technologies-wiremock2Manually: put the files in place
.github/skills/702-technologies-wiremock/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/702-technologies-wiremockManually: put the files in place
.devin/skills/702-technologies-wiremock/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 702-technologies-wiremock -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 702-technologies-wiremock
How to install 702-technologies-wiremock in Claude Code?
Run npx skills add jabrena/plinth --skill 702-technologies-wiremock -a claude-code in your terminal. The skill file is placed at ~/.claude/skills/702-technologies-wiremock/SKILL.md.
What does 702-technologies-wiremock do?
It guides your AI assistant in designing stable WireMock stubs, setting matching patterns, and debugging unmatched HTTP requests without tying logic to a specific framework.
Does this skill configure Spring Boot or Quarkus test runners?
No, it focuses solely on portable WireMock behavior. Framework configurations like @SpringBootTest or @QuarkusTest must be delegated to dedicated integration skills.
Source text
SKILL.md · Apache-2.0
--- name: 702-technologies-wiremock description: Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design or review WireMock stubs (JSON mappings or Java DSL); Improve request matching, isolation, or reset strategy for HTTP mocks; Add or fix verification of outbound HTTP calls to a WireMock server; Debug flaky tests involving WireMock or unmatched request journals. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # WireMock best practices Help teams use **WireMock** effectively for HTTP dependency stubbing with **stable, isolated** tests. **What is covered in this Skill?** - Stub **isolation**: per-test registration, `resetAll()`, avoiding leaked global stubs - **Request matching**: method, path, headers, query, body patterns; when broad patterns are acceptable - **Responses**: status, headers, JSON/XML bodies, `bodyFileName` / classpath fixtures, fault simulation (delays, errors) - **Dynamic ports** and propagating base URLs into the system under test - **Verification** of outbound HTTP calls and debugging unmatched requests - Clear **delegation** to framework integration-test skills for test class layout and extensions **Scope:** Portable WireMock behavior only. For **`BaseIntegrationTest`**, `WireMockExtension`, and stack-specific integration tests, use `@132-java-testing-integration-testing`, `@322-frameworks-spring-boot-testing-integration-tests`, `@422-frameworks-quarkus-testing-integration-tests`, or `@522-frameworks-micronaut-testing-integration-tests`. For **OpenAPI** contract quality, use `@701-technologies-openapi`. ## Constraints Keep recommendations at the WireMock and HTTP-stub layer unless the user explicitly asks for framework integration. After editing this repository's XML sources, regenerate skills and verify the build. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before proposing Java or Maven changes in the same change set - **FRAMEWORK**: Defer `@SpringBootTest` / `@QuarkusTest` / `@MicronautTest` and extension setup to `@132-java-testing-integration-testing` or the matching `322` / `422` / `522` integration-test skill - **CONTRACTS**: Defer OpenAPI document structure and linting to `@701-technologies-openapi` - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` before promoting changes - **EDGE CASE**: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands - **EDGE CASE**: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance - **EDGE CASE**: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off ## When to use this skill - Design or review WireMock stubs (JSON mappings or Java DSL) - Improve request matching, isolation, or reset strategy for HTTP mocks - Add or fix verification of outbound HTTP calls to a WireMock server - Debug flaky tests involving WireMock or unmatched request journals - Stub external HTTP APIs in tests with stable fixtures and dynamic ports ## Workflow 1. **Read reference and assess project context** Read `references/702-technologies-wiremock.md` and inspect current API/context artifacts before proposing changes. 2. **Gather scope and decide target improvements** Identify requested outcomes, constraints, and the minimum safe set of changes to apply. 3. **Apply technology-aligned changes** Implement or refactor artifacts following the reference patterns and project conventions. 4. **Run verification and report results** Execute appropriate checks and summarize what changed, what was verified, and any follow-up actions. ## Reference For detailed guidance, examples, and constraints, see [references/702-technologies-wiremock.md](references/702-technologies-wiremock.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth