browser
Web browser automation with AI-optimized snapshots for claude-flow agents
59
51%
Does it follow best practices?
Impact
57%
2.52xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/browser/SKILL.mdQuality
Discovery
22%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 description is too vague and technical to effectively guide skill selection. It lacks concrete actions, natural trigger terms users would say, and provides no explicit guidance on when to use the skill. The technical jargon ('AI-optimized snapshots', 'claude-flow agents') doesn't help users or Claude understand the practical capabilities.
Suggestions
Add specific concrete actions like 'Navigate websites, click elements, fill forms, extract page content, take screenshots'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks to browse a website, scrape web content, automate web interactions, or fill online forms'
Replace technical jargon with user-friendly terms - instead of 'AI-optimized snapshots', describe what this enables (e.g., 'capture page state for analysis')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('web browser automation') without listing concrete actions. It doesn't specify what operations can be performed (e.g., clicking, form filling, scraping, navigation). | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (browser automation) and completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('web browser', 'automation') but misses common user terms like 'scrape', 'click', 'navigate', 'fill form', 'website', or 'browse'. 'AI-optimized snapshots' and 'claude-flow agents' are technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'claude-flow agents' and 'AI-optimized snapshots' provides some distinctiveness, but 'web browser automation' is generic enough to potentially conflict with other web-related skills. | 2 / 3 |
Total | 6 / 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 strong, actionable skill with excellent conciseness and concrete executable examples. The table-based quick reference is particularly effective. The main weakness is the lack of error handling guidance and validation checkpoints in workflows, which is important for browser automation where elements may not load or pages may behave unexpectedly.
Suggestions
Add error handling guidance: what to do when elements aren't found, timeouts occur, or pages don't load as expected (e.g., 'If wait times out: re-snapshot and verify element exists')
Include a validation step in the core workflow, such as checking snapshot output before interacting or verifying page state after navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable bash commands throughout, with concrete examples for login flows, form submission, and data extraction. Commands are copy-paste ready with realistic values. | 3 / 3 |
Workflow Clarity | The core workflow section shows clear sequencing, but lacks explicit validation/error handling steps. No guidance on what to do if a click fails, element isn't found, or page doesn't load as expected. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but everything is in one file. The MCP tools, memory integration, and hooks sections could be split into separate reference files for better navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- ruvnet/ruvector
- Commit
462536e
- 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.