SKILLEMALL.ai
GitHub ↗ RU Sign in

AB api-testing

Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients. Covers schema validation with Zod 4/AJV, auth flow testing, CRUD lifecycle tests, error and header validation, pagination, and performance assertions. Use when: "API test," "endpoint test," "REST test," "GraphQL test," "schema validation," "Postman replacement." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; browser UI flows — use playwright-automation. Related: contract-testing, test-data-management, ci-cd-integration, playwright-automation.

petrkindlmann/qa-skills Agent Skills author: petrkindlmann MIT 4 files body ≈ 2 515 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients.

As a process B 76/100 · Nearly there — weak spots: inputs and preconditions

IntegrationPlaywrightSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
100/100
safety, quality, tests
Safety 60%
100
Quality 40%
100
Run on models
none yet
Process rating
B
76/100
Nearly there
Inputs and preconditions w 11
0
When it triggers w 12
50
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 55): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 76/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100Steps. 34 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2515 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • low 11 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 586: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 34 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 100.