CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is api-testing in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 reference dominated by executable TypeScript examples, with genuine one-level-deep reference files for advanced GraphQL patterns and schema validation. Its main cost is length: redundant basic CRUD examples and inline content that duplicates the reference files keep it from being lean, and it lacks explicit validation-checkpoint workflows beyond the built-in expect() assertions.

Suggestions

Collapse the four near-identical CRUD sections (GET/POST/PUT/DELETE) into one compact example or a short table of request methods, since Claude already knows Playwright's request API shape.

Replace the inline Ajv schema-validation example with a pointer to references/schema-validation.md (mirroring how advanced GraphQL patterns are handled), keeping only a one-line inline teaser.

Trim the GraphQL basics (query/mutation) to a single example and move detail into references/graphql-testing.md so SKILL.md reads as an overview rather than a full tutorial.

DimensionReasoningScore

Conciseness

The body is code-dominant with minimal prose, but the four near-identical CRUD examples (GET/POST/PUT/DELETE) and the inline Ajv example (duplicating references/schema-validation.md) re-teach basics Claude already knows and could be tightened or pushed to the reference files.

3 / 5

Actionability

Nearly all code is copy-paste ready and covers the common cases (auth, GraphQL query/mutation, mocking, upload, schema validation), but the 'GraphQL with auth' snippet references a `token` never defined in its scope, leaving a minor gap versus fully self-contained examples.

4 / 5

Workflow Clarity

Installation, Configuration, and Quick Start form a clear getting-started sequence, and assertions are embedded in every example (the DELETE test even verifies the follow-up 404), but there are no explicit checkpoints or error-recovery loops beyond the Best Practices list.

4 / 5

Progressive Disclosure

Both referenced files exist, are one level deep, and are clearly signaled with one-line descriptions in a References section; however, the ~380-line body inlines GraphQL basics and an Ajv example that duplicate the reference files instead of pointing to them, leaving minor organization gaps.

4 / 5

Total

15

/

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 description that explicitly answers both what the skill does and when to use it, with concrete trigger phrases and a clearly defined Playwright API-testing niche. The only weaknesses are minor: capability coverage could be broader and the generic 'testing APIs' trigger slightly raises overlap risk with adjacent testing skills.

DimensionReasoningScore

Specificity

Names the domain and tool ('REST and GraphQL API testing with Playwright') along with several concrete actions ('mocking endpoints, validating responses'), matching the 'several specific actions with minor gaps' anchor; not a 5 because capabilities like authentication, file upload, and schema validation are absent from the description.

4 / 5

Completeness

The first sentence clearly states what the skill does and the explicit 'Use when testing APIs, mocking endpoints, validating responses, or integrating API tests with E2E flows' clause provides concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say ('testing APIs', 'mocking endpoints', 'E2E flows') plus REST/GraphQL/Playwright keywords give good coverage; not a 5 because common variations like 'endpoint testing', 'integration tests', or 'API specs' are missing.

4 / 5

Distinctiveness Conflict Risk

The Playwright API-testing niche is mostly distinct, but the broad trigger 'testing APIs' could also fire for general API-testing or Playwright E2E skills, giving minor overlap with closely related skills rather than minimal conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/api-testing/SKILL.md

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.