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.

Quality

89%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, concise skill with highly actionable code examples and good structural organization. Its main weakness is the lack of a clear end-to-end workflow with validation steps—particularly for debugging probe failures and verifying correct configuration, which are key use cases mentioned in the skill description. The referenced bundle file (references/implementations.md) is not provided, slightly undermining the progressive disclosure.

Suggestions

Add a brief troubleshooting/validation workflow: e.g., 'curl /health/ready to verify, check kubectl describe pod for probe status, common failure patterns and fixes'

Provide the referenced references/implementations.md bundle file or remove the reference if it doesn't exist

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. The probe types table is a compact reference, code examples are directly useful without explaining what health checks are conceptually, and the best practices/never-do sections are terse bullet points. No unnecessary preamble or concept explanations.	3 / 3
Actionability	Provides fully executable Express.js code with a complete HealthChecker class, route definitions, and copy-paste ready Kubernetes YAML configuration. The code includes concrete patterns for database and Redis checks with proper error handling and status codes.	3 / 3
Workflow Clarity	The skill presents components (probe types, implementation, K8s config) but doesn't sequence them into a clear workflow for implementing health checks end-to-end. There are no validation steps—e.g., how to verify probes are working, test failure scenarios, or debug probe failures mentioned in the skill description.	2 / 3
Progressive Disclosure	References implementations.md for additional language implementations which is good structure, but no bundle files are provided so the reference is unverifiable. The main content is well-organized with clear sections, though the K8s config could arguably be in a reference file to keep the overview leaner.	2 / 3
	Total	10 / 12 Passed

Description

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

Validation

100%

Warnings & errors only

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: 5e92b71

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.