api-test-generator
Api Test Generator - Auto-activating skill for Test Automation. Triggers on: api test generator, api test generator Part of the Test Automation skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
0.99xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/api-test-generator/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 severely underdeveloped, essentially just restating the skill name without providing any meaningful detail about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use it, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions like 'Generates unit tests for REST APIs, creates mock server configurations, validates endpoint responses against schemas'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to test an API, generate API test cases, create endpoint tests, or mentions REST/GraphQL testing'
Add file type and technology triggers like '.spec.js', 'Postman', 'pytest', 'Jest', 'integration testing' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Api Test Generator' and 'Test Automation' without describing any concrete actions. There are no specific capabilities listed like 'generates test cases', 'creates mock endpoints', or 'validates API responses'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'Use when...' clause or explicit guidance on when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'api test generator' repeated twice, which is redundant and lacks natural variations users might say like 'API tests', 'test my endpoint', 'generate API test cases', 'REST testing', or 'integration tests'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'API test' is somewhat specific compared to generic 'testing', it could still overlap with other testing skills, code generation skills, or API-related skills. The lack of specific triggers increases conflict risk. | 2 / 3 |
Total | 5 / 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 with no actual content about API test generation. It contains only generic boilerplate describing what a skill should do without any concrete guidance, code examples, or actionable instructions. The content fails all dimensions as it provides zero value beyond placeholder text.
Suggestions
Add executable code examples showing how to generate API tests (e.g., using pytest with requests, or Jest with axios)
Include a concrete workflow: 1) Analyze API endpoint, 2) Generate test cases, 3) Create test file with specific structure, 4) Validate test runs
Provide specific patterns for common API test scenarios: authentication, error handling, response validation, mocking external services
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about API test generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate API tests. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only lists vague capabilities without any sequence of actions for generating API tests. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no structure for discovery or navigation to deeper 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
f17dd51
- 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.