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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-test-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use it. The description would fail to help Claude distinguish this skill from other testing or API-related skills in a larger skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates unit tests for REST API endpoints, creates mock request/response fixtures, validates API contracts against OpenAPI specs'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks to test an API, generate API tests, create endpoint tests, or mentions REST/GraphQL testing'
Add file type and technology triggers users might mention: '.spec.js', 'Jest', 'Postman', 'integration tests', 'endpoint validation'
| 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. Only mentions it's 'auto-activating' without explaining triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'api test generator' repeated twice. Missing natural variations users would say like 'API tests', 'test my endpoint', 'generate tests for REST API', 'integration tests', etc. | 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 capabilities makes it harder to distinguish from similar tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what an API test generator skill should do without providing any actual guidance, code examples, or workflows. The content fails all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete, executable code examples showing how to generate API tests (e.g., using pytest with requests, or Jest with axios)
Define a clear workflow: 1) Analyze API endpoint, 2) Generate test cases, 3) Create test file with specific structure, 4) Validate test runs
Include specific patterns for common scenarios: authentication tests, error handling tests, response validation
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual test generation instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The entire skill describes what it does abstractly without any executable guidance on how to actually generate API tests. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for generating API tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or supporting documentation. No structure for discovery or navigation. | 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.