skill-ao92265-claude-code-playbook-api-test · by Install
$ agentstack add skill-ao92265-claude-code-playbook-api-test ✓ 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 Used
- ✓ 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-ao92265-claude-code-playbook-api-test) 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
API Endpoint Testing
Interactive testing of API endpoints with validation of responses.
Steps
- Identify the endpoint:
- URL, HTTP method, required headers
- Authentication: Bearer token, API key, cookie, or none
- Request body format: JSON, form data, multipart
- Expected response: status code, content type, shape
- Test the happy path:
- Send a request with valid inputs
- Verify: status code matches expected (200, 201, etc.)
- Verify: response body shape matches API contract
- Verify: response headers are correct (Content-Type, CORS, caching)
- Record the response time
- Test error cases:
- Missing required fields → expect 400 Bad Request
- Invalid data types → expect 400 or 422
- Missing authentication → expect 401 Unauthorized
- Insufficient permissions → expect 403 Forbidden
- Non-existent resource → expect 404 Not Found
- Verify error response includes helpful message
- Test edge cases:
- Empty strings, null values, zero, negative numbers
- Very long strings (boundary testing)
- Special characters and unicode
- Empty arrays and objects
- Pagination boundaries (page 0, page beyond last)
- Test idempotency (for mutating endpoints):
- Send the same POST/PUT request twice
- Does it create duplicates? (it shouldn't for idempotent operations)
- Does the response change on the second call?
- Report results:
``` ## API Test Results — [ENDPOINT]
| Test | Expected | Actual | Status | |------|----------|--------|--------| | Happy path | 200 | 200 | PASS | | Missing auth | 401 | 401 | PASS | | Invalid body | 400 | 500 | FAIL | | ... | ... | ... | ... |
Response time: Xms Issues found: Y ```
Important
- Use
curlor the project's HTTP client — don't install extra tools. - Don't test against production unless the user explicitly says to.
- Mask sensitive data in output (tokens, passwords, PII).
- Test one endpoint at a time — keep the scope focused.
- Record response times but don't treat them as benchmarks — local testing != production performance.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ao92265
- Source: ao92265/claude-code-playbook
- 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.