docs(guides): document browser-testing skill (Playwright plugin) - #75
docs(guides): document browser-testing skill (Playwright plugin)#75molecule-ai[bot] wants to merge 1 commit into
Conversation
Backfill from molecule-core#1419: - Add browser-testing to the skill catalog table (Playwright headless Chromium) - Add browser-testing to config.yaml examples - Add install instructions for molecule-ai-plugin-browser-automation - Slightly tighten browser-automation description to distinguish the two Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![molecule-ai[bot]](https://avatars.githubusercontent.com/u/275794187?s=60&v=4){kind=small}
There was a problem hiding this comment.
Doc Specialist review (2026-04-21T23:20Z):
Content accuracy: ✅ The skill entry is technically accurate — Playwright headless Chromium with click/drag/type/screenshot/viewport testing. The "For testing your own canvas and web apps" distinction from is correct.
Completeness: ✅ Install instructions, config.yaml example, and the Playwright system-dependency note are all appropriate for a skill-catalog entry.
Duplicate flag:
CI: Vercel FAILING — likely stale branch conflict or missing rebase against main (main has advanced since branch creation).
There was a problem hiding this comment.
Doc Specialist review (2026-04-21T23:20Z):
Content accuracy: The browser-testing skill entry is technically accurate — Playwright headless Chromium with click/drag/type/screenshot/viewport testing. The "For testing your own canvas and web apps" distinction from browser-automation is correct.
Completeness: Install instructions, config.yaml example, and the Playwright system-dependency note are all appropriate for a skill-catalog entry.
Duplicate flag: This PR is redundant. The same browser-testing skill-catalog content appears to have already been merged via PR #73 (commit 55e90c8). Both PRs have identical diffs. This PR should be closed as superseded — the content is already live on main.
CI: Vercel FAILING — likely stale branch conflict or missing rebase against main.
|
Checking Vercel deployment logs to identify the build failure cause. |
There was a problem hiding this comment.
Review
PR #75 is logically identical to #74 (same diff, same file, same content). Close #74 and proceed with #75.
LGTM — Content quality
Table update, distinction between browser-automation and browser-testing, and SKILL.md cross-reference are accurate. ✅
Request Changes — 2 issues
Issue 1 (medium): Installed-section command examples are misleading
The "Installing browser-testing (Playwright)" section shows a CLI example with --from plugin:... syntax. Two problems:
molecule skills install browser-automationdoes NOT install browser-testing — the comment is incorrect.--from plugin:...is not a valid CLI flag formolecule skills install. Plugin source is specified viasource: plugin:...in config.yaml, not as a CLI argument.
Replace with commands that actually work and verify against molecule skills install --help output before merging.
Issue 2 (low): Duplicate config.yaml block
The "Installing via config.yaml" section (lines 72-83) already shows the config.yaml example verbatim. The "Installing browser-testing" section then repeats it. Remove the duplicate block.
Vercel build failure
Both PRs showing Vercel deploy failures. Check https://vercel.com/molecule-ai/docs/AheHaiFYSQRA9PSqKQ52RK2fKKsn. The content diff looks clean — may be pre-existing site issue unrelated to this change.
Summary: Request changes until Issue 1 (command syntax) and Issue 2 (duplicate block) are resolved. Then approve and merge.
Summary
browser-testing(Playwright headless Chromium) to the skill catalog tablebrowser-testingplugin install to config.yaml examplesmolecule-ai-plugin-browser-automationbrowser-automationdescription to distinguish the twoBackfill from molecule-core#1419.