playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
88
86%
Does it follow best practices?
Impact
90%
22.50xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates what the skill does and when to use it. It uses third person voice, lists concrete actions, and includes an explicit 'Use when...' clause with natural trigger terms. The only minor weakness is potential overlap with other skills that handle forms or data extraction outside of a browser context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'browser interactions', 'web testing', 'form filling', 'screenshots', and 'data extraction'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (automates browser interactions for web testing, form filling, screenshots, data extraction) and 'when' (explicit 'Use when...' clause listing six trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'navigate websites', 'interact with web pages', 'fill forms', 'take screenshots', 'test web applications', 'extract information from web pages'. These cover a good range of natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | While browser automation is a fairly distinct niche, terms like 'data extraction' and 'form filling' could overlap with non-browser skills (e.g., PDF form filling, API-based scraping). It could benefit from mentioning the specific tool (e.g., Playwright, Puppeteer) to further distinguish it. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable command reference for playwright-cli browser automation. Its greatest strengths are conciseness and actionability—every command is concrete and copy-paste ready. The main weaknesses are the lack of validation/error-recovery steps in workflows and the opportunity to better leverage progressive disclosure by moving the full command reference to a separate file.
Suggestions
Add validation checkpoints to the core workflow and examples, e.g., 'After clicking submit, run `playwright-cli snapshot` to verify the expected page loaded; if not, check `playwright-cli console` for errors.'
Move the full command reference to a separate COMMANDS.md or REFERENCE.md file, keeping only the quick start, core workflow, and one or two examples in SKILL.md with links to the detailed reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It's essentially a command reference with examples—no unnecessary explanations of what a browser is, what Playwright does, or how web automation works. Every line serves a purpose. | 3 / 3 |
Actionability | All commands are concrete, copy-paste ready bash commands. The examples show complete workflows with specific commands and element references (e.g., e1, e3). No pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | The core workflow section provides a basic 3-step sequence, and examples show multi-step processes. However, there are no validation checkpoints or error recovery steps—e.g., what to do if a snapshot shows unexpected state, or if a click doesn't navigate as expected. For browser automation involving form submissions and multi-step interactions, feedback loops would be valuable. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and logical grouping of commands (Core, Navigation, Keyboard, Mouse, etc.). However, the extensive command reference could be split into a separate REFERENCE.md, keeping SKILL.md as a concise overview with the quick start and core workflow, pointing to detailed references. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.