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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-health-checkerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It only contains the skill name, a duplicate trigger term, and a generic category label. It provides no information about what the skill actually does or when it should be selected over other skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Checks API endpoint availability, monitors response times, validates HTTP status codes, tests authentication flows'
Add a 'Use when...' clause with natural trigger terms like 'Use when checking if an API is working, monitoring endpoint health, diagnosing API connectivity issues, or when user mentions API status, uptime, or availability'
Remove the duplicate trigger term and expand with variations users would naturally say: 'health check', 'API status', 'is the API working', 'endpoint monitoring', 'service availability'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Api Health Checker' and category 'API Integration'. There are no specific capabilities listed like 'checks endpoint status', 'monitors response times', or 'validates API availability'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). Only provides category metadata. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api health checker' repeated twice, which is the skill name itself. Missing natural user phrases like 'check if API is working', 'endpoint status', 'API down', 'service availability', or 'ping API'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Integration' is extremely generic and could conflict with any API-related skill. Without specific capabilities or triggers, this could incorrectly activate for general API work, API testing, API documentation, etc. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It consists entirely of generic placeholder text that could apply to any skill topic. There is no actionable guidance, no code examples, no specific information about API health checking, and nothing that would help Claude perform this task.
Suggestions
Add concrete 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, how to interpret results, and what actions to take on failures
Include specific patterns for common scenarios: REST API health endpoints, retry logic, alerting thresholds, and circuit breaker patterns
Remove all generic boilerplate text and replace with actual technical content specific to API health checking
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of what an API health check actually involves. The content only describes what the skill claims to do without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no structure beyond generic headings. There are no references to detailed materials, no examples, and no actual content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.