CtrlK
BlogDocsLog inGet started
Tessl Logo

control-session-orchestrator

Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can spawn persistent project sessions and those sessions can spawn their own subagents, creating a two-level orchestration hierarchy.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable orchestration methodology with concrete contract schemas, a worker prompt template, and a rigorously gated multi-step workflow. Its only weaknesses are mild verbosity from repeated safety-invariant restatements and a monolithic single-file structure with no external references.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes Claude's competence (no basic-concept padding), but the runtime-vs-prompt rationale paragraph and repeated restatements of invariants like 'never drop silently' across Steps 6, 8, and Safety rules are minor over-explanation that could be tightened.

4 / 5

Actionability

Provides copy-paste-ready artifacts — the full control-result JSON block, the complete control-state manifest schema, and a complete worker prompt template — plus exact status enums and a concrete dispatch protocol, so Claude knows exactly what to emit and do.

5 / 5

Workflow Clarity

A clearly sequenced 9-step workflow (0–8) with explicit validation checkpoints — the result-gate (schema validation, 2-retry cap then escalate), the wave-join/completeness gate requiring terminal rows, and pilot gating for batches — plus validate→fix→retry feedback loops for batch/multi-session operations.

5 / 5

Progressive Disclosure

No bundle files exist, so all content lives in one 422-line SKILL.md; it is well-organized into clearly headed sections with an intra-document anchor link, and the inline schemas are core contracts rather than reference material, though some gate logic and the full manifest schema could optionally be split into reference files.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states what the skill does and gives explicit, natural trigger phrases for when to use it. The only soft spot is minor overlap with built-in workflow orchestration triggers, which the description acknowledges.

DimensionReasoningScore

Specificity

Lists multiple concrete orchestration actions — 'coordinating multi-agent, multi-session project work', 'orchestrate agents', 'create or steer worker sessions', 'fan out audits/research/migrations', 'coordinate parallel implementation streams', 'monitor other project sessions' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both: the 'what' ('Control-plane workflow for coordinating multi-agent, multi-session project work from a single…control session') and the 'when' via a concrete 'Use this skill whenever the user asks to…' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Uses natural user phrasings with synonyms — 'orchestrate agents', 'steer worker sessions', 'fan out audits/research/migrations', 'monitor other project sessions', 'run a workflow-like effort' — the kind of terms a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (session-native two-level orchestration) but 'orchestrate agents' and 'run a workflow-like effort' overlap with Claude Code's built-in Workflow/dynamic-workflow tooling; the description itself flags this overlap ('compare this control-session pattern to Claude Code dynamic workflows'), so it is mostly distinct with minor conflict risk rather than minimal.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pskoett/pskoett-ai-skills
Reviewed

Table of Contents

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.