omc-teams

CLI-team runtime for claude, codex, or gemini workers in tmux panes when you need process-based parallel execution

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/omc-teams/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 (orchestrating AI CLI workers in tmux for parallel execution) but lacks concrete action verbs describing what the skill actually does. It would benefit from an explicit 'Use when...' clause and more natural trigger terms users might employ when needing this capability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to run multiple AI agents in parallel, fan out tasks, or orchestrate concurrent CLI workers.'

List specific concrete actions the skill performs, e.g., 'Spawns and manages claude/codex/gemini workers in tmux panes, distributes tasks, collects results, and monitors execution.'

Include additional natural trigger terms like 'parallel tasks', 'multi-agent', 'concurrent', 'fan out', 'distribute work' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (CLI-team runtime, tmux panes, parallel execution) and mentions specific tools (claude, codex, gemini workers), but doesn't list concrete actions like 'spawn workers', 'manage panes', 'collect results', etc.	2 / 3
Completeness	The 'what' is partially addressed (runtime for AI workers in tmux panes) and there's an implicit 'when' ('when you need process-based parallel execution'), but there's no explicit 'Use when...' clause with clear trigger guidance. The 'when you need' phrasing is close but uses second person and is embedded rather than explicit.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'tmux', 'parallel execution', 'claude', 'codex', 'gemini', and 'workers', but misses common user phrasings like 'run tasks in parallel', 'multi-agent', 'concurrent', 'fan out', or 'distribute work'.	2 / 3
Distinctiveness Conflict Risk	The combination of tmux panes, CLI-team runtime, and specific AI worker tools (claude, codex, gemini) creates a very distinct niche that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Implementation

77%

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

This is a well-structured, highly actionable skill with clear multi-phase workflow and good validation checkpoints. Its main weakness is verbosity in certain sections (particularly Phase 0's environment detection and Phase 2.5's multi-repo resolution) that could be tightened or split into reference files. The error reference table and comparison table with /team are valuable additions that aid practical use.

Suggestions

Tighten Phase 2.5 (multi-repo workspace resolution) — the five bullet points are repetitive; consolidate into 2-3 concise rules with one example.

Consider extracting the detailed tmux environment detection logic (Phase 0) and multi-repo resolution (Phase 2.5) into a separate reference file to improve progressive disclosure and reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some sections that could be tightened—Phase 2.5 on multi-repo workspace resolution is quite verbose with repetitive bullet points, and the tmux environment detection logic in Phase 0 is overly detailed for what Claude can infer. The deprecated runtime note and comparison table add useful but slightly bulky context.	2 / 3
Actionability	Provides fully executable CLI commands throughout (omc team, tmux capture-pane, npm install commands), concrete examples with specific syntax patterns, and clear parameter formats. The workflow phases give copy-paste ready commands for each step.	3 / 3
Workflow Clarity	The six-phase workflow is clearly sequenced with explicit validation checkpoints: Phase 0 verifies prerequisites before proceeding, Phase 1 validates input before decomposition, Phase 3 includes post-launch verification of pane output, and Phase 5 recommends non-force shutdown before force. The error reference table provides a feedback loop for common failure modes.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections and tables, but it's a monolithic document with no references to external files for detailed content like the multi-repo workspace resolution logic or the full API reference. Phase 2.5 and the environment detection logic in Phase 0 could be split into separate reference files to keep the main skill leaner.	2 / 3
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 679b418

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.