api-testing-helper
Api Testing Helper - Auto-activating skill for API Development. Triggers on: api testing helper, api testing helper Part of the API Development skill category.
33
Quality
0%
Does it follow best practices?
Impact
95%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/api-testing-helper/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 severely deficient across all dimensions. It functions as a placeholder rather than a functional skill description, providing only the skill name and category without any concrete capabilities, actions, or trigger guidance. Claude would have no meaningful basis to select this skill appropriately.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates API test cases, validates response schemas, tests authentication flows, creates mock endpoints'
Include a 'Use when...' clause with natural trigger terms like 'test API', 'API endpoint', 'REST testing', 'HTTP request validation', 'mock server', 'API response'
Differentiate from other API skills by specifying the testing focus, e.g., 'Use when testing or validating API endpoints, not for API design or documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Api Testing Helper' and 'Auto-activating skill for API Development' are completely vague with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api testing helper' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'test endpoint', 'API request', 'REST', 'HTTP', 'postman', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'API Development' could overlap with many skills. No specific niche is carved out, and the description provides no distinguishing characteristics from other API-related skills. | 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 entirely meta-content describing what a skill would do rather than providing any actual guidance for API testing. It contains no executable code, no specific techniques, no tool recommendations, and no concrete instructions. The content is essentially a placeholder template that fails every dimension of the rubric.
Suggestions
Add concrete, executable code examples for common API testing scenarios (e.g., using curl, httpie, or Python requests library)
Include specific testing patterns such as authentication testing, error handling validation, and response schema verification
Provide a clear workflow for API testing: setup -> write tests -> execute -> validate -> report
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to test APIs. The entire content describes what the skill does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation. | 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
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.