browser-debug
Capture browser console, network, and performance logs for debugging. Auto-loads when debugging browser issues, analyzing errors, or investigating page behavior. Provides systematic log capture workflow using Chrome DevTools MCP.
Install with Tessl CLI
npx tessl i github:jpoutrin/product-forge --skill browser-debug72
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
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (console, network, performance logs), clear trigger conditions (debugging browser issues, analyzing errors), and uses natural developer terminology. The mention of Chrome DevTools MCP adds distinctiveness and technical specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Capture browser console, network, and performance logs' and 'systematic log capture workflow using Chrome DevTools MCP'. Names specific tools and log types. | 3 / 3 |
Completeness | Clearly answers both what ('Capture browser console, network, and performance logs') and when ('Auto-loads when debugging browser issues, analyzing errors, or investigating page behavior'). Explicit trigger guidance is provided. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'browser', 'console', 'network', 'debugging', 'errors', 'page behavior', 'Chrome DevTools'. Good coverage of terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on browser debugging via Chrome DevTools MCP. The combination of 'browser console', 'network logs', 'Chrome DevTools' creates distinct triggers unlikely to conflict with general debugging or other document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable guidance with executable MCP tool calls and CLI commands, but is severely bloated with content that should be in separate files or omitted entirely. It explains concepts Claude knows (what Chromium is, why DevTools Protocol matters) and includes extensive troubleshooting/best practices inline rather than referenced. The workflow is clear but lacks validation checkpoints for error handling.
Suggestions
Move 'Browser Compatibility', 'Best Practices', 'Troubleshooting', and 'Common Debugging Patterns' to separate referenced files (e.g., TROUBLESHOOTING.md, PATTERNS.md)
Remove explanatory content Claude already knows (what Chromium is, why browsers use DevTools Protocol, what PDF-style introductions)
Add explicit validation steps after MCP calls (e.g., 'If list_console_messages returns empty, verify browser connection with...')
Reduce the Quick Reference section to just the most common command, linking to a CLI_REFERENCE.md for full options
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400 lines. Includes unnecessary sections like 'When to Use This Skill' (auto-loading is metadata), 'Browser Compatibility' explanations Claude already knows, extensive 'Best Practices' and 'Troubleshooting' sections that could be separate files, and redundant explanations throughout. | 1 / 3 |
Actionability | Provides fully executable Python code examples for all MCP tool calls with specific parameters. CLI commands are copy-paste ready with clear options. Code examples are complete and specific. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (1-5) with logical sequence, but lacks explicit validation checkpoints. No feedback loops for error recovery - doesn't specify what to do if MCP calls fail or return unexpected results. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with everything inline. Troubleshooting, Best Practices, Configuration details, and Common Debugging Patterns should all be separate files. References to other skills exist but the main content is bloated. | 1 / 3 |
Total | 7 / 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.