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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill health-check-endpointsOverall
score
92%
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It clearly specifies the capability (health check endpoints with three specific types), provides explicit 'Use for' guidance with numerous natural trigger terms covering both infrastructure contexts (Kubernetes, load balancers) and problem scenarios (probe failures, timeout errors). The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'liveness, readiness, dependency monitoring' as distinct health check types, clearly describing what the skill does. | 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'). | 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' - all terms users naturally use when dealing with health check issues. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on health check endpoints with distinct triggers like 'probe failures', 'liveness', 'readiness' that are 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 strong, well-crafted skill that efficiently covers health check implementation with executable code and proper Kubernetes configuration. The content is appropriately concise and actionable. The main gap is the lack of explicit troubleshooting workflow or validation steps for when probes fail or need debugging.
Suggestions
Add a brief troubleshooting workflow section with steps to diagnose probe failures (e.g., 'If readiness fails: 1. Check logs, 2. Test endpoint manually with curl, 3. Verify dependency connectivity')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. The table format for probe types is information-dense, and the code examples are minimal yet complete. No padding or concepts Claude would already know. | 3 / 3 |
Actionability | Provides fully executable JavaScript code with a complete HealthChecker class, Express routes, and copy-paste ready Kubernetes YAML configuration. Concrete examples for database and Redis checks. | 3 / 3 |
Workflow Clarity | The probe types table clearly explains the sequence and purpose, but there's no explicit validation workflow for testing health endpoints or debugging probe failures. Missing feedback loop for when probes fail during setup. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from concepts to implementation to configuration. Additional implementations appropriately referenced in a separate file with clear signaling of what's contained there. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.