api-testing

HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-testing/skills/api-testing/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable API-testing cookbook with executable examples across both ecosystems. It loses points mainly for an implicit (rather than explicit) testing workflow and minor redundancy in the intro and best-practices list.

Suggestions

Add a short "Test workflow" section that sequences the steps explicitly (write request → assert status → validate body → run and read failures), with a checkpoint to re-run on failure.

Trim the redundant intro line and drop obvious items from Best Practices (e.g. "Validate status codes first") that Claude already knows, to push conciseness to 5.

If the file keeps growing, move GraphQL/Performance details into a one-level-deep reference file and signal it from SKILL.md to lift progressive disclosure to 5.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable code with minimal prose, but the opening line restates the description and the Best Practices list includes guidance Claude already knows ("Validate status codes first", "Test both happy path and error cases"), so it is not a 5.	4 / 5
Actionability	Code is fully executable and copy-paste ready — complete imports, real method chains, and concrete assertions covering GET/POST/PUT/DELETE, auth, file upload, GraphQL, and performance, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Content is organized into clear topical sections, but there is no explicit sequenced workflow with validation checkpoints for writing/running tests; the implicit test-then-assert flow is never made explicit.	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers and easy navigation, no nested references, and no bundle files to mismanage; minor gaps only (e.g. GraphQL/Performance sections could live in separate reference files), keeping it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, framework-named description that clearly conveys what the skill does across two language ecosystems. Its main weakness is the absence of an explicit "Use when…" trigger clause, which caps completeness at 3.

Suggestions

Append an explicit trigger clause, e.g. "Use when testing HTTP/REST or GraphQL APIs, validating request/response behavior, or writing API auth and error-handling tests."

Add common user phrasings or file/extension cues (e.g. "endpoint tests", "API integration tests") to lift trigger-term coverage toward 5.

Clarify when this skill applies versus sibling testing skills (vitest-testing, playwright-testing) to reduce overlap ambiguity.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — "Test REST APIs, GraphQL, request/response validation, authentication, and error handling" — with both TS (Supertest) and Python (httpx, pytest) coverage, matching the comprehensive-coverage anchor.	5 / 5
Completeness	The description gives a clear "what" but contains no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good keyword coverage including natural terms ("API testing", "REST APIs", "GraphQL", "authentication") and tool names ("Supertest", "httpx", "pytest"); a few natural variations (e.g. "endpoints") are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The named frameworks (Supertest, httpx, pytest) carve a clear niche with minimal conflict risk, but it overlaps with closely related testing skills (vitest-testing, playwright-testing noted in See Also), keeping it just below 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/api-testing/skills/api-testing/SKILL.md
Commit: 84802a4

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.