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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%Weight 40%Scale 1-5

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

A tight, highly actionable skill body: executable code, a clear probe taxonomy, and well-structured one-level-deep references to real bundle files. The only gap is the absence of an explicit verify/validate checkpoint for confirming probe behavior, which keeps workflow clarity at 4 rather than 5.

Dimension	Reasoning	Score
Conciseness	The body is lean: a probe-type table, executable code, and terse best-practice bullets with no padding or explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides complete, copy-paste-ready Express code and Kubernetes YAML covering the common cases, plus concrete do/don't lists; the guidance is directly executable rather than abstract.	5 / 5
Workflow Clarity	The probe-type table maps each probe to its purpose and failure action, giving a clear mental sequence for choosing/implementing probes, but there is no explicit validation step or feedback loop for verifying the endpoints behave as expected before relying on them.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview with one-level-deep, clearly signaled references (references/implementations.md) that are real files, and additional languages/configs are appropriately offloaded to that file; navigation is easy.	5 / 5
	Total	19 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid, third-person description that states concrete capabilities and includes an explicit 'Use for' trigger clause with natural keywords. It is one notch below top marks due to slightly broad trigger phrasing and minor synonym/extension gaps rather than any substantive weakness.

Suggestions

Tighten the trigger clause with sharper user phrasing, e.g. 'Use when configuring Kubernetes liveness/readiness/startup probes, debugging probe failures, or wiring health checks into load balancers and autoscalers.'

Add common synonyms/extensions users actually say (k8s, livenessProbe, readinessProbe, healthz, /healthz) to improve trigger-term coverage.

Drop the trailing catch-all 'timeout configuration errors' which broadens scope and raises overlap risk with general configuration skills.

Dimension	Reasoning	Score
Specificity	Names the domain (liveness, readiness, dependency monitoring) and several concrete capabilities, but coverage is a list of probe/use scenarios rather than fully enumerated actions; minor gaps keep it just below a 5.	4 / 5
Completeness	Clearly states what the skill does and provides an explicit 'Use for ...' trigger clause covering several scenarios; the when is present and concrete but is a comma list rather than a sharply scoped trigger phrase, so it falls just short of a 5.	4 / 5
Trigger Term Quality	Includes natural terms users would say (Kubernetes, load balancers, auto-scaling, probe failures, startup delays) with good coverage, though it lacks some common synonyms/extensions like k8s, livenessProbe/readinessProbe, or healthz.	4 / 5
Distinctiveness Conflict Risk	The Kubernetes/probe framing is a fairly distinct niche with low conflict risk against unrelated skills, but 'dependency monitoring' and 'timeout configuration errors' are broad enough to risk minor overlap with general observability skills.	4 / 5
	Total	16 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/health-check-endpoints/skills/health-check-endpoints/SKILL.md
Commit: 84802a4

Reviewed: 3 days 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.