parallel-task

Coordinate plan files by launching multiple parallel subagents for unblocked tasks. Triggers on explicit "/parallel-task" commands.

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The content is a well-sequenced, concise, and highly actionable workflow with explicit validation checkpoints and templates. The only weakness is progressive disclosure: everything is inline with no split reference files for the sizable templates.

Suggestions

Move the Task Prompt Template and Run Summary Template into referenced files (e.g. references/task-prompt.md, references/run-summary.md) and link to them from the body to improve progressive disclosure.

Add a short top-of-body overview line summarizing the end-to-end flow before diving into steps, so the structure is navigable at a glance.

Dimension	Reasoning	Score
Conciseness	The body is lean and structured with lists and templates, assumes Claude knows what subagents and plans are, and avoids explaining background concepts; every section earns its place as actionable material.	3 / 3
Actionability	It provides a concrete copy-paste Task Prompt Template, a Run Summary Template, numbered step-by-step instructions, and executable example usage commands, giving specific actionable guidance rather than vague direction.	3 / 3
Workflow Clarity	The process is explicitly sequenced (Steps 1–6) with a repeat loop on newly-unblocked tasks, explicit validation in Step 6 ('validate the plan's success... Perform available tests'), and a safety rule requiring validation before marking tasks complete.	3 / 3
Progressive Disclosure	No references/scripts/assets bundle exists and all content sits inline in a single ~150-line SKILL.md; the large Task Prompt and Run Summary templates are inline blocks that could be split into signaled reference files, so structure is present but not optimally separated.	2 / 3
	Total	11 / 12 Passed

Description

75%

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

The description clearly answers both what the skill does and when it triggers, with a distinctive slash-command trigger and third-person voice. Its main weakness is narrow trigger-term coverage and a limited set of named actions.

Suggestions

Expand the trigger clause to include natural-language variations a user might say, e.g. 'Use when the user asks to run plan tasks in parallel or delegates a plan to multiple agents.'

Name a few more concrete actions (e.g. parse sprints, mark tasks complete, loop on newly-unblocked tasks) to lift specificity.

Dimension	Reasoning	Score
Specificity	The phrase 'Coordinate plan files by launching multiple parallel subagents for unblocked tasks' names the domain (plan files) and a concrete action (launching parallel subagents), but the action set is narrow rather than a list of multiple specific operations.	2 / 3
Completeness	It states both what it does ('Coordinate plan files by launching multiple parallel subagents for unblocked tasks') and when to use it ('Triggers on explicit "/parallel-task" commands'), in third person, satisfying both the what and the when.	3 / 3
Trigger Term Quality	'Triggers on explicit "/parallel-task" commands' provides a real keyword a user would type, but coverage is limited to the single slash command with no common natural-language variations.	2 / 3
Distinctiveness Conflict Risk	The niche is specific (parallel subagent coordination of plan files) with a distinct '/parallel-task' trigger, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: jdrhyne/agent-skills
Commit: a4d31ad

Reviewed: 11 days 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.