api-health-checker
Api Health Checker - Auto-activating skill for API Integration. Triggers on: api health checker, api health checker Part of the API Integration skill category.
34
0%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/api-health-checker/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be nearly impossible for Claude to correctly choose this skill from a pool of similar API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Checks API endpoint availability, monitors response times, validates health check endpoints, and reports service status codes.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to check if an API is up, monitor endpoint health, verify service availability, or diagnose API connectivity issues.'
Include natural keyword variations users might say, such as 'API status', 'endpoint health', 'service uptime', 'ping API', 'API down', 'health check endpoint', '.health', 'status page'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Api Health Checker' is a name, not a description of capabilities. There are no specific actions like 'checks endpoint availability', 'monitors response times', or 'validates API status codes'. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states the skill name, a redundant trigger list, and a category label. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api health checker, api health checker'). Missing natural user terms like 'check API status', 'endpoint monitoring', 'API uptime', 'health endpoint', 'service availability', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Integration' is extremely broad and could overlap with any API-related skill. Nothing distinguishes this from other API tools, and the lack of specific capabilities makes conflict with similar skills very likely. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual instructional content. It is entirely composed of boilerplate meta-descriptions that repeat 'api health checker' without ever providing concrete guidance, code examples, or actionable steps. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for implementing an API health checker (e.g., a Python script using requests to check endpoint status, parse responses, and report health).
Define a clear workflow with specific steps: configure endpoints, implement health check logic, handle failures/retries, set up alerting, and include validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical content covering patterns like retry logic, timeout handling, and status aggregation.
If the topic warrants depth, add references to separate files for advanced patterns (e.g., distributed health checks, dashboard integration) rather than keeping everything vague in one file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'api health checker' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of API health check implementations. The content only describes what the skill could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. Sections like 'When to Use', 'Capabilities', and 'Example Triggers' all restate the same vague information without any references to detailed materials or useful navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.