orchestrator

Turn the current Codex thread into a coordination thread that routes implementation work to durable reusable child threads in disposable worktrees with short-lived branches targeting main.

Quality

68%

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 ./templates/plate-playground-template/.agents/skills/orchestrator/SKILL.md

Quality

Content

77%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 a highly actionable, well-sequenced protocol with concrete commands, templates, and validation checkpoints, but it is a long single file with notable cross-section repetition and no progressive disclosure into reference files.

Suggestions

Consolidate the repeated durable-thread-tools / no-hidden-workers / never-force-push rules into one authoritative section and reference it elsewhere to remove redundancy.

Move detailed operational reference material (Slot Conventions, Data And Runtime Policy, the full Child Prompt Shape) into one-level-deep reference files linked from SKILL.md.

Add a short overview/quick-start at the top so the core contract is graspable before the detailed policies.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude already knows, but the same gates (durable-thread-tools requirement, no hidden workers, never force push) are restated across Mode And Claim Discipline, Core Contract, Thread Tool Boundary, and Safety, which could be consolidated.	3 / 5
Actionability	It provides copy-paste-ready concrete guidance: exact tool names (codex_app.list_projects, etc.), branch format (codex/<surface>-<YYYYMMDD-HHMMSS>), a full child-prompt template, a status table, exact git commands, and exact blocker strings.	5 / 5
Workflow Clarity	Routing Rules and Status Check are clearly numbered sequences with explicit validation checkpoints (audit root checkout after first edit, verify git rev-parse --show-toplevel, rerun checks before push) and feedback loops for error recovery (stop and recreate on root leakage, pause on shared-data conflict, report non-trivial integration conflicts).	5 / 5
Progressive Disclosure	Sections are well-organized with clear headings, but at ~325 lines it is a monolithic SKILL.md with no bundle/reference files; operational detail such as Slot Conventions, Data And Runtime Policy, and the full Child Prompt Shape could be split into one-level-deep references for better progressive disclosure.	3 / 5
	Total	16 / 20 Passed

Description

58%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 specific and distinctive about its coordination/routing mechanism, but it is jargon-heavy and omits an explicit 'Use when...' trigger clause, leaving the activation condition only implied.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to orchestrate, delegate, or coordinate implementation work across child threads').

Soften Codex-specific jargon with plain synonyms users actually say ('orchestrate', 'delegate work', 'manage parallel tasks').

Lead with the concrete actions before the mechanism, so the 'what' reads as a list of capabilities rather than one dense clause.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions and objects — 'routes implementation work to durable reusable child threads in disposable worktrees with short-lived branches targeting main' — naming routing, child threads, worktrees, branches, and the main target, with only minor gaps in coverage.	4 / 5
Completeness	It clearly states what the skill does (turn the thread into a coordination/routing thread) but provides no explicit 'Use when...' trigger clause, so the 'when' is only weakly implied, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It contains some relevant terms ('coordination thread', 'routes implementation work', 'child threads', 'worktrees') but leans heavily on Codex-specific jargon and misses natural synonyms a user would say like 'orchestrate', 'delegate', or 'manage multiple tasks'.	3 / 5
Distinctiveness Conflict Risk	It carves out a clear niche (Codex thread orchestration via durable child threads and disposable worktrees) with mostly distinct triggers, carrying only minor overlap risk with general agent-orchestration skills.	4 / 5
	Total	14 / 20 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: templates/plate-playground-template/.agents/skills/orchestrator/SKILL.md
Commit: babb3c2

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.