endpoint-validator

Featured

Deterministic API endpoint validation with pass/fail reporting.

API & Backend 425 stars 46 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
88
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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: ```json { "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 bas...

Details

Author
notque
Repository
notque/vexjoy-agent
Created
6 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

backend-validation

Use this skill when validating a backend API or WebSocket endpoint end-to-end, including acquiring an OIDC bearer token for authenticated calls. Trigger whenever the user asks to test/validate/smoke-check a backend, write a Hurl test, hit a WebSocket, acquire an access token, exercise an OIDC flow, debug a 401, or verify an endpoint works with real auth. Applies to projects that use Hurl for HTTP tests, websocat for WebSocket probes, and oauth2c or curl-based flows for token acquisition (Authentik, Keycloak, Okta, Auth0, any RFC 6749 / OIDC Core provider). Prefer this skill over ad-hoc curl + bash when the user has more than one endpoint to check, chained auth flows, or anything resembling a regression test — because the Hurl + cached-refresh-token pattern is 10× less code and survives the next session.

11 Updated 1 months ago
johnkozaris
API & Backend Listed

endpoint-test

Hit a running dev endpoint via curl and verify status + response shape + required headers (auth, tenant) field-by-field against the DTO. Use AFTER any controller, DTO, guard, pipe or interceptor edit to prove the route works end-to-end, or when a frontend reports an unexpected shape and you need ground truth. NOT when no dev server is running (it refuses to auto-start), NOT against staging/prod hosts, and NOT for static contract diffing — that is api-snapshot.

1 Updated 6 days ago
adnanmokhtar
API & Backend Featured

backend-endpoint

Create REST/GraphQL API endpoint with validation, error handling, and tests. Auto-invoke when user says "add endpoint", "create API", "new route", or "add route".

232 Updated 2 days ago
alekspetrov