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 is an extremely weak description that provides virtually no useful information for skill selection. It lacks any concrete actions, meaningful trigger terms, explicit 'when to use' guidance, and distinguishing characteristics. It reads as a template placeholder rather than a functional skill description.
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 responses, write integration tests for REST/GraphQL APIs, or mentions tools like curl or Postman.'
Differentiate from other API-related skills by specifying the unique scope, e.g., focus on testing vs. design vs. documentation, and mention supported protocols or frameworks.
| 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 (e.g., send requests, validate responses, generate test cases). | 1 / 3 |
Completeness | Neither the 'what does this do' nor the 'when should Claude use it' questions are meaningfully answered. The description only states a category and a redundant trigger term, with no explicit guidance on when to activate. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('api testing helper, api testing helper'). There are no natural user keywords like 'test endpoint', 'HTTP request', 'REST API', 'status code', 'Postman', or 'curl'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'API Development' could overlap with API design, API documentation, API client generation, or any other API-related skill. Nothing distinguishes this from other potential API 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 an empty template/placeholder with no actual content. It repeats the phrase 'api testing helper' numerous times without ever defining what it means, how to do it, or providing any code, commands, or concrete guidance. It adds zero value beyond what the skill's title already conveys.
Suggestions
Add concrete, executable code examples for API testing (e.g., using curl, httpie, pytest, or Postman collections) with specific request/response patterns.
Define a clear workflow for API testing: e.g., 1) Set up test environment, 2) Write test cases, 3) Run tests, 4) Validate responses against expected schemas, 5) Report results.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that just repeat the skill name and replace with actionable content covering REST endpoint testing, authentication testing, error handling validation, etc.
Include specific tool recommendations with installation commands and example configurations (e.g., pytest + requests, or a curl-based testing approach with JSON schema validation).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'api testing helper' excessively, and provides zero substantive information about how to actually perform 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 | The content is a flat, repetitive structure with no references to external files, no meaningful sections, and no organized hierarchy of information. There is nothing to progressively disclose because there is no substantive content. | 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.