dmux-workflows

Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/dmux-workflows/SKILL.md

Quality

Content

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

The body is actionable and reasonably concise with concrete commands and complete JSON schemas, but as a batch/parallel orchestration skill it lacks an explicit post-merge validation feedback loop, and all detail is inlined rather than progressively disclosed into bundle files.

Suggestions

Add an explicit integration/validation step after merging parallel panes (e.g. run the test suite, resolve conflicts, re-run failing checks) to form a validate -> fix -> retry feedback loop and raise workflow_clarity.

Split the detailed ECC plan.json schema and the five workflow patterns into one-level-deep reference files under references/ with clearly signaled links from SKILL.md to improve progressive_disclosure.

Convert illustrative pane-prompt comments in Quick Start into runnable dmux invocations or move them to a copy-paste-ready script to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with patterns, commands, tables, and troubleshooting, with only minor restatements (e.g. 'dmux is a tmux-based orchestration tool' and 'Each pane is a full agent session') that could be trimmed.	4 / 5
Actionability	Provides executable commands (`dmux`, `git worktree add -b ...`, `node scripts/orchestrate-worktrees.js plan.json --execute`, `tmux capture-pane -pt ...`) and a complete, copy-paste-ready plan.json schema; some workflow-pattern blocks use illustrative placeholder prompts in comments rather than runnable commands.	4 / 5
Workflow Clarity	A rough create-panes -> run -> merge sequence exists with one light checkpoint ('Review pane output before merging to avoid conflicts'), but for a batch/parallel skill touching files there is no explicit validate -> fix -> retry feedback loop or integration-test step after merging, so validation is present but thin.	3 / 5
Progressive Disclosure	The 185-line body is well-sectioned but entirely inlined into a single file with no bundle references (references/scripts/assets absent); detailed content like the full ECC plan.json schema and five workflow patterns could reasonably live in one-level-deep reference files.	3 / 5
	Total	14 / 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.

The description clearly states both the capability and explicit activation triggers in third person, with a distinctive named tool. Minor specificity on abstract coordination verbs keeps it just below a perfect specificity score.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Multi-agent orchestration', 'parallel agent workflows', 'running multiple agent sessions in parallel', 'coordinating multi-agent development workflows'), though 'coordination' stays somewhat abstract rather than enumerating concrete operations.	4 / 5
Completeness	Explicitly answers both what ('Multi-agent orchestration using dmux') and when ('Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows') with concrete trigger conditions.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('running multiple agent sessions in parallel', 'coordinating multi-agent development workflows') plus the tool name and harness list; a few common synonyms like 'spawn agents' or 'parallelize' are missing.	4 / 5
Distinctiveness Conflict Risk	The named dmux tool and tmux-pane niche make it mostly distinct, though 'multi-agent orchestration' broadly could overlap with built-in Task/workflow tooling.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 3 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/dmux-workflows/SKILL.md
Commit: e04ea0b

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