SkillAgentSearch skills...

endpoint-validator

Deterministic API endpoint validation with pass/fail reporting.

Install / Use

npx skills add notque/vexjoy-agent --skill endpoint-validator

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Category

Operations

Supported Platforms

Universal

Our assessment of endpoint-validator

endpoint-validator scores 82/100 on our quality scale, 633rd of 762 Operations skills we index.

Its SKILL.md is 4.2 KB long, well organised into 9 sections with 3 code examples: a solid amount of guidance for an agent.

It has 425 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 12 days ago, so endpoint-validator is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

endpoint-validator compared with similar skills

All 4 of these similar skills score higher than endpoint-validator; compare them before choosing.

SkillScoreStarsUpdatedFormat
endpoint-validator (this skill)by notque8242512d agoSKILL.md
Agent-Reachby Panniantong10097.6ktodayCLAUDE.md
headroomby headroomlabs-ai10075.4ktodayCLAUDE.md
Scraplingby D4Vinci10087.7ktodayMCP Server
crawl4aiby unclecode10085.6ktodayMCP Server

Frequently asked questions

How do I install endpoint-validator?
Run npx skills add notque/vexjoy-agent --skill endpoint-validator. The install tabs above show the steps for each supported agent.
Which AI agents does endpoint-validator work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is endpoint-validator safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is endpoint-validator still maintained?
The repository was last updated 12 days ago, so endpoint-validator is actively maintained.

name: endpoint-validator promoted_to: deploy description: "Deterministic API endpoint validation with pass/fail reporting." user-invocable: false allowed-tools:

  • Bash
  • Read
  • Write
  • Glob
  • Edit routing: triggers:
    • "validate endpoints"
    • "smoke test API"
    • "health check endpoints"
    • "test endpoint"
    • "check API"
    • "smoke test" category: infrastructure not_for: "process/service uptime or daemon liveness (use service-health-check); only HTTP/API endpoint request validation" pairs_with:
    • assessment
    • testing

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} in base_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:

  1. Send request with configured method and timeout.
  2. Check status code against expect_status. Mismatch -> FAIL.
  3. If expect_key set, parse JSON and check key exists. Missing/invalid -> FAIL.
  4. If max_time set and elapsed exceeds it -> SLOW.
  5. 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 1

Exit 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; }
done

Related Skills

View on GitHub
GitHub Stars425
CategoryOperations
Updated12d ago
Forks48

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions