orchestrator

Turn the current Codex thread into a coordination thread that routes per-branch implementation work to durable reusable child threads without worktrees.

Quality

67%

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 ./.agents/skills/orchestrator/SKILL.md

Quality

Content

77%

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

The skill body is highly actionable with concrete commands, exact tool names, and ready-to-use templates, and its routing workflow is clearly sequenced with explicit checkpoints. It is slightly redundant and monolithic, with some content that could be tightened or split.

Suggestions

Consolidate the repeated "do not create worktrees" rule into one authoritative statement and reference it, removing the three other restatements.

Consider moving the child-prompt template and status-tracking table into a referenced reference file so the SKILL.md overview stays shorter and progressive disclosure is one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — lists, commands, and templates with no padding about concepts Claude already knows — but the "no worktree" rule is restated across Core Contract, Thread Tool Boundary, Safety, and Success Criteria, and could be tightened into a single canonical statement.	2 / 3
Actionability	It gives exact commands ($orchestrator on/off/status), namespaced tool names (codex_app.create_thread, send_message_to_thread, etc.), and copy-paste-ready child-prompt and status-table templates, providing concrete executable guidance rather than vague direction.	3 / 3
Workflow Clarity	Routing Rules is a clearly numbered 9-step sequence with explicit checkpoints (if found / if not found), the Thread Tool Boundary gives a stop-and-report guard when tools are missing, and Success Criteria serves as a checklist; conditionals and error handling are explicit.	3 / 3
Progressive Disclosure	Content is organized into well-labeled sections, but it is a single monolithic file over 50 lines with no external references or bundle files, and parts (child prompt template, status table) are inline rather than split out for staged discovery.	2 / 3
	Total	10 / 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 is specific and distinctive within its niche, but it describes a single routing action and omits an explicit "Use when..." trigger, leaving the "when to use it" half implicit.

Suggestions

Add a "Use when..." clause stating the natural trigger, e.g. "Use when the user wants the current Codex thread to coordinate branch work across child threads."

Broaden trigger coverage with plain-language variations users would actually say, such as "route branch work", "delegate to child threads", or "coordinate PRs".

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete routing action ("routes per-branch implementation work to durable reusable child threads without worktrees"), but it is essentially one routing action with modifiers rather than a list of multiple distinct actions, so it is not comprehensive enough for a 3.	2 / 3
Completeness	The description clearly answers "what" (turn the thread into a coordination/routing thread), but there is no "Use when..." clause or equivalent explicit trigger guidance for when to use it, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Terms like "Codex thread", "child threads", and "worktrees" are ones a user in this domain would say, but the phrasing is jargon-heavy ("per-branch implementation work", "durable reusable child threads") and lacks common plain-language variations.	2 / 3
Distinctiveness Conflict Risk	It carves out a clear niche — Codex thread orchestration routing to durable child threads without worktrees — that is distinct and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: udecode/plate
Path: .agents/skills/orchestrator/SKILL.md
Commit: 45116fd

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