CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/schemathesis-fuzzing

Use for any request to generate API tests from an OpenAPI or GraphQL schema, or to find inputs that make an API return 500 that hand-written tests miss: Schemathesis fuzzes every endpoint for 5xx errors and schema violations from the CLI or pytest, picks the conformance checks and gates CI as the API evolves.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

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 highly actionable, well-structured skill body: every section carries executable commands or config, the workflow is sequenced with failure-reproduction checkpoints, and CI/pytest depth is properly offloaded to a real, clearly signaled reference file. Remaining improvements are marginal — trimming duplicated install/references material and moving some setup deep-dives into the reference file.

DimensionReasoningScore

Conciseness

The body is dense and tool-specific (flags table, checks table, three failure-mode setups) with almost no explanation of concepts Claude already knows. Minor trimmable redundancy remains — the 'Install' section repeats the pip/uvx commands already given in 'How to use' step 2, and the closing 'References' section re-lists the link definitions — so it sits at 'efficient with minor over-explanation' rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is fully executable throughout: concrete `schemathesis run` invocations, a flags table, a worked example, complete TOML dynamic-auth config, a runnable Python auth hook, OpenAPI links YAML, and a pytest snippet. Common cases (CLI smoke run, 5xx-only run, pytest promotion, CI gating) are each covered by copy-paste-ready examples.

5 / 5

Workflow Clarity

The 'How to use' section gives a clear 4-step sequence (confirm schema, install, run against staging, promote to pytest/CI) with a verification checkpoint — reproducing failures via the printed curl command and Hypothesis seed — and the anti-patterns mandate triaging every shrunk failure. It stops short of anchor 5 because there is no explicit validate-before-gate checklist (e.g., confirming a clean baseline run before wiring the CI gate).

4 / 5

Progressive Disclosure

The single bundle file, references/ci-and-pytest-integration.md, exists and is clearly signaled three times with descriptive pointers, one level deep with no nested references. However, the ~315-line body inlines substantial deep-dive material (dynamic-auth TOML, stateful-links YAML, hook code) that could partly be split into references, keeping it at 'most content appropriately placed' rather than a lean overview.

4 / 5

Total

17

/

20

Passed

Description

88%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 covers both what the skill does and when to use it, with concrete capabilities and natural trigger phrases. Its only weaknesses are the slightly over-broad 'any request to generate API tests' trigger and a few missing synonyms for schema-based testing.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'fuzzes every endpoint for 5xx errors and schema violations', 'find inputs that make an API return 500', 'picks the conformance checks and gates CI', 'from the CLI or pytest' — with comprehensive coverage of the tool's capabilities and no vague filler. It matches the anchor for multiple specific concrete actions; score 4 would require noticeable coverage gaps, which are absent.

5 / 5

Completeness

It explicitly answers 'when' with 'Use for any request to generate API tests from an OpenAPI or GraphQL schema, or to find inputs that make an API return 500' and 'what' with 'fuzzes every endpoint for 5xx errors and schema violations from the CLI or pytest... gates CI'. Both are concrete and explicit, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'generate API tests', 'OpenAPI or GraphQL schema', 'API return 500', and 'fuzzes' are present and would be said by users needing this skill. A few common synonyms ('swagger', 'spec', 'property-based testing') are missing, so it falls just short of the comprehensive-synonyms anchor at 5 but is well above 'a few natural terms missing' being numerous (3).

4 / 5

Distinctiveness Conflict Risk

The schema-fuzzing niche (5xx discovery, schema conformance) is clearly distinct from example-based API testing skills, but the opening 'any request to generate API tests' is broad enough to overlap with those sibling skills. Minor overlap risk with closely related skills matches anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page