Skip to content
Back to skills

Api Session

ASecurity

WAY 2 — API test session. Use when the user says "api it", "test api", "run api tests", "api test" — OpenAPI spec or endpoint list → playwright-bdd API tests → run → file bugs → API session report.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 12, 2026
testingtestingapi

Works with

  • api

Security analysis

A100/100

Scanned October 12, 2026

npx -y skills add GhassenAZZOUZ/claude-qa-agent --skill api-session --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Session?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Api Session
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ghassenazzouz-api-session/badge)](https://www.skillsdirectory.com/skills/ghassenazzouz-api-session)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: api-session
description: WAY 2 — API test session. Use when the user says "api it", "test api", "run api tests", "api test" — OpenAPI spec or endpoint list → playwright-bdd API tests → run → file bugs → API session report.
---

# WAY 2 — API Testing

Run CLAUDE.md **Step 0** first. The API base URL comes from `--env`.

## Step 1: Gather inputs
You need at least one of: an OpenAPI/Swagger spec (file or URL), an API base URL, or a list of endpoints.
If you only have a base URL and no spec, ask: "Do you have an OpenAPI spec URL or file? If not, list the endpoints you want tested."

## Phase 1: Write tests
1. Fetch the spec (WebFetch) or read the file
2. Run `test-writer` (`api` type). It covers every endpoint with the 9 mandatory cases (+3 for POST/PUT), using the shared `steps/api.steps.ts` and the `api` fixture
3. Output: `Test#<nn>` triples under `./qa-artifacts/test-cases/[api-slug]-[YYYY-MM-DD]/`

## Phase 2: Execute
Run `test-execution-agent` with `--project=api`, scoped to that folder. It checks status, schema fields, response time (`API_PERF_THRESHOLD_MS`) and headers. Every request/response pair is saved to `./qa-artifacts/api-responses/` by the `api` fixture.

## Phase 3: Report bugs
For each real failure (skip what `bug-report` says not to file): apply the `bug-report` skill (API context) and file it with labels `bug`, `api`, `sev-<n>`, `p<n>`. The body must include the endpoint and method, the payload sent, expected vs actual (status + body diff), and the response time if over threshold. Redact tokens.

## Phase 4: Summary
Apply the `session-report` skill (WAY 2 template). It saves `./qa-artifacts/sessions/api-<YYYY-MM-DD-HH-MM>.md`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.