health-check-endpoints
Health check endpoints for liveness, readiness, dependency monitoring. Use for Kubernetes, load balancers, auto-scaling, or encountering probe failures, startup delays, dependency checks, timeout configuration errors.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely covers specific capabilities (health check endpoints for liveness, readiness, dependency monitoring) and provides explicit trigger conditions spanning both infrastructure contexts (Kubernetes, load balancers) and common problem scenarios (probe failures, startup delays). It uses third person voice appropriately and includes natural keywords developers would use when seeking help with health checks.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'health check endpoints', 'liveness', 'readiness', 'dependency monitoring'. These are distinct, well-defined capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Health check endpoints for liveness, readiness, dependency monitoring') and when ('Use for Kubernetes, load balancers, auto-scaling, or encountering probe failures, startup delays, dependency checks, timeout configuration errors') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Kubernetes', 'load balancers', 'auto-scaling', 'probe failures', 'startup delays', 'dependency checks', 'timeout configuration errors'. These are terms developers naturally use when encountering health check issues. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around health check endpoints and probes. The specific mention of liveness/readiness probes, Kubernetes, and probe failures makes it highly distinct and unlikely to conflict with general infrastructure or monitoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides actionable code examples for health check endpoints with good progressive disclosure. Its main weakness is the lack of explicit workflow steps for implementation and verification—there's no guidance on testing probes or validating that the Kubernetes configuration is working correctly. Overall it's a strong reference skill.
Suggestions
Add a brief verification/testing section (e.g., 'curl http://localhost:3000/health/ready to verify, then kubectl describe pod to confirm probe status') to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The probe types table is a compact reference, code examples are focused, and best practices are bullet points without unnecessary explanation. No concepts are over-explained. | 3 / 3 |
Actionability | Provides fully executable JavaScript code for health check endpoints, a complete Kubernetes YAML configuration, and concrete patterns for dependency checking. The code is copy-paste ready with real patterns (database ping, Redis ping, status codes). | 3 / 3 |
Workflow Clarity | While the probe types table clearly explains what each probe does and its failure action, there's no explicit workflow for implementing health checks step-by-step, and no validation/verification steps (e.g., how to test that probes work correctly, how to verify Kubernetes is hitting the endpoints). For a deployment-related skill, missing verification steps is notable. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with the core implementation inline, then appropriately references additional implementations (Flask, Spring Boot, full K8s config) in a separate file. Navigation is well-signaled and one level deep. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.