Feature Request

Context

We are building the Aspire CLI (aspire agent init / aspire init) which, with the user's permission, installs Playwright as part of the initialization workflow. As part of this process we want to ensure the Playwright skill file is dropped in the directory that is becoming the emerging standard for agent skill/tool discovery.

Aspire is already doing this for its own skill file — placing it in .agents/skills/ — and we'd like Playwright to follow the same convention so that agent tooling beyond Claude (which uses .claude/skills/) can also discover and use the Playwright skill.

Proposal

When playwright-cli install --skills (or playwright install --skills) is run, in addition to copying the skill files to .claude/skills/playwright-cli/, also copy them to .agents/skills/playwright-cli/ with the same directory structure (SKILL.md + references/).

The existing .claude/skills/ output should be preserved to avoid breaking current usage.

Expected behavior

$ playwright-cli install --skills
✅ Workspace initialized at `/path/to/project`.
✅ Skills installed to `.claude/skills/playwright-cli`.
✅ Skills installed to `.agents/skills/playwright-cli`.

Both directories would contain the same content:

.claude/skills/playwright-cli/
  SKILL.md
  references/
    ...

.agents/skills/playwright-cli/
  SKILL.md
  references/
    ...

Motivation

The .agents directory is emerging as a standard location for agent-related configuration and skills across multiple tools and platforms. By also writing to .agents/skills/, Playwright would be forward-compatible with tooling that adopts this convention, while maintaining backward compatibility with the existing .claude/skills/ location.

We are happy to contribute the implementation for this change.