api-testing

REST and GraphQL API testing with Playwright. Use when testing APIs, mocking endpoints, validating responses, or integrating API tests with E2E flows.

Quality

83%

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

Quality

Content

82%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 comprehensive, highly executable API-testing reference with copy-paste code across REST, GraphQL, auth, mocking, and validation. Its main weaknesses are length/redundancy and a large inlined body that could be split into more reference files, plus a lack of explicit failure-recovery feedback loops.

Suggestions

Move the auth, mocking, and file-upload sections into separate reference files (as done for graphql-testing.md and schema-validation.md) to shrink the SKILL.md body.

Trim the opening "Comprehensive API testing..." restatement and consolidate the near-identical GET/POST/PUT/DELETE examples into one parameterized pattern plus a per-verb snippet.

Add an explicit feedback loop for test failures (e.g., run → on failure, inspect response body/status → fix assertion or endpoint → re-run) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body leans on executable code with little concept re-explanation, but the opening restatement ("Comprehensive API testing...") and repeated near-identical example patterns across sections add some length that could be trimmed.	4 / 5
Actionability	Every section gives complete, copy-paste-ready TypeScript using Playwright's real API, covering GET/POST/PUT/DELETE, auth, GraphQL, mocking, schema validation, and uploads — matching the fully-executable anchor.	5 / 5
Workflow Clarity	A clear topical progression (Installation → Configuration → usage patterns → Response Validation → Best Practices) with an embedded verify-after-delete checkpoint, but no explicit feedback loop or error-recovery checklist for test failures.	4 / 5
Progressive Disclosure	Two real reference files are clearly signaled in a dedicated References section, but the ~375-line body inlines substantial material (auth, mocking, uploads, all REST verbs) that could live in separate references, leaving a moderate organization gap.	4 / 5
	Total	17 / 20 Passed

Description

83%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 strong, well-formed description that explicitly answers both what the skill does and when to use it, with several concrete trigger phrases. Minor gaps in action coverage and a slight E2E overlap risk keep specificity and distinctiveness at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Quotes several concrete actions — "testing APIs, mocking endpoints, validating responses, or integrating API tests with E2E flows" — but omits others the skill covers (auth, file upload, schema validation), so it falls just short of comprehensive.	4 / 5
Completeness	It states what ("REST and GraphQL API testing with Playwright") and gives an explicit "Use when" clause with multiple concrete triggers, matching the anchor that requires both answered clearly.	5 / 5
Trigger Term Quality	Natural phrases a user would say are present ("testing APIs", "mocking endpoints", "E2E flows"), but synonyms and extension-style triggers (e.g. "endpoint testing", ".graphql") are missing, keeping it below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The REST/GraphQL-with-Playwright niche is distinct, but the "integrating API tests with E2E flows" phrasing creates minor overlap with general Playwright/E2E testing skills.	4 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/api-testing/SKILL.md
Commit: 93ed392

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