bug-localization
Identify the precise location of bugs in source code, modules, and systems. Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis. Analyzes stack traces, error messages, failing tests, and code patterns to pinpoint buggy functions, classes, files, or modules with confidence rankings and supporting evidence.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 an excellent skill description that hits all the key criteria. It provides specific concrete actions, includes a comprehensive 'Use when...' clause with natural trigger terms developers would actually use, and clearly distinguishes itself as a bug localization tool rather than a general coding assistant. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Identify the precise location of bugs', 'Analyzes stack traces, error messages, failing tests, and code patterns', 'pinpoint buggy functions, classes, files, or modules with confidence rankings and supporting evidence'. | 3 / 3 |
Completeness | Clearly answers both what ('Identify the precise location of bugs', 'Analyzes stack traces...to pinpoint buggy functions') AND when ('Use this skill when debugging applications, investigating test failures, analyzing error reports, tracing runtime issues, or performing root cause analysis'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'debugging', 'test failures', 'error reports', 'runtime issues', 'root cause analysis', 'stack traces', 'error messages', 'failing tests'. These are all terms developers naturally use when seeking help with bugs. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on bug localization and root cause analysis. The specific triggers (debugging, test failures, stack traces, error messages) distinguish it from general coding skills or code review 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 skill excels at actionability with concrete code examples, clear bug patterns, and specific localization techniques. The workflow is well-structured with explicit steps and verification checkpoints. However, the document is excessively long and verbose, explaining many concepts Claude already understands, and would benefit from splitting detailed patterns into separate reference files.
Suggestions
Reduce verbosity by removing explanations of basic concepts (what stack traces are, what KeyError means) - Claude already knows these
Split the 5 detailed 'Localization Patterns' into a separate PATTERNS.md file, keeping only brief summaries in the main skill
Move 'Investigation Strategies' and 'Confidence Scoring' sections to separate reference files, linking from the main skill
Condense the reporting template section - one example is sufficient, the template explanation is redundant
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose. Many sections explain concepts Claude already knows (what stack traces are, basic debugging concepts). The 500+ lines could be condensed significantly while preserving actionable content. | 2 / 3 |
Actionability | Provides excellent concrete examples with real code snippets, specific error messages, and executable patterns. The localization patterns show exact code with bug locations marked and fixes provided. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow (Gather Evidence → Analyze Context → Locate Suspects → Rank Suspects → Investigation Plan) with explicit validation checkpoints and verification steps throughout. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one massive document. Complex patterns and investigation strategies could be split into separate reference files with the main skill providing an overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (702 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- ArabelaTso/Skills-4-SE
- Commit
0f00a4f
- 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.