Restassured Analysis Requirements
Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.
Install
$ agentstack add skill-jovd83-restassured-skill-requirements ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jovd83-restassured-skill-requirements) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Analyze Requirements
1. Find Sources
- Search the repo for stories, epics, acceptance criteria, ADRs, specs, and tickets.
- Read the user-provided requirement source completely.
- Extract only behavior that affects API requests, responses, authorization, validation, workflow state, integrations, or observability.
2. Normalize The Requirements
- Convert prose into testable behaviors.
- Separate happy path, validation, authorization, negative, and workflow behaviors.
- Mark missing details explicitly instead of inventing them.
3. Validate With The User
- Present the summarized behaviors.
- Ask the user to confirm that the requirement summary is complete.
- Stop before coverage generation when the summary is not approved.
4. Output Shape
- Group the output by feature or endpoint area.
- Include the source identifier for each behavior when available.
- Highlight gaps that must be resolved by contract analysis or user clarification.
5. Examples
- Input:
Derive tests from these checkout user stories.
Output: A grouped list of API behaviors, validations, permissions, and edge cases tied back to story IDs.
6. Troubleshooting
- Problem: The requirements mention UI behavior only.
Fix: Extract only the backend behavior that the API must enforce or expose.
- Problem: The requirements conflict with the contract.
Fix: Surface the mismatch and request clarification before implementation.
7. Handoff
Use dispatcher intent plan_api_test_coverage when the next step is scenario planning.
If dispatcher routing is unavailable, hand off to ../coverage_plan/generation/SKILL.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jovd83
- Source: jovd83/restassured-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.