browser-testing

Drive real browsers via Chrome DevTools MCP: navigate pages, capture snapshots, run responsive checks, and collect console/perf traces. Use when the user mentions: 'validate UI change in Chrome', 'capture a screenshot', 'run responsive checks', or 'collect console logs'. Trigger terms: browser testing, DevTools, console logs, screenshot, responsive testing

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 a strong skill description that covers all key dimensions well. It lists concrete actions, provides explicit 'Use when' guidance with natural trigger terms, and occupies a clear niche around Chrome DevTools-based browser testing. The description is concise yet comprehensive, making it easy for Claude to select appropriately from a large skill set.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: navigate pages, capture snapshots, run responsive checks, collect console/perf traces. Also specifies the mechanism (Chrome DevTools MCP).	3 / 3
Completeness	Clearly answers both 'what' (drive browsers via Chrome DevTools MCP with specific actions) and 'when' (explicit 'Use when...' clause with trigger phrases and a separate trigger terms list).	3 / 3
Trigger Term Quality	Includes a rich set of natural trigger terms users would actually say: 'validate UI change in Chrome', 'capture a screenshot', 'run responsive checks', 'collect console logs', 'browser testing', 'DevTools', 'responsive testing'. Good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to Chrome DevTools MCP-based browser interaction, which is a distinct niche. The combination of DevTools, browser testing, and screenshot/console log triggers makes it unlikely to conflict with generic testing or document skills.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with concrete MCP tool call examples and a well-structured testing workflow including validation checkpoints and error recovery loops. Its main weakness is that the tools reference section is somewhat lengthy inline content that could benefit from being split into a separate file, and a few explanatory comments could be trimmed for better token efficiency.

Suggestions

Consider moving the Chrome MCP Tools Reference section to a separate file (e.g., TOOLS_REFERENCE.md) and linking to it, keeping SKILL.md focused on the workflow.

Remove explanatory comments that Claude can infer, such as '// DOM snapshot, lighter than screenshot' and 'most layout bugs surface at smaller viewports'.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of code examples, but some sections include unnecessary commentary (e.g., 'most layout bugs surface at smaller viewports') and the responsive section could be tighter. The tool reference section is well-structured but slightly verbose with comments that Claude could infer.	2 / 3
Actionability	Provides fully concrete, copy-paste-ready MCP tool calls with specific function signatures and parameters. Every section includes executable JavaScript examples with real tool names and argument structures.	3 / 3
Workflow Clarity	Clear numbered workflow with explicit validation checkpoints: wait_for timeouts trigger server verification, console error checks feed back to fix-rebuild-reload cycles, and the regression re-test workflow has an explicit 'do NOT stop' loop until all tests pass. Error recovery paths are well-defined.	3 / 3
Progressive Disclosure	References project-specific config via testing-config.md which is good, but no bundle files are provided to verify that reference. The tools reference section is fairly long and could be split into a separate reference file, keeping SKILL.md as a leaner overview with workflow focus.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: monkilabs/opencastle
Commit: 7a69a05

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.