console-debugging
Use when debugging JavaScript errors, checking console warnings, analyzing browser logs, finding runtime errors, investigating console output, or troubleshooting browser issues. Provides console message analysis.
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/product-design/skills/console-debugging/SKILL.mdQuality
Discovery
89%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 excels at trigger term coverage and completeness, with a clear 'Use when...' clause and natural keywords users would actually say. The main weakness is the vague capability statement 'Provides console message analysis' which doesn't specify concrete actions the skill can perform. The description structure is inverted (when before what) but still functional.
Suggestions
Expand 'Provides console message analysis' to list specific actions like 'parses stack traces, filters errors by severity, identifies error patterns, suggests fixes for common issues'
Consider restructuring to lead with capabilities: 'Analyzes browser console output to identify errors, parse stack traces, and diagnose runtime issues. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (JavaScript/browser debugging) and mentions 'console message analysis' as an action, but lacks specific concrete actions like 'parse stack traces', 'filter by severity', or 'identify error patterns'. | 2 / 3 |
Completeness | Explicitly answers both what ('Provides console message analysis') and when ('Use when debugging JavaScript errors, checking console warnings...') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'debugging JavaScript errors', 'console warnings', 'browser logs', 'runtime errors', 'console output', 'troubleshooting browser issues' - these are all phrases users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on browser console/JavaScript debugging with distinct triggers like 'console warnings', 'browser logs', 'console output' that wouldn't overlap with general coding or other debugging skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 debugging skill with excellent actionability through concrete tool calls, error reference tables, and a useful report template. However, it's somewhat verbose for what Claude needs, and the workflow lacks explicit validation steps to confirm fixes work. The content organization is good but could benefit from splitting reference tables into separate files.
Suggestions
Add a validation step to the workflow (e.g., 'After applying fix, re-run list_console_messages to verify error is resolved')
Move the detailed error reference tables (TypeError, ReferenceError, etc.) to a separate CONSOLE_ERRORS_REFERENCE.md file and link to it
Trim the 'Console Message Categories' section - Claude knows what JavaScript errors and warnings are; focus on the MCP-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant information. The reference tables are useful but could be more compact, and some sections like 'Console Message Categories' explain concepts Claude likely already knows. | 2 / 3 |
Actionability | Provides concrete MCP tool calls with exact parameters, specific error-to-fix mappings in tables, and a complete debugging report template. The workflow steps are executable and the error reference tables give specific fixes. | 3 / 3 |
Workflow Clarity | The 5-step analysis workflow is clearly sequenced, but lacks explicit validation checkpoints or feedback loops. For debugging workflows, there's no 'verify fix worked' step or error recovery guidance when initial debugging doesn't resolve the issue. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's somewhat monolithic at ~180 lines. The reference to 'network-inspection' skill is good, but detailed reference tables could be split into separate files for better navigation. | 2 / 3 |
Total | 9 / 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.
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.