Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a pointer/stub that defers all substantive content to CLI-served skills via `agent-browser skills get core`. While this is a clever versioning strategy, it means the SKILL.md itself provides almost no actionable browser automation guidance—Claude must execute commands before it can help the user. The marketing-style 'Why agent-browser' section wastes tokens, and there are no validation steps or error handling for the bootstrap process.
Suggestions
Include at minimum a quick-start workflow example (e.g., navigate to URL, take screenshot, extract text) directly in SKILL.md so Claude can begin helping immediately without first running CLI commands
Remove or drastically shorten the 'Why agent-browser' section—it's marketing copy that doesn't help Claude perform tasks
Add error handling guidance for the bootstrap process (e.g., what to do if `agent-browser install` fails, Chrome isn't found, or `skills get` returns an error)
Consider inlining the core workflow patterns from `skills get core` as a fallback, since the current design means Claude is completely blocked if the CLI isn't installed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The stub is relatively lean, but the 'Why agent-browser' section is unnecessary filler—Claude doesn't need a marketing pitch about Rust performance or compatibility. The 'Observability Dashboard' section adds useful but somewhat tangential info. The core pointer pattern is efficient. | 2 / 3 |
Actionability | The skill provides concrete commands to load the actual skill content (`agent-browser skills get core`), and the install command is copy-paste ready. However, the skill itself contains no executable workflow guidance—it entirely defers to CLI-served content, meaning Claude cannot act on browser automation tasks from this file alone without first running commands. | 2 / 3 |
Workflow Clarity | There is a clear sequence implied: install, then run `skills get core` to load the real workflow. However, there are no validation checkpoints, no error recovery guidance (e.g., what if `agent-browser install` fails or Chrome isn't available), and the actual multi-step browser automation workflow is entirely absent from this file. | 2 / 3 |
Progressive Disclosure | The skill correctly acts as a discovery stub pointing to CLI-served specialized skills (electron, slack, dogfood, etc.), which is a reasonable progressive disclosure pattern. However, since no bundle files are provided and all real content is deferred to runtime CLI commands rather than referenced markdown files, there's no way to verify the referenced content exists or is well-structured. The pattern of requiring CLI execution to access instructions adds friction. | 2 / 3 |
Total | 8 / 12 Passed |