chrome
Comprehensive Chrome DevTools development system with native Chrome capabilities for debugging, E2E testing, performance analysis, and browser automation
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill chrome38
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a high-level overview of Chrome DevTools MCP capabilities but lacks the concrete, executable guidance needed to be actionable. It lists tool names and fictional CLI commands without showing actual usage patterns, and complex operations like E2E testing and performance analysis have no workflow definitions or validation steps.
Suggestions
Replace the fictional '/chrome' CLI syntax with actual MCP tool call examples showing real parameters and expected outputs
Add concrete workflow sequences for key operations like E2E testing (e.g., 1. navigate_page -> 2. take_snapshot -> 3. fill -> 4. click -> 5. verify with screenshot)
Include at least one complete, executable example for debugging a page issue using the listed MCP tools in sequence
Add validation checkpoints for performance tracing workflows (start trace -> perform actions -> stop trace -> verify trace data exists)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary padding like the 'Context' section listing status checks without explaining their purpose, and feature descriptions that could be more compact. | 2 / 3 |
Actionability | Despite listing many MCP tool names and CLI-style commands, there are no executable code examples, no concrete usage demonstrations, and the '/chrome' command syntax appears to be fictional rather than actual tool invocations. | 1 / 3 |
Workflow Clarity | No multi-step workflows are defined despite mentioning complex operations like E2E testing and performance tracing. There are no validation checkpoints, no error handling guidance, and no sequenced processes for any of the listed capabilities. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with headers, but everything is in one file with no references to detailed documentation. The structure is reasonable but could benefit from separating detailed guides for testing, debugging, and performance analysis. | 2 / 3 |
Total | 6 / 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.