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.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-pr-commentsSkill
- build-and-scan-container-imageSkill
- execute-database-migrationSkill
- generate-adrSkill
- generate-service-documentationSkill
- get-pr-commentsSkill
- incident-triageSkill
- install-dev-toolsSkill
- prepare-releaseSkill
- remediate-dependency-vulnerabilitiesSkill
- review-configurationSkill
- twg-agentic-searchSkill
- twg-artifactsSkill
- twg-code-reviewSkill
- twg-confluenceSkill
- twg-context-discoverySkill
- twg-engineering-workSkill
- twg-jira-resolve-merged-workSkill
- twg-jiraSkill
- twg-operational-healthSkill
- twg-responsibility-routingSkill
- twgSkill
- twg-space-creationSkill
- twg-status-rollupsSkill
- validate-and-deploy-iacSkill
- validate-and-deploy-kubernetesSkill
- validate-documentationSkill
- validate-github-actionsSkill
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
- Distinctive: line 30
Run connectivity, readiness, dependency, and smoke checks in that order.
- Distinctive: line 39
Use timeouts and bounded retries.
- Distinctive: line 40
Never issue requests to unapproved or reserved destinations.
- Distinctive: line 41
Do not send destructive requests as health checks.
- Distinctive: line 43
Do not treat a passing health endpoint as proof that user workflows work.
≈ “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.
Files
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: defaultfalse; enable only with explicit authorization for a local target.checksPath: optional check definitions; default./.service-checks.mode:quick,standard, orcomprehensive; defaultstandard.checkDependencies: defaulttrue.includeMetrics: defaulttrue.rollbackOnFailure: defaultfalse.rollbackApproval: defaultfalse; must be explicitly confirmed before rollback.timeout: default5m.format:summaryorjson; defaultsummary.
Workflow
- 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. - Run connectivity, readiness, dependency, and smoke checks in that order.
- Capture bounded latency, status, error, and recent-log evidence.
- Compare results with declared SLOs when available.
- Report failures and likely ownership; never infer recovery from one signal.
- Trigger rollback only when
rollbackOnFailureandrollbackApprovalare 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.
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
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.

