Java Testing
HoangNguyen0403/agent-skills-standard
Testing standards using JUnit 5, AssertJ, Mockito, Cucumber, and Spring Boot integration tests for Java.
A skill your agent uses when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures…
Install 702 Technologies Wiremock
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jabrena/plinth 702-technologies-wiremock --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/702-technologies-wiremock .claude/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .claude/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremockType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jabrena/plinth 702-technologies-wiremock --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/702-technologies-wiremock .agents/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .agents/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jabrena/plinth 702-technologies-wiremock --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/702-technologies-wiremock .cursor/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .cursor/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jabrena/plinth.git --path skills/702-technologies-wiremock--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jabrena/plinth 702-technologies-wiremock --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/702-technologies-wiremock .gemini/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .gemini/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jabrena/plinth 702-technologies-wiremockInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/702-technologies-wiremock .github/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .github/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jabrena/plinth --skill 702-technologies-wiremock -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jabrena/plinth 702-technologies-wiremock --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jabrena/plinth.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/702-technologies-wiremock .opencode/skills/702-technologies-wiremock && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "702-technologies-wiremock" agent skill from https://github.com/jabrena/plinth/tree/main/skills/702-technologies-wiremock into .opencode/skills/702-technologies-wiremock/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "702-technologies-wiremock", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
702-technologies-wiremock- GitHub stars
- 447
- Token cost
- ~1.1k tokens
- SKILL.md length
- 408 words
- Files
- 2 (incl. references)
- Skills in repo
- 124
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures…
- You need framework-agnostic WireMock guidance — stub design
- SKILL.md covers Constraints, When to use this skill, Workflow and Reference
- Calls mvn
- Programmatic mappings
What it does
702 Technologies Wiremock is an agent skill from jabrena/plinth. 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…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/702-technologies-wiremock.md`).
It sits in Testing & QA, covering Backend development, Failing and flaky tests and Integration testing. It works with Java, Spring Boot and OpenAPI. The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.
When your agent uses it
- You need framework-agnostic WireMock guidance — stub design
- Programmatic mappings
- Precise request matching
- Response bodies and faults
Example prompts
- “/702-technologies-wiremock”
What it can do on your machine
Read from SKILL.md and the folder at commit dca88dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mvn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
702 Technologies Wiremock loads about 1.1k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 175 tokens; SKILL.md has 408 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 408 words, ~1,068 tokens.
Download SKILL.mdSave it as
.claude/skills/702-technologies-wiremock/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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
- metadata.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 compileormvn compilebefore proposing Java or Maven changes in the same change set - FRAMEWORK: Defer
@SpringBootTest/@QuarkusTest/@MicronautTestand extension setup to@132-java-testing-integration-testingor the matching322/422/522integration-test skill - CONTRACTS: Defer OpenAPI document structure and linting to
@701-technologies-openapi - VERIFY: Run
./mvnw clean verifyormvn clean verifybefore 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
Show full SKILL.md (140 more words)Show less
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.
- Gather scope and decide target improvements
Identify requested outcomes, constraints, and the minimum safe set of changes to apply.
- Apply technology-aligned changes
Implement or refactor artifacts following the reference patterns and project conventions.
- 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.
© jabrena, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/702-technologies-wiremock of jabrena/plinth.
- SKILL.md
- references/702-technologies-wiremock.md
Open the folder on GitHubat commit dca88dc
Compare with similar skills
702 Technologies Wiremock next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| 702 Technologies Wiremock this skilljabrena/plinth | 447 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Java TestingHoangNguyen0403/agent-skills-standard | 572 | — | ~1k | Automated safety check: Pass | MIT | |
| Java Coding StandardsSnailclimb/AIGuide | 675 | — | ~1k | Automated safety check: Pass | None | |
| Oryxos Initoryx-labs/oryxos | 187 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Springboot Init Skilljiushiwon/wg-skills | 114 | — | ~2.2k | Automated safety check: Notes | Apache-2.0 | |
| Spring Data Testingarangodb/spring-data | 116 | — | ~844 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Java Coding Standards
Snailclimb/AIGuide
Java/Spring Boot 编码规范：用于编写、审查、重构和讲解 Java 代码。适用于 Java 风格、Spring Boot 架构、Controller/Service/Manager/DAO 分层、API 边界、Entity/VO/Form/DTO/BO 设计、MyBatis/MyBatis-Plus 持久化、事务、异常、日志、安全、性能、测试和 Java 代码评审等场景。默认结合…
Oryxos Init
oryx-labs/oryxos
初始化 OryxOS（或同类 JDK 21 + Spring Boot 3.x 企业级单体）的工程地基：Maven 多模块骨架、 结构化日志、Actuator + Prometheus 监控、Spring MVC + 虚拟线程、springdoc OpenAPI、 统一响应体与全局异常/错误码、Google 格式 + 阿里编码规约（Spotless + 阿里 P3C +…
Springboot Init Skill
jiushiwon/wg-skills
Spring Boot 项目一键初始化技能。面向零基础小白，提供环境探测、自动安装、完整 Web 骨架生成、SSE 流式框架、JWT 鉴权、统一响应封装、文件上传接口、一键启动/重启脚本、Swagger 文档，内置 MySQL（默认）/ PostgreSQL / MongoDB 数据库选择。用户只需说"帮我搭一个 Spring Boot…
Spring Data Testing
arangodb/spring-data
Write and run tests for arangodb/spring-data, select regression coverage, and reproduce CircleCI failures.
Springboot Verification
affaan-m/ECC
Run the full Spring Boot verification loop — Maven or Gradle build, SpotBugs, PMD, and Checkstyle static analysis, unit and Testcontainers integration tests with JaCoCo coverage, OWASP dependency…
More from jabrena/plinth
All 124 skills in this repo703 Technologies Fuzzing Testing
jabrena/plinth
A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…
033 Architecture Diagrams
jabrena/plinth
A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…
112 Java Maven Plugins
jabrena/plinth
A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…
151 Java Performance Jmeter
jabrena/plinth
A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…
161 Java Profiling Detect
jabrena/plinth
A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…
001 Commands Inventory
jabrena/plinth
A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…
Related
Works with
Categories
Questions about 702 Technologies Wiremock
What does 702 Technologies Wiremock do?
A skill your agent uses when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures…. 702 Technologies Wiremock is an agent skill from jabrena/plinth. 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.
When should I use 702 Technologies Wiremock?
702 Technologies Wiremock fits situations like: you need framework-agnostic WireMock guidance — stub design; programmatic mappings; precise request matching; response bodies and faults.
How do I install 702 Technologies Wiremock in Claude Code?
Run `npx skills add jabrena/plinth --skill 702-technologies-wiremock -a claude-code`. Or copy the skill folder (skills/702-technologies-wiremock in jabrena/plinth) into .claude/skills/702-technologies-wiremock in your project. Claude Code loads it when a task matches its description.
How do I install 702 Technologies Wiremock in Codex?
Run `npx skills add jabrena/plinth --skill 702-technologies-wiremock -a codex`. Or copy the skill folder (skills/702-technologies-wiremock in jabrena/plinth) into .agents/skills/702-technologies-wiremock in your project. Codex loads it when a task matches its description.
Can I use 702 Technologies Wiremock in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jabrena/plinth --skill 702-technologies-wiremock -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/702-technologies-wiremock, .gemini/skills/702-technologies-wiremock, .github/skills/702-technologies-wiremock and .opencode/skills/702-technologies-wiremock in your project.
What does 702 Technologies Wiremock need to run?
Going by SKILL.md and its folder, 702 Technologies Wiremock needs the command-line tools its instructions call (mvn).
Does 702 Technologies Wiremock access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is 702 Technologies Wiremock safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does 702 Technologies Wiremock use?
702 Technologies Wiremock is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does 702 Technologies Wiremock use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to 702 Technologies Wiremock?
Skills that share tags, products or a category with 702 Technologies Wiremock: Java Testing (HoangNguyen0403/agent-skills-standard, 572 stars), Java Coding Standards (Snailclimb/AIGuide, 675 stars), Oryxos Init (oryx-labs/oryxos, 187 stars) and Springboot Init Skill (jiushiwon/wg-skills, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 702 Technologies Wiremock?
jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.
Source: jabrena/plinth on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.