New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

API Playwright Test Developer

by jaktestowac in jaktestowac/awesome-copilot-for-testers

Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows.

MITAuto-check passedTesting & QA

Install API Playwright Test Developer

skills CLI
$ npx skills add jaktestowac/awesome-copilot-for-testers --skill api-playwright-test-developer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jaktestowac/awesome-copilot-for-testers api-playwright-test-developer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/api-playwright-test-developer .claude/skills/api-playwright-test-developer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-playwright-test-developer
GitHub stars
116
Token cost
~2k tokens
SKILL.md length
729 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows.

  • Works in 5 steps: Explicit setup/teardown → Single responsibility per test case → Assertions → …
  • Creating backend API tests
  • SKILL.md covers When to Use, Core Principles, Recommended Folder Layout and Playwright Test Example…, plus 7 more sections
  • Needs API_TOKEN

What it does

API Playwright Test Developer is an agent skill from jaktestowac/awesome-copilot-for-testers. Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows. Use when creating backend API tests, contract checks, data-driven API coverage, API+UI hybrid workflows, or reviewing existing Playwright API suites.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering API testing and Browser testing. It works with Playwright. The repository describes itself as: 👨💻 Instructions, prompts, and chat modes to help You with test automation for GitHub Copilot 🤖. The licence is MIT.

When your agent uses it

  • Creating backend API tests
  • Contract checks
  • Data-driven API coverage
  • API+UI hybrid workflows

Example prompts

  • “Use the api-playwright-test-developer skill to write and reviews API automation tests with Playwright Test, covering setup/teardown, assertions…”
  • “/api-playwright-test-developer”

Requirements

  • A credential in API_TOKEN

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Explicit setup/teardown
  2. Single responsibility per test case
  3. Assertions
  4. Clear data management
  5. Patterns and best practices

What it can do on your machine

Read from SKILL.md and the folder at commit 8910672. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • playwright.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API Playwright Test Developer loads about 2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 729 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jaktestowac/awesome-copilot-for-testers at commit 8910672, republished under its MIT licence (© jaktestowac). 729 words, ~1,996 tokens.

Download SKILL.mdSave it as .claude/skills/api-playwright-test-developer/SKILL.md (or your agent's skills folder).
name
api-playwright-test-developer
description
Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows. Use when creating backend API tests, contract checks, data-driven API coverage, API+UI hybrid workflows, or reviewing existing Playwright API suites.
argument-hint
Endpoint or OpenAPI spec, expected behaviors, auth details, and any existing fixtures or helpers
user-invocable
true

API Playwright Test Developer

This skill defines the standard approach for writing and maintaining Playwright-based API tests. It is optimized for robust, repeatable automated validation of REST/GraphQL services, readable test design, and minimal flakiness.

When to Use

  • API endpoint functional testing (status, schema, body values)
  • Data-driven regression coverage across all environments
  • Contract checks (OpenAPI/JSON Schema) for service evolution
  • End-to-end test flows mixing UI and API interactions (hybrid tests)
  • CI pipeline smoke tests and API health checks

Core Principles

  1. Explicit setup/teardown
    • Use test.beforeEach and test.afterEach for consistent test state management (e.g., create/delete test data).
    • Clean up created test data in test.afterEach by default. Skip cleanup only temporarily when debugging a failure, and never commit that state.
    • Avoid shared mutable state across tests to prevent flakiness.
    • Use unique identifiers in test data to avoid collisions and ensure idempotency.
  2. Single responsibility per test case
    • Each test should target one behavior (e.g., 200 vs 401, field validation, paginated listing).
    • Use descriptive test titles to clarify the intent and expected outcome.
    • For complex scenarios, break down into multiple focused tests rather than one large test with many assertions.
    • When testing e2e flows, consider using test.step to logically group related API calls and assertions within a single test case.
  3. Assertions
    • Avoid brittle tests that rely on dynamic timestamps or ordering unless controlled.
    • Add descriptive messages to assertions for easier debugging.
    • Use soft assertions expect.soft for multiple checks in a single test without stopping at the first failure.
  4. Clear data management
    • Use fixtures/config to store base URL, auth tokens, test payload templates.
    • Use factory functions to generate test data with unique identifiers.
    • Avoid hardcoding environment-specific values in tests; use environment variables or config files.
    • For complex data setup, consider using API calls in beforeEach to create necessary resources instead of relying on static test data.
  5. Patterns and best practices
    • Use request fixture for API calls.
    • Use AAA pattern (Arrange-Act-Assert) for test structure.
    • Use builders or factories for constructing request payloads to improve readability and maintainability.
    • Use Simple Request Object Pattern to encapsulate API interactions and reduce duplication across tests.
    • Use test.describe to group related tests and share setup/teardown logic.
.
├── tests/
│   ├── api/
│   │   ├── users.spec.ts
│   │   ├── auth.spec.ts
│   │   ├── orders.spec.ts
│   │   └── contracts.spec.ts
│   ├── e2e/
│   │   ├── signup-and-purchase.spec.ts
│   │   └── checkout-api-ui.spec.ts
│   └── fixtures/
│       ├── api-fixtures.ts
│       ├── data-fixtures.ts
│       └── auth-fixtures.ts
├── helpers/
│   ├── api-helpers.ts
│   ├── schema-validators.ts
│   └── retry-utils.ts
├── data/
│   └── payloads/
│       ├── create-user.json
│       ├── update-order.json
│       └── login.json
├── docs/
│   └── api-test-guidelines.md
├── .github/
│   └── workflows/
│       └── api-tests.yml
├── playwright.config.ts
└── .env.example
  • tests/api/: dedicated API service tests and contract/spec tests.
  • tests/e2e/: hybrid scenarios that combine UI and API flows.
  • tests/fixtures/: setup data and auth fixtures for Playwright Test.
  • helpers/: reusable request builders, response assertions, schema validators.
  • data/payloads/: canonical test payloads to avoid inline duplication.
  • .env.example: environment abstraction for endpoints and tokens.
  • .github/workflows/api-tests.yml: CI pipeline orchestration with separate API test job.

Playwright Test Example (TypeScript)

ts
import { test, expect } from '@playwright/test';

test.describe('API: /users', () => {
  test('GET /users returns 200 and JSON schema', async ({ request }) => {
    const response = await request.get('/api/users', {
      headers: { Authorization: `Bearer ${process.env.API_TOKEN}` },
    });

    expect(response.status()).toBe(200);
    expect(response.headers()['content-type']).toContain('application/json');

    const body = await response.json();
    expect(Array.isArray(body)).toBeTruthy();
    expect(body.length).toBeGreaterThanOrEqual(0);
  });
});
Show full SKILL.md (344 more words)Show less

Common Patterns

  • request.get, request.post, request.put, request.delete

  • HTTP retries for transient 5xx responses (in test infrastructure, not per-test)

  • Data-driven tests: Playwright Test has no test.each - loop over a test-case array instead, so each case registers as its own test:

    ts
    const cases = [
  { name: 'admin', role: 'admin', expectedStatus: 200 },
  { name: 'guest', role: 'guest', expectedStatus: 403 },
];

for (const data of cases) {
  test(`GET /reports as ${data.name} returns ${data.expectedStatus}`, async ({ request }) => {
    const response = await request.get('/api/reports', {
      headers: { Authorization: `Bearer ${tokenFor(data.role)}` },
    });
    expect(response.status()).toBe(data.expectedStatus);
  });
}

    See the parameterize guide: https://playwright.dev/docs/test-parameterize

  • Auth token refresh helpers and failures when invalid credentials are used

  • Validate headers cache-control, strict-transport-security, etc. for security tests

Hybrid API+UI Scenario

  1. Authenticate with API: POST /auth/login → token
  2. Set browser storage/cookie in Playwright page context
  3. Visit protected UI page to assert data mirrored from API
  4. Modify resource via API, then confirm UI updates (or vice versa)

Troubleshooting Guide

  • 401/403: verify token scope, environment URL, and clock skew
  • 404: confirm route path and version (/v1, /v2), check mock intercepts
  • Timeout: increase timeout in request and page.waitForResponse with precise matcher
  • Flakiness: isolate side effects, use dedicated test data, run service health checks before suite

Best Practices Checklist

  • Leverage shared fixtures for base URL and authentication
  • Keep request payloads small and reproducible
  • Assert exact response fields and types
  • Log request/response on failure with contextual messages
  • Use test.step for complex flows to improve readability
  • Clean up created test data in afterEach
  • Regularly review and refactor tests to remove redundancy and improve clarity
  • designing-test-data - when the test data strategy needs dedicated design
  • verifying-acceptance-criteria - when API behavior must be checked against stated acceptance criteria
  • code-review-advanced - when an existing API suite needs a structured review

Definition of Done

This skill is complete when:

  • each test targets one behavior with a descriptive title
  • setup and teardown are explicit, and created data is cleaned up in afterEach
  • assertions check status, content type, and exact response fields
  • data-driven cases use the loop-over-cases pattern, not a nonexistent test.each
  • environment-specific values come from config or environment variables, not hardcoded literals

References

© jaktestowac, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/api-playwright-test-developer of jaktestowac/awesome-copilot-for-testers.

Open the folder on GitHubat commit 8910672

Compare with similar skills

API Playwright Test Developer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API Playwright Test Developer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API Playwright Test Developer this skilljaktestowac/awesome-copilot-for-testers116—~2kAutomated safety check: PassMIT
API Testingfugazi/test-automation-skills-agents247—~1.5kAutomated safety check: PassMIT
Common Tasksidavidov13/agentic-playwright223—~2.5kAutomated safety check: PassMIT
Data Strategyidavidov13/agentic-playwright223—~3.4kAutomated safety check: PassMIT
API Testingpetrkindlmann/qa-skills163—~2.7kAutomated safety check: PassMIT
Playwright E2E Testingfugazi/test-automation-skills-agents247—~3.2kAutomated safety check: PassMIT

Similar skills

  • API Testing

    fugazi/test-automation-skills-agents

    Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).

    247 GitHub stars~1.5k tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Common Tasks

    idavidov13/agentic-playwright

    Copy-paste AI prompt templates for common Playwright scaffold development tasks — adding page objects, functional/E2E/API tests, Zod schemas, factories, fixtures, and components.

    223 GitHub stars~2.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • Data Strategy

    idavidov13/agentic-playwright

    Test data strategy for the Playwright scaffold — Faker + Zod factories for dynamic happy-path data, static TS files (.ts with as const exports — never .json) for domain-specific curated invalid…

    223 GitHub stars~3.4k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • API Testing

    petrkindlmann/qa-skills

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

    163 GitHub stars~2.7k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • Playwright E2E Testing

    fugazi/test-automation-skills-agents

    Author and maintain versioned Playwright (@playwright/test) TypeScript UI specs for browser user flows.

    247 GitHub stars~3.2k tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Test Standards

    idavidov13/agentic-playwright

    Spec file conventions for the Playwright scaffold — imports from test-options.ts, test file structure (describe / beforeEach / test / test.step), single-tag rule, functional vs E2E vs API vs setup…

    223 GitHub stars~3.9k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

More from jaktestowac/awesome-copilot-for-testers

All 13 skills in this repo

  • Assessing Comprehension Debt

    jaktestowac/awesome-copilot-for-testers

    Measures the risk that code shipped without anyone understanding it: a teach-back attestation on high-risk changes, a risk band from changed-code complexity, diff size and whether a human…

    116 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Creating Orchestration Packs

    jaktestowac/awesome-copilot-for-testers

    Creates agent orchestration packs: cooperating .agent.md files with an orchestrator, subagents, matched handoffs, minimal tool grants, and a shared handoff packet contract.

    116 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Creating Plugins

    jaktestowac/awesome-copilot-for-testers

    Packages repository skills as installable Copilot plugins: marketplace registration, plugin.json manifests, generated skill copies, and the sync check CI enforces.

    116 GitHub stars~3.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Governing Quality Waivers

    jaktestowac/awesome-copilot-for-testers

    Turns "we will skip this check for now" into a dated, attributed, expiring waiver with a stated reason and owner, inventories the silent skips already hiding in a repo - skipped tests, disabled lint…

    116 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

  • Recording Change Intent

    jaktestowac/awesome-copilot-for-testers

    Requires an externalised rationale for high-risk changes - new public exports, new endpoints, auth edits, migrations, removed guards - recorded as an Intent commit trailer, an ADR reference, or a…

    116 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Running Visual Regression Tests

    jaktestowac/awesome-copilot-for-testers

    Sets up and maintains visual regression testing: what to snapshot, baseline strategy, masking dynamic regions, threshold tuning, containerized baselines, and the review-and-update workflow.

    116 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about API Playwright Test Developer

What does API Playwright Test Developer do?

Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows. API Playwright Test Developer is an agent skill from jaktestowac/awesome-copilot-for-testers. Writes and reviews API automation tests with Playwright Test, covering setup/teardown, assertions, data management, and hybrid API+UI flows.

When should I use API Playwright Test Developer?

API Playwright Test Developer fits situations like: creating backend API tests; contract checks; data-driven API coverage; API+UI hybrid workflows.

How do I install API Playwright Test Developer in Claude Code?

Run `npx skills add jaktestowac/awesome-copilot-for-testers --skill api-playwright-test-developer -a claude-code`. Or copy the skill folder (skills/api-playwright-test-developer in jaktestowac/awesome-copilot-for-testers) into .claude/skills/api-playwright-test-developer in your project. Claude Code loads it when a task matches its description.

How do I install API Playwright Test Developer in Codex?

Run `npx skills add jaktestowac/awesome-copilot-for-testers --skill api-playwright-test-developer -a codex`. Or copy the skill folder (skills/api-playwright-test-developer in jaktestowac/awesome-copilot-for-testers) into .agents/skills/api-playwright-test-developer in your project. Codex loads it when a task matches its description.

Can I use API Playwright Test Developer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jaktestowac/awesome-copilot-for-testers --skill api-playwright-test-developer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-playwright-test-developer, .gemini/skills/api-playwright-test-developer, .github/skills/api-playwright-test-developer and .opencode/skills/api-playwright-test-developer in your project.

What does API Playwright Test Developer need to run?

Going by SKILL.md and its folder, API Playwright Test Developer needs credentials named API_TOKEN. Our summary lists: A credential in API_TOKEN.

Does API Playwright Test Developer access the network?

SKILL.md names 1 domain. As links in the text: playwright.dev. This is read from the text; nothing was executed.

Is API Playwright Test Developer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does API Playwright Test Developer use?

API Playwright Test Developer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does API Playwright Test Developer use?

About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to API Playwright Test Developer?

Skills that share tags, products or a category with API Playwright Test Developer: API Testing (fugazi/test-automation-skills-agents, 247 stars), Common Tasks (idavidov13/agentic-playwright, 223 stars), Data Strategy (idavidov13/agentic-playwright, 223 stars) and API Testing (petrkindlmann/qa-skills, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API Playwright Test Developer?

jaktestowac (a GitHub user) maintains it in jaktestowac/awesome-copilot-for-testers, which has 116 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 26, 2026.

Source: jaktestowac/awesome-copilot-for-testers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.