mk:playwright-cli
Session-persistent browser automation via Playwright CLI — form filling, screenshots, data extraction, multi-step flows.
Connecting the steps of a workflow
What it does
> Use playwright-cli when: DOM interaction, navigation, data extraction, or generating reusable .spec.ts E2E test code. > Use `mk:agent-browser` instead when: session persistence (auth flows, MFA, cookie import) is required.
Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract…
You don’t need to name it. Ask for the job in your own words — your AI loads the skill when the request matches.
What it can touch
No script files in its folder
Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).
How we know
Listed the 9 files in the skill’s folder on GitHub; none is a script or program.
Mentions an outside service
The instructions point your AI at these sites or APIs. Anything it sends there leaves your computer.
How we know
Web addresses in the SKILL.md, excluding GitHub and documentation sites: playwright.dev.
Uses terminal commands
It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.
How we know
The SKILL.md contains shell code blocks.
Says which tools it uses
It declares the tools it expects to be allowed: Bash(playwright-cli:*)
How we know
The allowed-tools field in the SKILL.md front matter.
No known risk pattern found
Launch7’s automated check read all 9 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-05, commit 9e5f4e9 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to ngocsangyem/MeowKit: 2026-07-27 (70 days before the scan).
Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from ngocsangyem
All from this publisher →- mk:agent-browser
Browser automation CLI for AI agents using agent-browser.
- mk:angular
Angular v20+ patterns — 10 topics consolidated with progressive disclosure.
- mk:autobuild
mk:autobuild — Autonomous Multi-Hour Build Orchestration
- mk:bootstrap
End-to-end project orchestrator: research → design → plan → scaffold → implement → docs.
- mk:confluence
Routing skill — recommends the correct mk:confluence-* leaf for any Confluence Cloud task.
