dispatch

Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it", "run the batches".

Quality

90%

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

81%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 dense, highly actionable orchestration skill with explicit sequencing, validation checkpoints, and well-signaled references to real bundle files. Its main weakness is conciseness — several core rules and skip conditions are repeated across sections and could be consolidated.

Suggestions

Consolidate the "review agents ≥ batches + 1" rule and the D7 skip conditions into a single authoritative location (e.g. Iron Rules) and reference it elsewhere instead of restating the full conditions each time.

Consider moving the detailed "marginal vs. not-marginal" signals table in Step 5 into a reference file, keeping only the decision rule inline.

Tighten the repeated failure-recovery pointers (DOCTRINE rule 14) into one stated policy near Step 2b rather than re-citing the path at each sub-step.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and domain-specific (no padding about concepts Claude already knows), but several rules are restated across sections — "review agents ≥ batches + 1" appears in the agent map, Iron Rules, Overview, and Output, and the D7 skip conditions are explained in Step 3, Instructions, and Output — so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready commands (`python3 $PLUGIN_ROOT/scripts/resolve-mode.py ...`, `bash $PLUGIN_ROOT/scripts/queue-commit.sh ...`, `gh pr create`, `git push -u origin <branch>`) plus concrete verdict types and exact file paths covering the common cases.	5 / 5
Workflow Clarity	Steps 0–5 are clearly sequenced with sub-phases, explicit validation checkpoints (gates, NEEDS_FIX retry with max-3 limits, SECURITY_VIOLATION halt), and feedback loops (validate → fix → re-run) for the batch/destructive operations the rubric flags as needing validation.	5 / 5
Progressive Disclosure	Good section structure with one-level-deep references to real bundle files (worker-prompt.md, reviewer-prompt.md, review-levels.md, quality-gates.md, git-workflow.md, examples.md, DOCTRINE.md — all verified present) and worked transcripts moved out to keep the body lean; minor gaps remain in that several long tables and the D7/marginal-signal detail are inlined and could be split.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is concise, third-person, and cleanly answers both what the skill does and when to use it, with concrete trigger phrases and a distinct niche. It is a strong, well-scoped description with no over-claims or padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Fans out parallel workers under per-batch Reviewers", "runs a final integration review", "commits per sub-task", "no auto-deploy" — giving comprehensive coverage of the skill's behavior.	5 / 5
Completeness	Explicitly answers what (fan-out, final integration review, per-sub-task commits, endpoint with no auto-deploy) and when ("Use when a task file exists in .hyperflow/tasks/ and workers need dispatching") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes both the slash-command form and natural phrases a user would say ("run the plan", "execute the task", "build it", "run the batches"), plus the triggering condition, covering synonyms comprehensively.	5 / 5
Distinctiveness Conflict Risk	The trigger is narrowly scoped to an existing `.hyperflow/tasks/` task file requiring worker dispatch, a clear niche with minimal overlap against generic skills.	5 / 5
	Total	20 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 19 suspicious	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/skills/dispatch/SKILL.md
Commit: 88dcf65

Reviewed: 3 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.