automating-api-testing

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

54%

Overall

Validation — 81%

Implementation — 7%

Activation — 100%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
body_output_format	No obvious output/return/format terms detected; consider specifying expected outputs	Warning

	Total	13 / 16 Passed

Implementation

This skill content reads like marketing copy rather than actionable instructions. It describes what the skill does conceptually but provides no executable code, specific commands, tool references, or concrete examples that Claude could actually use to perform API testing. The content assumes Claude needs explanation of basic concepts while failing to provide the specific technical guidance needed.

Suggestions

Replace abstract examples with executable code showing actual test generation (e.g., pytest fixtures, specific HTTP client usage, actual GraphQL test queries)

Add specific tool recommendations and commands (e.g., 'Use httpx for REST: `httpx.get(url, headers=auth_headers)`')

Include a concrete workflow with validation steps: parse spec → generate tests → run tests → validate responses → report failures

Remove explanatory text about what CRUD/GraphQL operations are and replace with copy-paste ready test templates

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 vague steps without any validation checkpoints, specific tools, or error handling. There's no guidance on what to do if parsing fails, tests fail, or contracts don't match.	1 / 3
Progressive Disclosure	The content has reasonable section organization (Overview, How It Works, Examples, Best Practices), but everything is in one file with no references to detailed documentation for specific topics like authentication testing or OpenAPI validation.	2 / 3
	Total	5 / 12 Passed

Activation

100%

This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes comprehensive trigger terms that users would naturally use, 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: 'request generation, validation, comprehensive test coverage', 'analyzes API endpoints', '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 endpoint 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 'CRUD operations' and 'authentication flows'.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on API testing with distinct triggers (REST, GraphQL, OpenAPI, contract tests); unlikely to conflict with general testing or documentation skills due to specific API focus.	3 / 3
	Total	12 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.