trace-and-isolate
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component, function, or line is faulty. Covers binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions across TypeScript, SQL, and bash.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill trace-and-isolate96
Does it follow best practices?
Validation 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 an excellent skill description that hits all the marks. It provides specific concrete techniques, uses natural language triggers that developers would actually say, explicitly states both what it does and when to use it, and carves out a distinct niche around bug localization rather than general debugging. The description is comprehensive without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions'. Also specifies languages covered (TypeScript, SQL, bash). | 3 / 3 |
Completeness | Clearly answers both what ('Applies systematic tracing and isolation techniques...') AND when with explicit 'Use when...' clause listing five specific trigger scenarios (hard to locate bug, code not working, error/crash, regression, narrowing down faulty component). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bug', 'not working as expected', 'error', 'crash', 'regression', 'narrow down', 'faulty'. These are exactly the phrases developers use when seeking debugging help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on bug localization and tracing techniques. The specific mention of 'pinpoint exactly where a bug originates', git bisect, [TRACE] patterns, and isolation techniques distinguishes it from general debugging or code review skills. | 3 / 3 |
Total | 12 / 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 with excellent actionability and workflow clarity. The quick reference table provides efficient navigation, and all techniques include concrete, executable examples. The only weakness is the length—at 200+ lines, some advanced patterns could be moved to separate reference files for better progressive disclosure.
Suggestions
Consider moving 'Common Isolation Patterns' (database, network, time isolation) to a separate PATTERNS.md file and linking from the main skill
The 'Breakpoint Strategies' section could be condensed or moved to an ADVANCED.md file since it's IDE-specific and less universally applicable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, minimal prose, and letting code examples speak for themselves. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable code examples across TypeScript, SQL, and bash. Git bisect commands are copy-paste ready, logging patterns are concrete, and isolation techniques include specific implementation code. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (binary search steps, git bisect workflow). Includes explicit checklists for isolation verification and clear 'when to move on' criteria as validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but it's a fairly long monolithic document. Some sections like 'Common Isolation Patterns' could be split into separate reference files for better navigation. | 2 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.