Source profileQuality 55/100

github/awesome-copilot/skills/playwright-generate-test/SKILL.md

playwright-generate-test

Generate a Playwright test based on a scenario using Playwright MCP

Source repository stars
37,126
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/playwright-generate-test"
    Safe inspection promptEditorial

    Inspect the Agent Skill "playwright-generate-test" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/playwright-generate-test/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Specific Instructions

      You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.

      You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.DO run steps one by one using the tools provided by the Playwright MCP.

    Permission review

    Static risk signals and limitations

    Writes files

    medium · line 11

    The documentation asks the agent to create, modify, or delete local files.

    Save generated test file in the tests directory

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score55/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/playwright-generate-test/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    Test Generation with Playwright MCP

    Your goal is to generate a Playwright test based on the provided scenario after completing all prescribed steps.

    Specific Instructions

    • You are given a scenario, and you need to generate a playwright test for it. If the user does not provide a scenario, you will ask them to provide one.
    • DO NOT generate test code prematurely or based solely on the scenario without completing all prescribed steps.
    • DO run steps one by one using the tools provided by the Playwright MCP.
    • Only after all steps are completed, emit a Playwright TypeScript test that uses @playwright/test based on message history
    • Save generated test file in the tests directory
    • Execute the test file and iterate until the test passes

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    testing-anti-patterns

    Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

    2026-07-280 platforms
    Computed 997

    event4u-app/agent-config

    design-review

    Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

    2026-07-280 platforms
    Computed 987

    event4u-app/agent-config

    pest-testing

    Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.

    2026-07-280 platforms