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.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill playwright-cli92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes a clear 'Use when...' clause with natural trigger terms, and establishes a distinct domain (browser automation) that won't easily conflict with other skills.
| 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, and data extraction') AND when ('Use when the user needs to navigate websites, interact with web pages...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'navigate websites', 'interact with web pages', 'fill forms', 'take screenshots', 'test web applications', 'extract information from web pages'. Good coverage of common user language. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on browser automation and web interaction. The combination of 'browser', 'web pages', 'screenshots', and 'web testing' creates a distinct domain unlikely to conflict with document processing or other skills. | 3 / 3 |
Total | 12 / 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-crafted, highly actionable skill with excellent conciseness. The command reference is comprehensive and immediately usable. The main weakness is the lack of validation/verification steps in workflows - particularly important for browser automation where page state can be unpredictable.
Suggestions
Add validation checkpoints to examples, e.g., 'After clicking submit, run `playwright-cli snapshot` to verify the expected page loaded before proceeding'
Include error recovery guidance, such as what to do when an element ref is stale or a click doesn't produce expected results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what browser automation is or how Playwright works. Every line is a concrete command or example. | 3 / 3 |
Actionability | Fully executable commands throughout. Every example is copy-paste ready with real command syntax. No pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | Core workflow is stated (navigate, interact, re-snapshot) but lacks validation checkpoints. Examples show sequences but don't include error handling or verification steps (e.g., checking if form submission succeeded before proceeding). | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Core, Navigation, Keyboard, etc.) but everything is in one file. For this comprehensive command reference, splitting advanced topics (DevTools, Sessions, Tracing) into separate files would improve navigation. | 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.
- 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.