dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
Overall
score
99%
Does it follow best practices?
Validation 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 an excellent skill description that hits all the marks. It uses third person voice, provides specific concrete actions, includes comprehensive natural trigger phrases users would actually say, and clearly distinguishes itself as a browser automation skill with explicit 'Use when' guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'navigate websites, fill forms, take screenshots, extract web data, test web apps, automate browser workflows' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Browser automation with persistent page state' plus specific actions) and when (explicit 'Use when...' clause with detailed trigger phrases and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would actually say: 'go to [url]', 'click on', 'fill out the form', 'take a screenshot', 'scrape', 'automate', 'test the website', 'log into'. These match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on browser automation with distinct triggers like 'go to [url]', 'click on', 'scrape', 'log into'. The 'persistent page state' qualifier and browser-specific terminology make it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices across all dimensions. It provides concrete, executable examples while maintaining brevity, includes clear workflow patterns with validation checkpoints, and appropriately delegates detailed scraping guidance to a reference file. The content respects Claude's intelligence while providing the specific, project-relevant information needed for browser automation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Playwright and TypeScript. No unnecessary explanations of basic concepts; every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples throughout, including complete heredoc scripts, API usage patterns, and copy-paste ready snippets. The TypeScript vs browser context warning includes concrete correct/incorrect examples. | 3 / 3 |
Workflow Clarity | Clear workflow loop pattern (write → run → evaluate → decide → repeat) with explicit validation steps. Setup instructions include waiting for ready messages before proceeding. Error recovery section provides debugging workflow. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections. Appropriately references external file (references/scraping.md) for advanced scraping guide. Content is organized for quick scanning with headers, code blocks, and bullet points. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.