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.
39
Quality
7%
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
7%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 that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or natural trigger scenarios. The redundant trigger terms and complete absence of action verbs or 'Use when' guidance make this description ineffective for Claude to choose appropriately among multiple skills.
Suggestions
Add specific actions the skill performs, e.g., 'Checks API endpoint availability, measures response times, validates HTTP status codes, and monitors service health'
Include a 'Use when...' clause with natural trigger terms like 'check if API is working', 'test endpoint health', 'API status', 'service availability', 'is the server responding'
Remove the redundant trigger term and expand with variations users would naturally say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Api Health Checker' and 'API Integration' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does (e.g., ping endpoints, check response times, validate status codes). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'api health checker' repeated twice, which is redundant and overly specific. Missing natural variations users would say like 'check API status', 'is the API working', 'endpoint health', 'API uptime', or 'service availability'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API health checker' is a somewhat specific domain, the lack of detail about what distinguishes it from other API-related skills (testing, monitoring, debugging) creates potential overlap. The 'API Integration' category is broad. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual content. It describes what an API health checker skill would do without providing any concrete implementation, code examples, health check patterns, or actionable guidance. The entire body could be replaced with a single sentence and lose no information.
Suggestions
Add executable code examples showing how to implement API health checks (e.g., endpoint ping, response time measurement, status code validation)
Define a clear workflow for health checking: what to check, in what order, and how to interpret/report results
Include specific patterns like retry logic, timeout handling, and alerting thresholds with concrete values
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no specific value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The entire skill describes what it does abstractly without showing how to actually check API health. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for performing API health checks. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there are no references to detailed documentation and the sections themselves contain no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
0c08951
- 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.