What's going on?
The bundled SKILL.md has an ## Installation section, but it only covers installing the CLI (npm install -g @playwright/cli@latest). It never mentions playwright-cli install --skills[=agents] [--global] — the command that installs the skill itself.
README.md documents it, but the README is read by humans, while SKILL.md is the file that actually enters an agent's context. In #42304 the answer to "how do I update a skill" was: re-run playwright-cli install --skills=... [--global]. That makes it the update procedure too, and it's absent from the one file the agent reads.
Practical consequence: asked to install the skill into a second location, my agent copied the skill directory out of the installed package by hand, because the command wasn't in anything it had in context. install --skills=agents --global would have done it.
Suggestion: two lines in the ## Installation section of SKILL.md, showing --skills=claude|agents and --global.
Version
0.1.18
What's going on?
The bundled
SKILL.mdhas an## Installationsection, but it only covers installing the CLI (npm install -g @playwright/cli@latest). It never mentionsplaywright-cli install --skills[=agents] [--global]— the command that installs the skill itself.README.mddocuments it, but the README is read by humans, whileSKILL.mdis the file that actually enters an agent's context. In #42304 the answer to "how do I update a skill" was: re-runplaywright-cli install --skills=... [--global]. That makes it the update procedure too, and it's absent from the one file the agent reads.Practical consequence: asked to install the skill into a second location, my agent copied the skill directory out of the installed package by hand, because the command wasn't in anything it had in context.
install --skills=agents --globalwould have done it.Suggestion: two lines in the
## Installationsection ofSKILL.md, showing--skills=claude|agentsand--global.Version
0.1.18