automating-api-testing
This skill automates API endpoint testing, including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs. It is used when the user requests API testing, contract testing, or validation against OpenAPI specifications. The skill analyzes API endpoints and generates test suites covering CRUD operations, authentication flows, and security aspects. It also validates response status codes, headers, and body structure. Use this skill when the user mentions "API testing", "REST API tests", "GraphQL API tests", "contract tests", or "OpenAPI validation".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill automating-api-testing68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes comprehensive natural trigger terms, explicitly addresses both what the skill does and when to use it, and carves out a distinct niche in API testing that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automates API endpoint testing', 'request generation', 'validation', 'generates test suites covering CRUD operations, authentication flows, and security aspects', 'validates response status codes, headers, and body structure'. | 3 / 3 |
Completeness | Clearly answers both what (automates API testing, generates test suites, validates responses) AND when with explicit 'Use this skill when...' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'API testing', 'REST API tests', 'GraphQL API tests', 'contract tests', 'OpenAPI validation', plus domain terms like 'REST', 'GraphQL', and 'OpenAPI specifications'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API testing with distinct triggers like 'REST API tests', 'GraphQL API tests', 'contract tests', and 'OpenAPI validation' that are unlikely to conflict with general testing or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads more like marketing copy than actionable instructions. It describes capabilities abstractly without providing any executable code, specific commands, or concrete examples that Claude could actually use. The content explains concepts Claude already understands while omitting the specific implementation details that would make this skill useful.
Suggestions
Replace abstract examples with actual executable test code (e.g., show a complete pytest or Jest test file for a sample endpoint)
Add specific commands for parsing OpenAPI specs and generating tests (e.g., actual Python/JS code snippets)
Include concrete validation steps with example assertions for status codes, headers, and response bodies
Remove explanatory text about what CRUD operations and GraphQL queries are - Claude knows these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what CRUD operations are, what GraphQL queries/mutations are). Phrases like 'This skill empowers Claude' and 'ensures thorough validation' are filler that add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The examples describe what the skill 'will do' abstractly rather than showing actual test code, API calls, or specific commands Claude should execute. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three high-level steps, but lacks specific validation checkpoints, error handling, or feedback loops. There's no guidance on what to do if test generation fails or how to verify test correctness. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline with no references to external files for detailed API schemas, test templates, or advanced configurations. The structure exists but could benefit from splitting detailed content. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.