Install the Playwright CLI skill for Codex and other agents, not only Claude Code

Open Beginner friendly
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
playwright, shell
Domain
devtools

Research direction

Start with config.playwright-cli.yaml to see how the post-start hook installs the skill, then read the README and tests/test.bats for the existing setup and assertions. Add support for choosing claude and agents targets through PLAYWRIGHT_CLI_SKILLS, keeping claude as the default and hook failures non-fatal. Done means the README documents both targets and tests cover the configured and default behavior, including the expected skill paths.

Written by the indexing model from the issue text.

Description

enhancement
Is there an existing issue for this?
  • I have searched the existing issues
Is your feature request related to a problem?

Problem

The post-start hook in config.playwright-cli.yaml runs playwright-cli install --skills without a value:

- exec: "which playwright-cli > /dev/null 2>&1 && playwright-cli install --skills || true"

Playwright CLI treats that as claude:

$ playwright-cli install --help
  --skills  install skills, possible values: claude (default), agents.

So the skill only lands in .claude/skills/playwright-cli/. Codex, and other agents that read .agents/skills/, never get it, although the CLI and Chromium are installed and work for them.

Steps to reproduce

  1. ddev add-on get e0ipso/ddev-playwright-cli && ddev restart
  2. ddev exec ls .agents/skills: there's no playwright-cli.
  3. In Codex inside the web container, the skill isn't listed (codex debug prompt-input "hi" doesn't mention it).

Running ddev exec playwright-cli install --skills agents by hand writes .agents/skills/playwright-cli/, and Codex picks it up.

Versions: add-on v1.2.3, @playwright/cli 0.1.24, Codex CLI 0.169.0, DDEV ≥ 1.25.

Current workaround

A project-owned .ddev/config.playwright-cli-codex.yaml:

hooks:
  post-start:
    - exec: "which playwright-cli > /dev/null 2>&1 && playwright-cli install --skills agents || true"

DDEV runs the hooks from every config.*.yaml file, so the add-on's own hook still runs too.

Describe your solution

Let projects choose the targets with an environment variable, keeping today's behavior as the default:

#ddev-generated
hooks:
  post-start:
    # Install the Playwright CLI skill for each target in PLAYWRIGHT_CLI_SKILLS
    # ("claude", "agents"; default "claude"), if the CLI is available.
    - exec: 'which playwright-cli > /dev/null 2>&1 && for target in ${PLAYWRIGHT_CLI_SKILLS:-claude}; do playwright-cli install --skills "$target"; done || true'
web_environment:
  - PLAYWRIGHT_MCP_CONFIG=/var/www/html/.ddev/playwright-cli/cli.config.json

A project opts in with:

ddev dotenv set .ddev/.env.web --playwright-cli-skills="claude agents"
ddev restart

Setting web_environment in a project config.*.yaml file would work too.

  • Default unchanged: existing projects don't suddenly get an .agents/skills/ folder they would need to ignore in Git.
  • Failures stay non-fatal: || true keeps the hook from breaking ddev start, as it does today.
  • README: document the variable and the two targets.
  • Test: extend tests/test.bats. With PLAYWRIGHT_CLI_SKILLS="claude agents", assert that .agents/skills/playwright-cli/SKILL.md exists. With the default, keep the current .claude/skills/playwright-cli assertion and check that .agents/skills/playwright-cli doesn't exist.
Describe alternatives

No response

Additional context
  • Always install both targets: no configuration, but every project gets .agents/skills/playwright-cli/ and has to ignore it in Git.
  • Detect the agents in use from folders such as .codex/ or .agents/: works without configuration, but it's implicit and easy to get wrong.
Dominant language
Shell
Stars
6
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.