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.
Install with Tessl CLI
npx tessl i github:code-yeongyu/oh-my-openagent --skill dev-browser100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Quality
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 provides specific capabilities, comprehensive natural trigger phrases users would actually say, explicit 'Use when' guidance, and clear browser-focused terminology that distinguishes it from other skills. The description uses proper third-person voice throughout.
| 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). The 'Trigger phrases include' section provides explicit guidance. | 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 concise, actionable guidance with executable code examples, clear workflow patterns with validation checkpoints, and well-organized progressive disclosure to reference materials. The content respects Claude's intelligence while providing the specific, project-relevant details 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 example clearly shows correct vs incorrect patterns. | 3 / 3 |
Workflow Clarity | The 'Workflow Loop' section explicitly defines a 5-step iterative process with clear validation checkpoints. The 'Choosing Your Approach' section provides clear decision criteria, and setup instructions include explicit wait conditions before proceeding. | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview sections and one-level-deep references to detailed materials (references/installation.md, references/scraping.md). Content is appropriately split between quick-start inline examples and linked detailed guides. | 3 / 3 |
Total | 12 / 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.