703-technologies-fuzzing-testing — Claude Code skill
The 703-technologies-fuzzing-testing skill guides CATS-based fuzz testing for Java APIs from an OpenAPI contract. Use it to probe invalid inputs, boundary conditions, and CI checks.
Apache-2.0 304 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a claude-codeWhat 703-technologies-fuzzing-testing does
The skill guides an agent through setting up and reviewing HTTP API fuzz tests with CATS. It covers negative cases such as omitted fields, incorrect types, malformed values, and violations of size, range, format, or enum constraints. It also addresses local runs, CI checks, and how to report and investigate findings.
Before changing the project, the agent must read references/703-technologies-fuzzing-testing.md and inspect the API context. It must run ./mvnw compile or mvn compile first; a compilation failure means stopping there. CATS must use a verified local cats/cats.jar or an approved prebuilt image. After changes, the skill calls for ./mvnw clean verify or mvn clean verify.
What it helps with
- Add contract-based negative tests for a Java API
- Catch missing fields and invalid payload types
- Probe size and range boundaries
- Add reproducible CATS checks to CI
Example prompts for the agent
- Add CATS fuzz tests for this Java API using its OpenAPI contract.
- Check how the API handles missing fields and malformed values.
- Set up CATS checks in CI and explain how to reproduce their failures.
How to install 703-technologies-fuzzing-testing
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a claude-code2Manually: put the files in place
~/.claude/skills/703-technologies-fuzzing-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/703-technologies-fuzzing-testing/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a codex2Manually: put the files in place
.agents/skills/703-technologies-fuzzing-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a cursor2Manually: put the files in place
.cursor/skills/703-technologies-fuzzing-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/703-technologies-fuzzing-testing2Manually: put the files in place
.github/skills/703-technologies-fuzzing-testing/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/703-technologies-fuzzing-testingManually: put the files in place
.devin/skills/703-technologies-fuzzing-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -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 703-technologies-fuzzing-testing
How do I install 703-technologies-fuzzing-testing in Claude Code?
Run npx skills add jabrena/plinth --skill 703-technologies-fuzzing-testing -a claude-code. The skill file is at ~/.claude/skills/703-technologies-fuzzing-testing/SKILL.md.
What does 703-technologies-fuzzing-testing do?
It guides CATS-based fuzz testing for Java APIs against OpenAPI contracts. The workflow covers invalid requests, boundary inputs, CI checks, and investigation of findings.
What must pass before the skill changes a project?
The project must compile with ./mvnw compile or mvn compile; the workflow stops if compilation fails. CATS must run from a verified local cats/cats.jar or an approved prebuilt image.
Source text
SKILL.md · Apache-2.0
--- name: 703-technologies-fuzzing-testing description: Use 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 integration, reproducible failures, and local execution guidance. This should trigger for requests such as Add fuzz testing to a Java project; Use CATS for API negative testing; Review CI quality gates for API contract robustness; Improve boundary and malformed input test coverage; Run CATS fuzz tests against an OpenAPI contract. Part of Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # Java fuzz testing with CATS Design and implement contract-driven fuzz testing for Java APIs using CATS to uncover edge cases and input-validation defects early. **What is covered in this Skill?** - CATS setup using a trusted local jar or prebuilt image and baseline command usage for OpenAPI-driven fuzzing - Negative testing strategy for invalid payloads, missing fields, wrong types, and malformed values - Boundary testing for size, range, format, and enum constraints - CI integration patterns with actionable logs and reproducible failures - Local execution workflow for contributors before opening pull requests - Reporting and triage practices for fuzzing findings **Scope:** Focus on HTTP API fuzzing and contract validation with CATS. Use this skill to define practical, repeatable checks in both local and CI workflows. ## Constraints Before applying any fuzz testing changes, ensure the project compiles. If compilation fails, stop immediately. After implementation, regenerate skills and run verification. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before applying any change - **SAFETY**: If compilation fails, stop immediately and do not proceed - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` after applying improvements - **SUPPLY CHAIN**: Use only a verified local `cats/cats.jar` or an approved prebuilt image; generated artifacts must depend only on trusted local or approved image inputs - **BEFORE APPLYING**: Read the reference for detailed examples, good/bad patterns, and constraints - **EDGE CASE**: If request scope is ambiguous, stop and ask a clarifying question before applying changes - **EDGE CASE**: If required inputs, files, or tooling are missing, report what is missing and ask whether to proceed with setup guidance ## When to use this skill - Add fuzz testing to a Java project - Use CATS for API negative testing - Review CI quality gates for API contract robustness - Improve boundary and malformed input test coverage - Run CATS fuzz tests against an OpenAPI contract ## Workflow 1. **Read reference and assess project context** Read `references/703-technologies-fuzzing-testing.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/703-technologies-fuzzing-testing.md](references/703-technologies-fuzzing-testing.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth