agentleFS
ByronScottJonesByronScottJones/Agents/skills/verify-service-health/SKILL.md

verify-service-health

Skill7 starsChanged 2 months agoMITView on GitHub

Use when verifying a service deployment, readiness, dependencies, smoke flows, logs, metrics, or rollback signals. Runs bounded read-only checks by default and never triggers rollback without explicit confirmation.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Run connectivity, readiness, dependency, and smoke checks in that order.

    line 30
  2. Distinctive:

    Use timeouts and bounded retries.

    line 39
  3. Distinctive:

    Never issue requests to unapproved or reserved destinations.

    line 40
  4. Distinctive:

    Do not send destructive requests as health checks.

    line 41
  5. Distinctive:

    Do not treat a passing health endpoint as proof that user workflows work.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Verify Service Health

Turn deployment and observability guidance into a repeatable health gate.

Parameters

  • serviceURL: required unless checks use a local target.
  • approvedHosts: required for remote checks; reserved and private destinations are blocked by default.
  • allowAuthorizedLocalTarget: default false; enable only with explicit authorization for a local target.
  • checksPath: optional check definitions; default ./.service-checks.
  • mode: quick, standard, or comprehensive; default standard.
  • checkDependencies: default true.
  • includeMetrics: default true.
  • rollbackOnFailure: default false.
  • rollbackApproval: default false; must be explicitly confirmed before rollback.
  • timeout: default 5m.
  • format: summary or json; default summary.

Workflow

  1. Validate the target URL against approvedHosts; block loopback, link-local, metadata, private-network, and other reserved destinations unless an authorized local target is explicitly enabled.
  2. Run connectivity, readiness, dependency, and smoke checks in that order.
  3. Capture bounded latency, status, error, and recent-log evidence.
  4. Compare results with declared SLOs when available.
  5. Report failures and likely ownership; never infer recovery from one signal.
  6. Trigger rollback only when rollbackOnFailure and rollbackApproval are both true and a documented rollback path exists.

Safety

  • Use timeouts and bounded retries.
  • Never issue requests to unapproved or reserved destinations.
  • Do not send destructive requests as health checks.
  • Redact authorization headers and sensitive response fields.
  • Do not treat a passing health endpoint as proof that user workflows work.

Output

Return target, check results, latency, dependency status, evidence timestamps, failed checks, likely owners, rollback recommendation, and limitations.

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.