Playwright Pro 2.1.1
v1.0.0Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test mi...
⭐ 0· 56·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Playwright test generation, review, fix, migration, BrowserStack/TestRail integrations) match the included assets: templates, agents (migration-planner, test-architect, test-debugger), hooks to detect/validate Playwright tests, and two MCP integration clients for BrowserStack and TestRail. There are no unrelated binaries or environment requirements declared.
Instruction Scope
SKILL.md and CLAUDE.md limit actions to test generation, review, debugging, migration and optional external integrations. The agents are allowed to read the repo (Read/Grep/Glob/LS) and the test-debugger may run Bash commands (it explicitly runs npx playwright test). Hooks run two shell scripts: detect-playwright.sh (on session start) and validate-test.sh (on PostToolUse Write/Edit). These scripts inspect repository files and test files for anti-patterns — expected for the skill but worth noting because they operate on local files and may run automatically after writes.
Install Mechanism
There is no automated install spec (instruction-only), which minimizes automatic disk writes. However, the skill bundle contains runnable code (TypeScript MCP servers and shell hooks). Running those MCP servers or hooks requires Node/tsx/python3/bash on the host and would be a manual action by the user or the platform's plugin runtime. No remote download URLs or extract steps are present.
Credentials
The manifest declares no required environment variables. The SKILL.md documents optional env vars for TestRail (TESTRAIL_URL/USER/API_KEY) and BrowserStack (BROWSERSTACK_USERNAME/ACCESS_KEY) that are appropriate for those integrations. No unrelated credentials are requested. The MCP server code checks for those env vars and exits if they are absent, which matches the 'optional integration' behavior.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent platform-wide privileges. Hooks are present and configured to run on SessionStart and after write/edit operations (PostToolUse), which is consistent with a developer tooling plugin that validates tests. The skill does not attempt to modify other skills' config or request elevated system-wide settings.
Assessment
This skill appears coherent with its stated purpose. Things to consider before installing or enabling it: 1) Hooks will run shell scripts on session start and after file writes — they inspect your repository and validate test files; review hooks/validate-test.sh and hooks/detect-playwright.sh if you want to confirm exact behavior. 2) The BrowserStack and TestRail integrations are optional but require credentials (env vars) to operate; only provide those credentials if you intend to use those integrations. 3) The package includes TypeScript 'MCP' servers (BrowserStack/TestRail) that will perform network calls when you run them locally — review their code and only run them in trusted environments. 4) The test-debugger agent runs Playwright commands (npx playwright test) during diagnosis; expect it to execute local tests and create traces. If any of that is undesirable, avoid starting the MCP servers or enable only the portions you trust.Like a lobster shell, security has layers — review code before you run it.
latestvk979pgwrq3b39pn94k1fc7yqz984a17w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.