Name: api-test-suite-builder
Rating: 60.8 (1 reviews)
Author: alirezarezvani

api-test-suite-builder

Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

Quality

71%

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 ./.gemini/skills/api-test-suite-builder/SKILL.md

The canonical home for this skill is api-test-suite-builder in alirezarezvani/claude-skills

Quality

Content

65%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.

The body is well-structured and highly actionable, with concrete commands and test matrices that assume Claude's competence. Its weaknesses are a missing validation step in the batch generation workflow and a broken reference to a non-existent example file, both of which hold back the workflow and disclosure dimensions.

Suggestions

Add a verification checkpoint to the generation workflow, e.g. run the generated tests and confirm each detected route has at least one covering test before finishing.

Either create references/example-test-files.md with the promised example tests or remove the dangling 'See references/example-test-files.md' pointer.

Move the per-framework route-detection command blocks or the full test matrices into a references file so SKILL.md stays a lean overview with one-level-deep, real references.

Dimension	Reasoning	Score
Conciseness	Largely efficient with dense, useful bash snippets and tables and no padding of concepts Claude already knows; a little redundancy between Core Capabilities, Common Pitfalls, and Best Practices could be trimmed.	4 / 5
Actionability	Provides executable per-framework route-detection commands and concrete auth/input test matrices with expected status codes, but the 'Example Test Files' pointer references a non-existent file and the scan commands are illustrative rather than complete generators.	4 / 5
Workflow Clarity	The 'Generating Tests from Route Scan' section gives a clear six-step sequence, but this batch generation workflow lacks any validation/verification checkpoint (no running of generated tests, no coverage confirmation), which caps batch workflows at 3 per the rubric.	3 / 5
Progressive Disclosure	Section structure is clear, but the only external reference ('references/example-test-files.md') points to a file that does not exist in the bundle, and the bulk of the material is inlined in SKILL.md rather than appropriately split.	3 / 5
	Total	14 / 20 Passed

Description

78%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.

The description is concise, action-oriented, and provides explicit trigger guidance for a well-defined niche, distinguishing it cleanly from adjacent skills. The main weakness is that the 'what' is folded into the 'when' clauses rather than stated as a standalone capability, leaving it slightly short of a fully explicit what-and-when pairing.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('generate API tests, create integration test suites, test REST endpoints, or build contract tests') with only minor coverage gaps such as omitted frameworks or the scan-based nature.	4 / 5
Completeness	Explicit 'Use when...' triggers are present and concrete, and the what is conveyed through the trigger clauses rather than a separate third-person capability statement, so the 'what' could be more explicit.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('generate API tests', 'integration test suites', 'test REST endpoints', 'build contract tests'), missing a few synonyms like 'API testing' or 'endpoint tests'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (API test generation) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/api-test-suite-builder/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour 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.