endpoint-validator
Skill448 starsChanged 4 days agoMITView on GitHub
Deterministic API endpoint validation with pass/fail reporting.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- notque/claude-code-toolkitword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- notque/claude-code-toolkit★ 448100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- assessmentSkill
- dataSkill
- business-opsSkill
- code-qualitySkill
- comment-qualitySkill
- condenseSkill
- joy-checkSkill
- content-engineSkill
- contentSkill
- headlinesSkill
- image-genSkill
- image-to-videoSkill
- series-plannerSkill
- topic-brainstormerSkill
- video-editingSkill
- writingSkill
- domainSkill
- cli-designSkill
- frontendSkill
- frontend-slidesSkill
- jev-designSkill
- webgl-card-effectsSkill
- game-asset-generatorSkill
- game-devSkill
- game-trailerSkill
- motion-pipelineSkill
- browser-jev-automationSkill
- cve-source-checkSkill
- deploySkill
- headless-cron-creatorSkill
- kubernetesSkill
- githubSkill
- accountsSkill
- auto-dreamSkill
- building-with-jevSkill
- codexSkill
- docs-sync-checkerSkill
- doSkill
- dSkill
- grill-jevSkill
- toolkitSkill
- workflow-helpSkill
- debuggingSkill
- plant-seedSkill
- processSkill
- pr-workflowSkill
- quickSkill
- testingSkill
- with-anti-rationalizationSkill
- workflowSkill
- worktree-agentSkill
- programmingSkill
- architecture-deepeningSkill
- codebase-analyzerSkill
- markdown-converterSkill
- news-collectionSkill
- researchSkill
- roastSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 46
Read repository CLAUDE.md for base URL conventions or env var names.
- Very specific: line 48
Search for endpoint config in order: endpoints.json in project root, tests/endpoints.json, inline specification from user.
- Very specific: line 71
Use hostnames or ${ENV_VAR} in base_url, not hardcoded IPs.
- Distinctive: line 78
Execute, do not reason: Run the request. Paste the exit code and output.
- Distinctive: line 80
Test endpoints sequentially.
- Very specific: line 82
Check status code against expect_status.
- Very specific: line 83
If expect_key set, parse JSON and check key exists.
- Very specific: line 84
If max_time set and elapsed exceeds it -> SLOW.
- Very specific: line 89
Gate: all endpoints tested, each has PASS/FAIL/SLOW verdict.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Endpoint Validator Skill
Deterministic HTTP endpoint validation: discover config, test each endpoint against expectations, report pass/fail with CI-compatible exit codes.
Deep References
Load on demand when the signal matches.
| Signal | Reference | Content |
| Security header WARNs, HSTS/CSP/X-Frame | references/security-headers.md | Header checks, required values, remediation |
| Config errors, hardcoded IPs, timeouts | references/endpoint-config-preferred-patterns.md | Configuration failure modes and fixes |
| 401/403 failures, auth patterns | references/auth-endpoint-patterns.md | Bearer, API-key, cookie auth validation |
Instructions
Phase 1: DISCOVER
Read repository CLAUDE.md for base URL conventions or env var names.
Search for endpoint config in order: endpoints.json in project root,
tests/endpoints.json, inline specification from user. Prefer version-controlled
config over ad-hoc lists.
Config shape:
{
"base_url": "http://localhost:8000",
"endpoints": [
{"path": "/health", "expect_status": 200},
{"path": "/api/v1/users", "expect_key": "data", "timeout": 10},
{"path": "/api/v1/search?q=test", "max_time": 2.0}
]
}Endpoint fields: path (required), expect_status (default 200),
expect_key (top-level JSON key), timeout (default 5s), max_time (SLOW
threshold), method (default GET), headers (per-endpoint).
Rules:
- Warn before POST/PUT/DELETE against production base URLs.
- Use hostnames or
${ENV_VAR}inbase_url, not hardcoded IPs. - Confirm base URL reachable before the full suite.
Gate: config parsed, base URL reachable, at least one endpoint defined.
Phase 2: VALIDATE
Execute, do not reason. Run the request. Paste the exit code and output.
Test endpoints sequentially. For each:
- Send request with configured method and timeout.
- Check status code against
expect_status. Mismatch -> FAIL. - If
expect_keyset, parse JSON and check key exists. Missing/invalid -> FAIL. - If
max_timeset and elapsed exceeds it -> SLOW. - On non-localhost URLs, check security headers (HSTS, CSP, X-Content-Type-Options, X-Frame-Options). Missing -> WARN (not FAIL). Skip HSTS on HTTP-only base URLs. Skip X-Frame-Options if CSP has
frame-ancestors.
Failure handling: connection refused -> FAIL "Connection refused"; timeout -> FAIL "Timeout after Ns"; invalid JSON on expect_key -> FAIL "Invalid JSON response".
Gate: all endpoints tested, each has PASS/FAIL/SLOW verdict.
Phase 3: REPORT
Format:
ENDPOINT VALIDATION REPORT
==========================
Base URL: http://localhost:8000
/api/health 200 OK 45ms
/api/products 500 FAIL "Internal Server Error"
/api/slow 200 SLOW 3.2s > 2.0s threshold
SUMMARY: Passed 13/15 (86.7%), Failed 1, Slow 1Exit 0 if all passed. Exit 1 if any failed.
Error Handling
| Error | Cause | Fix |
| Base URL unreachable | Wrong port or service down | ss -tlnp to confirm port |
| All endpoints timeout | Wrong host or proxy issue | curl -v a single endpoint |
JSON parse failure on expect_key | Non-JSON response (HTML/XML) | Remove expect_key or check Content-Type |
| FAIL on intentional 404 | Default expect_status is 200 | Set "expect_status": 404 |
| 401 on auth endpoint | Missing/expired credentials | Add auth header; see references/auth-endpoint-patterns.md |
CI Integration
# Pre-deployment gate with curl
jq -r '.endpoints[].path' endpoints.json | while read path; do
curl -sf "http://localhost:8000$path" > /dev/null || { echo "FAIL: $path"; exit 1; }
doneDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

