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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%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, lean methodology skill with a clear sequenced workflow, validation checklist, and feedback loop. Its main weakness is progressive disclosure: a valuable reference file exists but is never referenced from the body, hurting navigation.

Suggestions

Add a clearly signaled link to references/hypothesis-testing.md (e.g., a '## Templates & Decision Trees' section: 'See [hypothesis-testing.md](references/hypothesis-testing.md) for task templates, evidence report formats, and the arbitration decision tree') so the bundle reference is discoverable.

Consider moving the six detailed failure-mode bullet lists into the reference file, keeping only the category names and a one-line summary inline in SKILL.md to tighten conciseness.

Add a brief inline example of a completed evidence citation or a short arbitration walkthrough to push actionability from concrete guidance toward fully copy-paste-ready templates.

Dimension	Reasoning	Score
Conciseness	The body is lean — bullet taxonomies, an evidence-type table, and a confidence table with no padding explaining what debugging or ACH is — with only minor sections (the six full failure-mode bullet lists) that could be tightened or delegated to the reference.	4 / 5
Actionability	Provides concrete, specific guidance — evidence-strength ratings, a file:line citation example, numeric confidence thresholds, and an arbitration protocol — but it is process/methodology guidance rather than copy-paste executable code, so it does not reach the fully-executable anchor 5.	4 / 5
Workflow Clarity	Clear sequence from Hypothesis Generation through Evidence Collection to Result Arbitration (4 numbered steps), with an explicit validation checklist ('Validate Fix') and a feedback loop ('If no hypotheses confirmed: generate new hypotheses based on evidence gathered') for error recovery.	5 / 5
Progressive Disclosure	Sections are well-organized and a reference file (references/hypothesis-testing.md) exists with templates and a decision tree, but the body never links to or signals that reference, leaving it orphaned — matching the anchor 3 case of references present but not clearly signaled.	3 / 5
	Total	16 / 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, well-structured description that clearly states both capability and trigger conditions using natural language. Its only weakness is mild breadth in the debugging trigger and process-level rather than fully concrete action phrasing.

Dimension	Reasoning	Score
Specificity	Lists several concrete methodology actions — 'parallel investigation', 'evidence collection', 'root cause arbitration', 'competing hypotheses' — but they are process descriptions rather than a comprehensive list of discrete concrete operations, so it sits below the anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration') and 'when' ('Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases are present ('debugging bugs with multiple potential causes', 'root cause analysis', 'parallel investigation workflows'), giving good coverage, though synonyms like 'troubleshooting' or 'RCA' are missing.	4 / 5
Distinctiveness Conflict Risk	The ACH / parallel-investigation framing carves a distinct niche, but the lead trigger 'debugging bugs' is broad and risks overlap with general debugging skills, keeping it just below the minimal-conflict anchor 5.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 554237f

Reviewed: 31 minutes ago

Table of Contents

Discovery Implementation Validation

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.