CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

parallel-debugging

Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, efficient methodology skill with concrete evidence standards, a sequenced arbitration protocol, and a fix-validation checklist. Its main flaws are the missing mechanics for actually running parallel investigations and an orphaned bundle reference file that the body never points to.

Suggestions

Link references/hypothesis-testing.md from the body (e.g. under Hypothesis Generation and Result Arbitration: 'Task templates, decision trees, and error-type patterns: see [hypothesis-testing.md](references/hypothesis-testing.md)') so the bundle content is discoverable rather than orphaned.

Add a short section on how to actually run the parallel investigation — how to split hypotheses across agents, what prompt/scope each investigator gets, and how to collect their reports — since the description promises parallel agent investigation but the body never operationalizes it.

State the end-to-end workflow as one explicit numbered sequence (generate hypotheses → dispatch investigators → collect reports → arbitrate → validate fix) up front, rather than leaving the overall order implied by section arrangement.

DimensionReasoningScore

Conciseness

The body is composed of tight bullet lists and tables with no concept exposition — the hypothesis taxonomy, evidence-strength table, and confidence criteria are compact prompting material, not padding. It is not a 5 because the six failure-mode bullets enumerate bug classes (e.g. off-by-one errors, type mismatches) that Claude already knows, and a few sections could be trimmed further.

4 / 5

Actionability

Concrete, executable guidance throughout: a concrete evidence citation example with file:line format, quantitative confidence bands ('High (>80%)', 'Medium (50-80%)'), explicit arbitration rules, and a fix-validation checklist. It falls short of a 5 because the parallel mechanics are never specified — the description promises 'parallel agent investigation' but the body gives no instruction for how to dispatch or scope parallel investigators.

4 / 5

Workflow Clarity

The sections form a coherent sequence (generate hypotheses across categories → collect evidence to standards → arbitrate → validate the fix), the arbitration protocol is numbered, and there is an explicit error-recovery loop ('If no hypotheses confirmed: generate new hypotheses based on evidence gathered') plus a validation checklist. It misses a 5 because the end-to-end workflow is implied by section order rather than stated as one explicit ordered process.

4 / 5

Progressive Disclosure

The body itself is well organized into clear sections of appropriate length, but a bundle file — references/hypothesis-testing.md, containing task templates, an arbitration decision tree, and common hypothesis patterns — is never linked or mentioned anywhere in the body. That reference is undiscoverable from the skill and partially duplicates the inline arbitration logic, which is exactly the 'references present but not clearly signaled' profile of a 3 rather than the well-signaled references of a 4.

3 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and explicitly states both what the skill does and when to use it, with natural trigger phrasing and a distinctive methodology-based niche. The only weaknesses are minor: slightly abstract action terms and a few missing synonyms for the trigger conditions.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'competing hypotheses', 'parallel investigation', 'evidence collection', and 'root cause arbitration' — giving a clear picture of what the skill does. It falls short of a 5 because the actions are methodological abstractions with minor gaps in coverage, but it clearly exceeds the 1-2 concrete actions of a 3.

4 / 5

Completeness

It explicitly answers both questions: 'Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration' states what it does, and 'Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows' states when to use it with concrete trigger phrases — a direct match for the 5 anchor.

5 / 5

Trigger Term Quality

Phrases like 'debugging bugs with multiple potential causes', 'performing root cause analysis', and 'organizing parallel investigation workflows' are natural things a user would say. A few common variations (e.g. 'intermittent bug', 'why is this failing', 'RCA') are missing, keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The competing-hypotheses/ACH framing carves out a clear niche distinct from generic debugging or code-review skills. The opening 'Debug complex issues' is broad enough to overlap with general debugging skills, so it does not fully reach the minimal-conflict-risk profile of a 5, but it is well above the broad overlap of a 3.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

wshobson/agents

Path

plugins/agent-teams/skills/parallel-debugging/SKILL.md

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.