agentleFS
lordmaculordmacu/nexo-rs/skills/endpoint-check/SKILL.md

Endpoint Check

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

HTTP probe (status + latency) and TLS certificate inspection (expiry, issuer, SANs).

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user wants to verify that an HTTP endpoint is alive, measure its latency, or inspect a TLS certificate's expiry and issuer.

    line 11
  2. Distinctive:

    Verify that a deployment published new code (compare response body)

    line 20
  3. Distinctive:

    No args. Info + limits.

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Endpoint Check

Use when the user wants to verify that an HTTP endpoint is alive, measure its latency, or inspect a TLS certificate's expiry and issuer. Combines naturally with Phase 7 heartbeat for periodic monitoring.

Use when

  • "Is my API up?"
  • "How long until cert X expires?"
  • "Check my endpoints and alert me if something fails" (pair with heartbeat)
  • Verify that a deployment published new code (compare response body)

Do not use when

  • You need complex auth (OAuth, mTLS) — use fetch-url or a dedicated extension
  • You need full body download — use fetch-url
  • It is an internal container health check — use the orchestrator-native check

Tools

status

No args. Info + limits.

http_probe { url, method?, timeout_secs?, follow_redirects?, expected_status? }

  • url required (http/https)
  • method GET (default) or HEAD
  • timeout_secs 1..60 (default 10)
  • follow_redirects default true
  • expected_status optional: returns matches_expected: bool

Returns {status, latency_ms, final_url, content_type, body_preview (≤500 chars), [matches_expected]}.

ssl_cert { host, port?, timeout_secs?, warn_days? }

  • host required
  • port default 443
  • timeout_secs 1..60 (default 10)
  • warn_days default 30 — sets expiring_soon: true below threshold

Returns {subject, issuer, sans, serial_hex, signature_algorithm, chain_length, not_before_unix, not_after_unix, seconds_until_expiry, days_until_expiry, expiring_soon, expired}.

Note: this tool does not validate trust chains — expired/self-signed certs still return parsed metadata. Use expired/expiring_soon to decide.

Execution guidance

  • For periodic monitoring, combine with heartbeat: probe every N minutes and alert when status changes or expiring_soon flips true.
  • For deploy comparisons, store baseline probe output in TaskFlow state_json and diff against new runs.
  • ssl_cert is informational; for actionable alerts, use days_until_expiry with a stricter threshold (e.g., 14 days).
  • Error -32005 timeout means server did not reply within timeout_secs.
  • Errors -32060/-32061 in ssl_cert usually indicate DNS/TCP connect issues.

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.