tessl-labs/health-checks
Health check and readiness endpoints for web services — liveness probes,
97
99%
Does it follow best practices?
Impact
94%
3.61xAverage score across 4 eval scenarios
Passed
No known issues
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (liveness probes, dependency checks, startup/shutdown), uses natural terminology that developers would actually search for, and includes an explicit 'Use when...' clause with clear deployment contexts. The description effectively carves out a distinct niche in the health monitoring/observability space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'liveness probes, dependency checks, and graceful startup/shutdown' along with the domain 'Health check and readiness endpoints for web services'. | 3 / 3 |
Completeness | Clearly answers both what ('Health check and readiness endpoints... liveness probes, dependency checks, graceful startup/shutdown') and when ('Use when building any backend service that will be deployed behind a load balancer, in containers, or in any environment that monitors service health'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'health check', 'readiness endpoints', 'liveness probes', 'load balancer', 'containers', 'service health', 'backend service', 'startup/shutdown'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on health monitoring infrastructure with distinct triggers like 'liveness probes', 'readiness endpoints', and deployment contexts; unlikely to conflict with general web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates best practices across all dimensions. It's concise yet comprehensive, provides executable code in multiple languages, clearly explains the workflow with validation checkpoints, and is well-organized with a practical checklist. The 'Important Details' section adds significant value by covering common pitfalls without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with no unnecessary explanation of basic concepts. The skill assumes Claude knows what load balancers, containers, and health checks are, jumping straight to actionable content. | 3 / 3 |
Actionability | Provides complete, executable code examples in three languages (TypeScript, Python, Go), plus ready-to-use Kubernetes YAML and Dockerfile configurations. All examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear separation of liveness vs readiness with explicit rationale, graceful startup pattern with gating mechanism, and a comprehensive checklist at the end. The 'Important Details' section provides explicit validation guidance (503 for not ready, don't check external services in liveness). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Two Endpoints, Implementation, Graceful Startup, Kubernetes Configuration, Important Details, Checklist). Content is appropriately contained in a single file given the scope, with a reference to an external verifier. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents