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
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 essentially a placeholder with no substantive content. It lacks any concrete actions, natural trigger terms, explicit usage guidance, or distinguishing characteristics. It would be nearly impossible for Claude to reliably select this skill from a pool of available skills based on this description alone.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates API test cases, sends HTTP requests, validates response status codes and payloads, tests authentication flows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to test an API endpoint, debug HTTP requests, validate REST responses, or mentions Postman, cURL, or API testing.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually use, such as 'REST API', 'HTTP request', 'endpoint testing', 'API validation', 'status codes'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is an 'Api Testing Helper' for 'API Development' without describing what it actually does—no mention of specific capabilities like sending requests, validating responses, generating test cases, etc. | 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 trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'api testing helper' repeated twice. These are not natural phrases a user would say; users would more likely say things like 'test my API', 'send a request', 'check endpoint', 'REST', 'HTTP', 'Postman', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'API Development' and 'API Testing Helper' could overlap with numerous other skills related to APIs, testing, development, HTTP clients, etc. There are no distinct triggers or niche identifiers. | 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 template/placeholder with no substantive content. It contains only generic boilerplate text that repeats the skill name without providing any actual guidance on API testing — no code, no tools, no workflows, no examples. It would provide zero value to Claude beyond what it already knows.
Suggestions
Add concrete, executable code examples for common API testing scenarios (e.g., using curl, httpie, pytest, or Postman collections to test REST/GraphQL endpoints).
Define a clear workflow for API testing: e.g., 1) Identify endpoints, 2) Write test cases, 3) Execute tests, 4) Validate responses against expected schemas, 5) Report results — with specific commands at each step.
Remove all boilerplate filler ('This skill provides automated assistance for...') and replace with actionable content such as example request/response pairs, authentication setup, and error handling patterns.
Include references to specific tools and libraries (e.g., pytest + requests, REST Client VS Code extension, OpenAPI validation tools) with concrete usage examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'api testing helper' excessively, and provides zero substantive information about API testing. | 1 / 3 |
Actionability | There are no concrete code examples, commands, tool references, or executable guidance whatsoever. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow, sequence, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or any actionable process. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external resources, and the content itself is a shallow placeholder with no meaningful structure or navigation to deeper material. | 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
3a2d27d
- 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.