parallel-task

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

The body is a tight, well-structured orchestration playbook with concrete templates, a clear sequenced workflow, explicit validation checkpoints, and safety boundaries, with no unnecessary concept explanation.

Dimension	Reasoning	Score
Conciseness	Lean imperative process with template code blocks and no concept-explaining fluff; it assumes Claude's competence and every section earns its place, with only minor repetition of summary instructions.	3 / 3
Actionability	Provides concrete, copy-paste-ready task-prompt and run-summary templates plus explicit example usage commands and defined subagent fields, giving executable guidance for orchestration.	3 / 3
Workflow Clarity	Clear 6-step sequence with explicit safety boundaries, a validation checkpoint in Step 6, a repeat loop, and feedback handling for blockers (surface and stop that branch).	3 / 3
Progressive Disclosure	Single-file skill with no bundle files needed; content is well-organized into clearly signaled sections (process, templates, error handling, examples), qualifying for a top score under the simple-skills note.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 identifies a distinct niche and gives an explicit command trigger, but it stops short of comprehensive action coverage and lacks a natural 'Use when...' trigger clause, leaving it solid but not top-tier.

Suggestions

Add a 'Use when...' clause listing natural-language triggers (e.g., 'Use when running a multi-task plan in parallel, or when the user asks to execute a sprint/phase across subagents').

Expand the action list beyond 'coordinate' and 'launch' (e.g., 'parse plan files, track dependencies, validate completed tasks, and report run summaries').

Dimension	Reasoning	Score
Specificity	Names the domain ('plan files') and concrete actions ('Coordinate', 'launching multiple parallel subagents for unblocked tasks'), but lists only two actions rather than a comprehensive set.	2 / 3
Completeness	States what the skill does and gives a trigger, but the trigger is only the literal command rather than a 'Use when...' clause with explicit natural triggers, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Includes the explicit '/parallel-task' command as a trigger that users would type, but lacks natural-language keyword variations beyond the literal command.	2 / 3
Distinctiveness Conflict Risk	The explicit '/parallel-task' command trigger carves out a clear, distinct niche that is unlikely to fire for the wrong skill.	3 / 3
	Total	9 / 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: 292843f

Reviewed: about 18 hours 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.