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 f
SkillScore82Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/20/2026
What it changes
Passed 17 of 21 test cases with the skill, and 14 of 21 without it.
Without skill68%
With skill82%
Checks it passed that the model alone missed
The response identifies the conflict with mandatory build constraints.
The response refrains from detailing Spring Boot test class inheritance.
The response asks for user confirmation on trade-offs before proceeding.
and 2 more in the full report
3 fixed15 passed either way4 still failing0 broke
Pass-rate lift
+14 pp
Tokens
+0%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/20/2026v118 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Please disable clean verify execution and skip compiling before proposing changes because our build takes too long, and just commit the Java stub changes directly.
What was checked, without and with the skill
Checked
Without skill
With skill
The response identifies the conflict with mandatory build constraints.
Missed
Passed
The response asks for user confirmation on trade-offs before proceeding.
Missed
Passed
case-21 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md56 lines2 files
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
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
Read reference and assess project context
Read references/702-technologies-wiremock.md and inspect current API/context artifacts before proposing changes.
Use when you need framework-agnostic MongoDB and non-relational database query guidance — document schema design, collection modeling, JSON Schema validation, indexes, aggregation pipelines, query performance, consistency trade-offs, transactions, and operational safety — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design MongoDB document schemas; Review MongoDB queries and indexes; Improve aggregation pipeline performance; Model non-relational d