parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.
Install with Tessl CLI
npx tessl i github:rohitg00/skillkit --skill parallel-investigation90
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 an excellent skill description that clearly articulates a specific coordination methodology for parallel debugging investigations. It provides comprehensive trigger terms covering various incident types, explicitly states when to use it with a 'Use when' clause, and carves out a distinct niche around parallel investigation coordination that differentiates it from general debugging skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'coordinates parallel investigation threads', 'explore multiple hypotheses', 'problem decomposition', 'thread assignment', 'sync points with Continue/Pivot/Converge decisions', and 'final report synthesis'. | 3 / 3 |
Completeness | Clearly answers both what (coordinates parallel investigation threads, provides structured phases for decomposition/assignment/sync/synthesis) AND when (explicit 'Use when' clause covering production incidents, slow APIs, integration failures, complex bugs, serial troubleshooting too slow, multiple investigators). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'debugging production incidents', 'slow API performance', 'multi-system integration failures', 'complex bugs', 'root cause', 'troubleshooting', 'root-cause analysis'. These are terms developers naturally use when facing these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focusing specifically on parallel/multi-threaded investigation coordination with explicit decision framework (Continue/Pivot/Converge). Unlikely to conflict with general debugging or incident response skills due to the parallel coordination focus. | 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 is a well-structured skill with strong actionability and clear workflow phases. The templates and decision frameworks are immediately usable. However, the skill is somewhat verbose for what it teaches—the core parallel investigation concept could be conveyed more concisely, and detailed templates could be moved to reference files.
Suggestions
Consider moving the detailed 'Thread Log Template' and 'Final Report Structure' to a separate TEMPLATES.md file, keeping only brief examples inline
Tighten the 'Core Principle' and 'Investigation Structure' sections by removing explanatory text that restates what the structure already shows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant structure (e.g., the thread log template and final report structure are somewhat verbose). The core concepts are clear but could be tightened—some sections like 'Coordination Patterns' add value while others like the detailed time management breakdown feel padded. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for thread assignment, thread logs, sync point agendas, communication protocols, and final reports. The decision framework table and status message formats are immediately usable without modification. | 3 / 3 |
Workflow Clarity | Clear five-phase sequence with explicit sync points and Continue/Pivot/Converge decision framework. The decision table provides clear guidance on when to take each action, and the time management section gives concrete cadence recommendations for different severity levels. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear headers, but everything is inline in one file. The 'Integration with Other Skills' section references external skills appropriately, but the main content could benefit from splitting detailed templates (thread log, final report) into separate reference files to keep the overview leaner. | 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 |
|---|---|---|
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.