New: 98,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

Common Tasks

by idavidov13 in 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.

MITAuto-check passedTesting & QA

Install Common Tasks

skills CLI
$ npx skills add idavidov13/agentic-playwright --skill common-tasks -a claude-code

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

GitHub CLI
$ gh skill install idavidov13/agentic-playwright common-tasks --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/idavidov13/agentic-playwright.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/common-tasks .claude/skills/common-tasks && 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
common-tasks
GitHub stars
223
Token cost
~2.5k tokens
SKILL.md length
986 words
Files
9 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Identify the task category and resolve… → Select and customize the matching prompt… → Load the specialized skill for the deep… → …
  • The user asks how do I add a ...
  • SKILL.md covers Critical, Instructions, Prompt Templates and See Also
  • Calls npx and npm

What it does

Common Tasks is an agent skill from 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. Use when the user asks "how do I add a ...", "give me a prompt for ...", "create a new [page object | test | schema | factory | fixture | component]", or when bootstrapping a new scaffold artifact and wanting a standardized starting prompt. This skill is a routing layer; for the deep rules of each task category load the matching skill…

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/examples.md`, `references/templates/api-schemas.md` and `references/templates/components.md`).

It sits in Testing & QA, covering API testing, Prompt engineering and Browser testing. It works with Playwright, Zod and TypeScript. The repository describes itself as: Production-grade Playwright + TypeScript Scaffold for Agentic Testing. Harness for all major AI coding agents baked in. The licence is MIT.

When your agent uses it

  • The user asks how do I add a ...
  • Give me a prompt for ...
  • Create a new [page object | test | schema | factory | fixture | component]
  • Bootstrapping a new scaffold artifact and wanting a standardized starting prompt

Example prompts

  • “how do I add a ...”
  • “give me a prompt for ...”
  • “/common-tasks”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify the task category and resolve paths
  2. Select and customize the matching prompt template
  3. Load the specialized skill for the deep rules
  4. Verify with the checklist, then run the affected tests

What it can do on your machine

Read from SKILL.md and the folder at commit f6cbf35. 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

    Shell commands in SKILL.md call:

    • npx
    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Common Tasks loads about 2.5k tokens when it runs, and up to ~8.2k if it reads all its reference files. Until then it costs about 205 tokens; SKILL.md has 986 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~205
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.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 idavidov13/agentic-playwright at commit f6cbf35, republished under its MIT licence (© idavidov13). 986 words, ~2,526 tokens.

Download SKILL.mdSave it as .claude/skills/common-tasks/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
common-tasks
description
Copy-paste AI prompt templates for common Playwright scaffold development tasks — adding page objects, functional/E2E/API tests, Zod schemas, factories, fixtures, and components. Use when the user asks "how do I add a ...", "give me a prompt for ...", "create a new [page object | test | schema | factory | fixture | component]", or when bootstrapping a new scaffold artifact and wanting a standardized starting prompt. This skill is a routing layer; for the deep rules of each task category load the matching skill directly — page-objects / selectors / playwright-cli for UI locators, api-testing for API tests and schemas, fixtures / helpers for fixtures, data-strategy for factories and static data, test-standards for test structure and tags, type-safety for TypeScript + Zod, enums for endpoint enums.
author
Ivan Davidov

AI Prompt Templates for Agentic Playwright

Codegen sub-router. Owns prompt templates per artifact type and the post-generation verification checklist. Plugs into ai-native-workflow Phase 2 (Route) for codegen intents.

For the 8-phase workflow see ai-native-workflow/SKILL.md. For worked examples and troubleshooting see this skill's references/.

Critical

These rules are unique to template usage. All other rules (selectors, waits, types, Zod strictness, response validation, tags, fixtures, JSDoc, no-XPath, no-hardcoded-strings, etc.) live in the CLAUDE.md Constitution and the leaf skills (api-testing, page-objects, selectors, test-standards, data-strategy, type-safety, fixtures, enums). Re-read the Constitution + the matching leaf skill's Critical block before generating from any template here.

  • Resolve {area} first. Every template contains {area} as a placeholder. Run the matching ls (ls pages/, ls tests/, ls fixtures/api/schemas/, ls test-data/factories/, ls test-data/static/, ls enums/) and substitute the real folder name before filling the template. Do not guess.
  • Templates are starters, not substitutes. Each template is a 10-15 line scaffold. The leaf skill listed for the category owns the deep rules — load it and follow it end-to-end. Never reimplement a leaf skill's rules inline in your prompt.
  • Walk the verification checklist (below) after generating. It is the canonical post-codegen audit; the leaf skills point here for it.

Instructions

Phase 1: Identify the task category and resolve paths

Match the user's request to one row, then run the ls commands the row's templates need.

CategoryTemplate sectionSpecialized skill(s)ls to run before filling
Page object / componentPage Object Taskspage-objects, selectors, playwright-clils pages/
Functional / E2E testTest Taskstest-standards, data-strategyls tests/, ls test-data/factories/
API testTest Tasks → Add API Testapi-testing, test-standardsls tests/, ls fixtures/api/schemas/, ls enums/
Zod response schemaAPI Schema Tasksapi-testing, type-safetyls fixtures/api/schemas/
Data factoryData Factory Tasksdata-strategy, type-safetyls test-data/factories/
Static test dataData Factory Tasks → Static Test Datadata-strategy, api-testingls test-data/static/
Fixture (POM / helper)Fixture Tasksfixtures, helpers(no path placeholder)
UI componentComponent Taskspage-objects, selectors(no path placeholder)
Phase 2: Select and customize the matching prompt template

Open the theme file for your category from the Prompt Templates index below, copy the block, and replace every [PLACEHOLDER] and every {area} with concrete values. Leave no unreplaced placeholders in the final prompt.

Phase 3: Load the specialized skill for the deep rules

The templates intentionally stay shallow. When the task needs more than the template's bullets — full status-code coverage, selector exploration rules, fixture composition patterns — load the specialized skill listed in Phase 1 and follow it end-to-end. Do not reimplement that skill's rules inline. Re-read the CLAUDE.md Constitution + the leaf skill's Critical block before writing code.

Phase 4: Verify with the checklist, then run the affected tests

Walk every box. Then run the affected tests; on red, load debugging.

Verification Checklist

After generating code, confirm each box:

  • Imports are from fixtures/pom/test-options.ts (never @playwright/test in specs)
  • Paths, credentials, and endpoints come from process.env.* and enums/{area}/* — nothing hardcoded
  • Locators use getByRole / getByLabel / getByTestId — no XPath
  • No any types
  • No hard waits (waitForTimeout)
  • No JSDoc on locator getters/methods (JSDoc only on action methods)
  • Tests use test.step with Given/When/Then structure
  • Each test has exactly ONE tag from @smoke, @sanity, @regression, @e2e, @api, @destructive (never @functional, never multiple)
  • Tags live on individual tests, not on test.describe() blocks
  • Tests that mutate shared/global state (locale, permissions, roles, guest access, feature flags, global settings) are tagged only @destructive; tests that create + clean up only their own data keep their importance tag
  • Any state-mutating test (destructive or isolated) has an afterEach/afterAll hook that reverts what it wrote
  • Happy-path test data uses factories; curated invalid values come from test-data/static/util/ or test-data/static/{area}/
  • Zod schemas use z.strictObject() — never z.object()
  • API response validation uses expect(SchemaName.parse(body)).toBeTruthy();
  • API tests with request bodies include empty-body + per-field omission + per-field invalid-type for...of loops (universal arrays imported from test-data/static/util/invalid-values.ts)
  • Coverage audit: Every status code in the OpenAPI spec has a matching test (or test.skip + // FIXME)
  • Path parameter tests: Endpoints with path params have the invalid-format data-driven loop
  • 405 tests: At least one unsupported HTTP method test per endpoint
  • Auth matrix: Endpoints with security have both 401 (no token) and 403 (wrong role) tests
  • Behavior mismatches: Any divergence from spec uses test.skip + // FIXME: <ticket-url>, never silent omission
  • No explore-only or throwaway test files committed
Show full SKILL.md (290 more words)Show less
Run the affected tests (mandatory)
bash
npx playwright test tests/{area}/[type]/[name].spec.ts   # specific file
npx playwright test --grep @smoke                        # by tag
npm test                                                 # all non-destructive

Failure protocol: Read the error → load debugging (failure-mode taxonomy + right Playwright tool per failure: UI Mode, Trace Viewer, Inspector, HTML report) → fix the root cause (no try/catch on expect, no timeout bumps, no silent .skip) → re-run; for flake fixes, 5x consecutively.

Prompt Templates

Split by theme under templates/ so the agent loads only the slice it needs — open the file matching your Phase 1 category, copy the block, and replace every [PLACEHOLDER] and {area} with concrete values.

See Also

  • CLAUDE.md — Constitution (MUST/SHOULD/WON'T tables) is the safety floor for every artifact generated from a template here.
  • ai-native-workflow — owns the 8-phase workflow; Phase 2 routes codegen intents to this skill.
  • api-testing — deep rules for API tests + schemas; load before using Add API Test or Create a New Zod Schema templates.
  • page-objects, selectors, playwright-cli — the UI authoring chain; load before using Page Object Tasks templates.
  • test-standards — spec structure, tagging, web-first assertions, data-driven loops; load before using any Test Tasks template.
  • data-strategy — factory + static-data three-tier rule; load before using Data Factory Tasks.
  • fixtures, helpers — DI patterns and helper-fixture promotion; load before using Fixture Tasks.
  • type-safety — Zod 4 validators + the expect(Schema.parse(body)).toBeTruthy() rule; load before any schema work.
  • debugging — load on Phase 4 verification red.
  • refactor-values — load when a template would change an existing enum value or static-data row.
  • references/examples.md — three end-to-end multi-skill chains using the templates.
  • references/troubleshooting.md — common pitfalls when filling templates and how to fix.

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

Files

SKILL.md and 8 other files (references) in .claude/skills/common-tasks of idavidov13/agentic-playwright.

  • SKILL.md
  • references/examples.md
  • references/templates/api-schemas.md
  • references/templates/components.md
  • references/templates/data.md
  • references/templates/fixtures.md
  • references/templates/page-objects.md
  • references/templates/tests.md
  • references/troubleshooting.md

Open the folder on GitHubat commit f6cbf35

Compare with similar skills

Common Tasks 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.

Common Tasks compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Common Tasks this skillidavidov13/agentic-playwright223—~2.5kAutomated safety check: PassMIT
API Testingfugazi/test-automation-skills-agents247—~1.5kAutomated safety check: PassMIT
API Testingpetrkindlmann/qa-skills165—~2.7kAutomated safety check: PassMIT
Playwright E2E Testingfugazi/test-automation-skills-agents247—~3.2kAutomated safety check: PassMIT
Playwright Automationpetrkindlmann/qa-skills165—~5.5kAutomated safety check: PassMIT
RStudio Selenium to Playwright Migrationrstudio/rstudio5.1k—~3.6kAutomated safety check: PassCustom licence

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

  • API Testing

    petrkindlmann/qa-skills

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

    165 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

  • Playwright Automation

    petrkindlmann/qa-skills

    Write production-grade Playwright tests in TypeScript: Page Object Model, fixtures, auto-waiting, user-facing locators, parallel execution, CI integration, sharding, and 2025-2026 feature awareness.

    165 GitHub stars~5.5k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • RStudio Selenium to Playwright Migration

    rstudio/rstudio

    Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.

    5.1k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Svelte Testing

    spences10/sveltest

    Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

    113 GitHub stars~579 tokensUpdated today
    Testing & QAAuto-check passed

More from idavidov13/agentic-playwright

All 13 skills in this repo

  • AI Native Workflow

    idavidov13/agentic-playwright

    Sole entry-point router for AI-assisted work on this Playwright scaffold — owns the 8-phase main workflow (classify → route → explore → plan+confidence → human gate → apply → verify → report), the…

    223 GitHub stars~3.5k tokensUpdated 6 days ago
    Auto-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
    Auto-check passed

  • Page Objects

    idavidov13/agentic-playwright

    Page Object Model pattern for the Playwright scaffold — class structure, get-accessor locator pattern, action-method conventions, component composition, registration via the page-object fixture, and…

    223 GitHub stars~3.6k tokensUpdated 6 days ago
    Auto-check passed

  • Selectors

    idavidov13/agentic-playwright

    Selector strategy, exploration-first workflow, locator priority order (getByRole then getByLabel then getByPlaceholder then getByText then getByTestId), and feedback/validation-message selector…

    223 GitHub stars~2.7k tokensUpdated 6 days ago
    Auto-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
    Auto-check passed

  • Type Safety

    idavidov13/agentic-playwright

    TypeScript type safety conventions for the Playwright scaffold — the "no any" rule, Zod 4 schema patterns (z.strictObject, top-level validators like z.uuid / z.email / z.url / z.int / z.enum)…

    223 GitHub stars~3.5k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Common Tasks

What does Common Tasks do?

Copy-paste AI prompt templates for common Playwright scaffold development tasks — adding page objects, functional/E2E/API tests, Zod schemas, factories, fixtures, and components. Common Tasks is an agent skill from 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.

When should I use Common Tasks?

Common Tasks fits situations like: the user asks how do I add a ..; give me a prompt for ..; create a new [page object | test | schema | factory | fixture | component]; bootstrapping a new scaffold artifact and wanting a standardized starting prompt.

How do I install Common Tasks in Claude Code?

Run `npx skills add idavidov13/agentic-playwright --skill common-tasks -a claude-code`. Or copy the skill folder (.claude/skills/common-tasks in idavidov13/agentic-playwright) into .claude/skills/common-tasks in your project. Claude Code loads it when a task matches its description.

How do I install Common Tasks in Codex?

Run `npx skills add idavidov13/agentic-playwright --skill common-tasks -a codex`. Or copy the skill folder (.claude/skills/common-tasks in idavidov13/agentic-playwright) into .agents/skills/common-tasks in your project. Codex loads it when a task matches its description.

Can I use Common Tasks 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 idavidov13/agentic-playwright --skill common-tasks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/common-tasks, .gemini/skills/common-tasks, .github/skills/common-tasks and .opencode/skills/common-tasks in your project.

What does Common Tasks need to run?

Going by SKILL.md and its folder, Common Tasks needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.

Does Common Tasks access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Common Tasks 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 Common Tasks use?

Common Tasks 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 Common Tasks use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.7k tokens, read only when the agent opens those files.

What are the alternatives to Common Tasks?

Skills that share tags, products or a category with Common Tasks: API Testing (fugazi/test-automation-skills-agents, 247 stars), API Testing (petrkindlmann/qa-skills, 165 stars), Playwright E2E Testing (fugazi/test-automation-skills-agents, 247 stars) and Playwright Automation (petrkindlmann/qa-skills, 165 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Common Tasks?

idavidov13 (a GitHub user) maintains it in idavidov13/agentic-playwright, which has 223 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 1, 2026.

Source: idavidov13/agentic-playwright on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.