Install
$ agentstack add skill-jovd83-playwright-skill-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Playwright Coverage Plan Review
Use this skill to turn a proposed plan into an approved plan.
Review Workflow
- Present the plan in a compact, scannable format.
- Highlight any assumptions, exclusions, or high-cost scenarios.
- Ask for additions, removals, or reprioritization only where that decision matters.
- Record the approved scope clearly before downstream work begins.
Output Contract
Summarize the plan with:
Included coverageAssumptionsProposed exclusions or deferred itemsQuestions requiring a decision
When helpful, include an updated approval table:
| Requirement ID | Scenario | Priority | Status | Notes | |---|---|---|---|---|
Use Status values such as proposed, approved, deferred, or removed.
Approval Rules
- If the user already approved the scope in the same thread, do not force a second approval loop.
- If the plan is large, costly, or assumption-heavy, get explicit approval before implementation.
- If feedback changes the plan materially, refresh the presented version before proceeding.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jovd83
- Source: jovd83/playwright-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.