test-guided-bug-detector
Uses failing test results as signals to guide bug search and narrow down candidate fault locations. Use when one or more tests are failing and the user wants to understand what's broken, when CI reports failures, or when triaging a batch of test failures after a change.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill test-guided-bug-detector93
Quality
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 is a well-crafted description with strong completeness and trigger term coverage. The explicit 'Use when' clause with multiple scenarios provides clear guidance for skill selection. The main weakness is that the capability description could be more specific about the concrete actions performed beyond the general 'guide bug search and narrow down fault locations'.
Suggestions
Add more specific concrete actions like 'analyzes stack traces, identifies regression points, maps failures to recent code changes' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (failing tests, bug search) and describes the general action (guide bug search, narrow down fault locations), but doesn't list multiple concrete specific actions like 'analyze stack traces, identify regression commits, map failures to code changes'. | 2 / 3 |
Completeness | Clearly answers both what (uses failing test results to guide bug search and narrow fault locations) AND when (explicit 'Use when' clause with multiple trigger scenarios: failing tests, CI failures, triaging batch failures). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'failing test', 'tests are failing', 'CI reports failures', 'test failures', 'what's broken', 'triaging'. Good coverage of variations users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test failure analysis and fault localization. Distinct triggers like 'CI reports failures', 'triaging test failures' make it unlikely to conflict with general debugging or testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides expert-level guidance on test failure triage with excellent actionability. The decision table, Ochiai formula, clustering criteria, and worked example are all concrete and immediately usable. The only weakness is that it's somewhat long for a single file and could benefit from clearer cross-references to related skills.
Suggestions
Convert the `→ bug-localization` reference to an explicit markdown link (e.g., `[bug-localization](bug-localization.md)`) for clearer navigation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with actionable tables, formulas, and examples. No explanation of basic concepts Claude already knows; the content is dense with novel, specific guidance. | 3 / 3 |
Actionability | Provides concrete decision tables, a specific formula (Ochiai), clustering criteria in priority order, and a worked example showing exact steps. The output format template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear three-step sequence (triage → localize → cluster) with explicit decision points. The worked example demonstrates the feedback loop of fix-then-rerun, and the clustering approach prevents wasted effort. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a single monolithic file. The reference to `bug-localization` skill suggests external content exists but isn't clearly signaled as a link. For a skill of this length (~100 lines), some content could be split out. | 2 / 3 |
Total | 11 / 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.