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".
63
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/api-test-automation/skills/api-test-automation/SKILL.mdQuality
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 strong skill description that clearly articulates specific capabilities, provides explicit trigger guidance with natural user terms, and distinguishes itself well from other potential skills. It covers both the 'what' and 'when' comprehensively, listing concrete actions like test suite generation, CRUD coverage, and response validation alongside clear trigger phrases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: 'request generation', 'validation', 'test coverage for REST and GraphQL APIs', 'analyzes API endpoints', 'generates test suites covering CRUD operations, authentication flows, and security aspects', and 'validates response status codes, headers, and body structure'. | 3 / 3 |
Completeness | Clearly answers both 'what' (automates API endpoint testing, generates test suites, validates responses) and 'when' (explicit 'Use this skill when the user mentions...' clause with specific trigger phrases, plus 'It is used when the user requests API testing, contract testing, or validation against OpenAPI specifications'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'API testing', 'REST API tests', 'GraphQL API tests', 'contract tests', 'OpenAPI validation', 'CRUD operations', 'authentication flows'. These are terms users would naturally use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around API testing specifically, with distinct triggers like 'contract tests', 'OpenAPI validation', 'REST API tests', and 'GraphQL API tests' that are unlikely to conflict with general testing or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%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 like a marketing description rather than actionable instructions for Claude. It lacks any concrete code examples, specific tool/framework references, executable commands, or validation steps. The content explains what the skill does conceptually but never shows Claude how to actually generate or execute API tests.
Suggestions
Add concrete, executable code examples showing actual generated test output (e.g., a complete pytest or Jest test file for a sample REST endpoint with assertions on status codes, headers, and response body).
Specify the exact tools and frameworks to use (e.g., pytest + requests, Jest + supertest, or specific GraphQL testing libraries) with installation commands and configuration.
Replace the abstract 'How It Works' steps with a concrete workflow including validation checkpoints, such as: parse OpenAPI spec → generate test file → run tests → check results → fix failures → re-run.
Remove the 'When to Use This Skill', 'Best Practices', and 'Integration' sections as they add no actionable value, and replace them with concrete examples showing input API definitions and expected test output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with unnecessary explanations. Sections like 'How It Works', 'When to Use This Skill', 'Best Practices', and 'Integration' explain things Claude already knows or repeat the skill description. The 'Overview' sentence tells Claude what it's 'empowered' to do rather than instructing it. Nearly every section describes rather than instructs. | 1 / 3 |
Actionability | There is no executable code, no concrete commands, no specific test frameworks, no example test output, and no copy-paste ready snippets. The examples describe what 'the skill will' do in abstract terms ('Generate a test suite covering CRUD operations') without showing any actual generated test code, assertions, or tool usage. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three abstract steps (analyze, generate, execute) with no concrete commands, validation checkpoints, or error recovery. The examples similarly describe outcomes without specifying how to achieve them. There are no validation or verification steps for the generated tests. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, there are no bundle files or references to external documents, and the content is a monolithic set of vague descriptions that could benefit from splitting actionable details into referenced files. For a skill with no bundle, the organization is adequate but the content itself doesn't warrant deeper structure. | 2 / 3 |
Total | 5 / 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.
- Commit
13d35b8
- 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.