Install
$ agentstack add skill-jovd83-restassured-skill-coverage-gap-report ✓ 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.
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
Build Coverage Gap Report
1. Gather Inputs
- Require the current
docs/testing/test-mapping-report.md. - Require
docs/testing/contract-mismatches.mdwhen it exists. - Require the active coverage matrices when they contain gaps not yet reflected in traceability.
2. Choose The Files
- Prefer
docs/testing/coverage-gap-report.md. - When the user wants human-friendly navigation, also generate
docs/testing/html/coverage-gap-report.html.
3. Build The Report
- Treat
Not covered,Partial, andContract driftoperations as primary gaps. - Include explicit gap bullets from the traceability report.
- Separate the report into summary, operation gaps, and planning recommendations.
- Keep one operation row per endpoint and method in markdown.
- In HTML, group the operation gaps by resource and make the next action obvious.
4. Output Shape
- Start from [coverage-gap-report-template.md](assets/coverage-gap-report-template.md).
- Keep the exact section headings so the generator can update the file deterministically.
- Run
python scripts/generate_coverage_gap_report.py --mapping --output-md --output-html.
5. Keep It Actionable
- Explain why each gap matters.
- Recommend the next slice to implement.
- Update the session-state artifact after generating or changing the report.
6. Examples
- Input:
Show me the biggest API coverage gaps.
Output: Create docs/testing/coverage-gap-report.md and the paired HTML report.
- Input:
Which endpoints are only covered through drift assertions?
Output: Produce a gap report that isolates Contract drift operations and suggests next actions.
7. Troubleshooting
- Problem: The traceability report says everything is covered.
Fix: Still surface Contract drift rows and explicit gap bullets because those are planning gaps.
- Problem: The markdown and HTML disagree.
Fix: Regenerate the HTML from the canonical markdown inputs and do not hand-edit the HTML.
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.