Summary
The installed-skill check compares only SKILL.md. A stale or missing file under references/ produces no warning when the root skill still matches the bundled copy.
I checked the published @playwright/cli@0.1.19 npm tarball, which includes the skills and reference files. This is a gap in the existing check, not a recurrence of the missing-package-files issue in #276.
Reproduction
- Install matching skills with
playwright-cli install --skills.
- Leave
.claude/skills/playwright-cli/SKILL.md unchanged.
- Change or remove
.claude/skills/playwright-cli/references/video-recording.md.
- Invoke a command that runs
checkInstalledSkills().
Expected: the same refresh guidance used for an outdated root skill, covering the affected reference too.
Actual: no mismatch warning. Changing SKILL.md itself does produce the warning.
I independently exercised the published skillCheck.js in a small filesystem fixture with matching root files and different reference files; the reference-only case emitted nothing, while a root-file change emitted the expected warning. The current implementation at 655530f still resolves and compares only the root SKILL.md.
The path history supports the same scope: #427 introduced the stale-skill warning, #439 added line-ending normalization, and the later Playwright roll did not extend the comparison to references/. The current package contains the files, but the installed-copy check does not cover their content.
This matters for the compatibility policy described in #415: the agent also reads the linked guides, and #322 is an example of command syntax living in those guides. Comparing the installed reference tree against the bundled tree, or using a generated content manifest, would extend the existing advisory check. Line-ending normalization should remain, and locally edited guides can receive a warning rather than a hard failure.
Summary
The installed-skill check compares only
SKILL.md. A stale or missing file underreferences/produces no warning when the root skill still matches the bundled copy.I checked the published
@playwright/cli@0.1.19npm tarball, which includes the skills and reference files. This is a gap in the existing check, not a recurrence of the missing-package-files issue in #276.Reproduction
playwright-cli install --skills..claude/skills/playwright-cli/SKILL.mdunchanged..claude/skills/playwright-cli/references/video-recording.md.checkInstalledSkills().Expected: the same refresh guidance used for an outdated root skill, covering the affected reference too.
Actual: no mismatch warning. Changing
SKILL.mditself does produce the warning.I independently exercised the published
skillCheck.jsin a small filesystem fixture with matching root files and different reference files; the reference-only case emitted nothing, while a root-file change emitted the expected warning. The current implementation at655530fstill resolves and compares only the rootSKILL.md.The path history supports the same scope: #427 introduced the stale-skill warning, #439 added line-ending normalization, and the later Playwright roll did not extend the comparison to
references/. The current package contains the files, but the installed-copy check does not cover their content.This matters for the compatibility policy described in #415: the agent also reads the linked guides, and #322 is an example of command syntax living in those guides. Comparing the installed reference tree against the bundled tree, or using a generated content manifest, would extend the existing advisory check. Line-ending normalization should remain, and locally edited guides can receive a warning rather than a hard failure.