swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

Quality

61%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/swarm-planner/SKILL.md

Quality

Discovery

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 identifies a clear and distinctive niche—creating dependency-aware plans for parallel multi-agent execution—which minimizes conflict risk. However, it lacks explicit 'Use when...' trigger guidance and could benefit from more concrete action details and natural user-facing keywords to improve discoverability and completeness.

Suggestions

Add an explicit 'Use when...' clause describing trigger scenarios, e.g., 'Use when the user asks to break down a project into parallelizable tasks for multiple agents' or 'Use when planning multi-agent workflows.'

List more specific concrete actions, e.g., 'Analyzes task dependencies, generates a DAG-based execution plan, assigns work units to parallel agents, and identifies critical path tasks.'

Dimension	Reasoning	Score
Specificity	It names the domain (implementation plans, multi-agent execution) and a key action (creates dependency-aware implementation plans), but doesn't list multiple concrete actions or elaborate on what the plans contain or how they work.	2 / 3
Completeness	The 'what' is reasonably clear (creates dependency-aware implementation plans for parallel multi-agent execution), but the 'when' is only implied by '[EXPLICIT INVOCATION ONLY]' rather than providing explicit trigger guidance like 'Use when...' with natural trigger scenarios.	2 / 3
Trigger Term Quality	Includes some relevant terms like 'implementation plans', 'parallel', 'multi-agent', and 'dependency-aware', but these are somewhat technical. Terms like 'task breakdown', 'work plan', 'parallelization', or 'agent coordination' that users might naturally say are missing.	2 / 3
Distinctiveness Conflict Risk	The combination of 'dependency-aware implementation plans' and 'parallel multi-agent execution' is a very specific niche that is unlikely to conflict with other skills. The '[EXPLICIT INVOCATION ONLY]' tag further reduces conflict risk.	3 / 3
	Total	9 / 12 Passed

Implementation

64%

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

This skill provides strong actionable guidance with a concrete dependency format, useful example, and a complete plan template that agents can follow. Its main weaknesses are moderate verbosity with redundant sections (principles echoing process steps, duplicate clarification steps), a numbering error in the workflow, and a monolithic structure that would benefit from extracting the template into a separate file. Overall it's a solid skill that could be tightened for better token efficiency and clearer sequencing.

Suggestions

Fix the duplicate step numbering (two step 4s) and consolidate the redundant clarification steps (1a and 3) into a single, clearly positioned step with conditional triggers.

Extract the Plan Template into a separate referenced file (e.g., PLAN_TEMPLATE.md) to reduce the main skill's token footprint and improve progressive disclosure.

Remove the Core Principles section or merge it into the Process steps, since principles like 'Explore Codebase' and 'Ask Questions' are already covered in the numbered workflow steps.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy—step 3 (stop and request user input) largely repeats step 1a, the core principles section overlaps with the process steps, and the plan template is quite lengthy. Some trimming would improve token efficiency without losing clarity.	2 / 3
Actionability	The skill provides a concrete task dependency format with a clear example, a complete plan template with specific fields (depends_on, validation, status, log), a parallel execution wave table, and a specific subagent review prompt. This is copy-paste ready guidance.	3 / 3
Workflow Clarity	The multi-step process is clearly sequenced (Research → Documentation → Clarify → Plan → Save → Review), and includes a feedback loop via subagent review. However, there are two steps labeled '4' (Create Plan and Save Plan), step 1a's conditional logic is somewhat ambiguous, and there's no explicit validation checkpoint for the plan itself beyond the subagent review—e.g., no checklist to verify all dependencies are satisfied before saving.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections and headers, but the lengthy plan template could be extracted to a separate file. With no bundle files, everything is inline in a single document that runs quite long. The template section alone accounts for a large portion of the content and would benefit from being a referenced file.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: am-will/codex-skills
Commit: d3983b1

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