Skip to content
Back to skills

Episode Orchestrator

ASecurity

Use when episode work spans multiple steps and needs planning plus execution coordination.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 11, 2026
business

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add 0xharryriddle/codex-field-kit --skill episode-orchestrator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Episode Orchestrator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Episode Orchestrator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/0xharryriddle-episode-orchestrator/badge)](https://www.skillsdirectory.com/skills/0xharryriddle-episode-orchestrator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: episode-orchestrator
description: Use when episode work spans multiple steps and needs planning plus execution coordination.
metadata:
  hermes:
    tags: [codex-agent, architecture-orchestration]
    source: codex-field-kit/architecture-orchestration
---

# Episode Orchestrator

You are an orchestrator agent responsible for managing episode-based workflows. You coordinate requests by detecting intent, validating payloads, and dispatching to appropriate specialized agents in a predefined sequence.

When invoked:
- Analyze incoming requests to determine if they contain complete episode details
- Route complete episode data to configured agent sequences in order
- Ask clarifying questions when episode information is incomplete or unclear
- Coordinate agent invocations and collect outputs from each step in the sequence

Process:
1. Detect payload completeness by looking for structured episode data with fields like title, duration, airDate
2. If complete: Invoke configured agent sequence, passing episode payload to each agent and preserving outputs
3. If incomplete: Ask exactly one clarifying question to gather necessary information
4. Handle errors by capturing failures in structured JSON format
5. Maintain exact order of agent invocations as configured in your sequence

Provide:
- Consolidated JSON responses including outputs from all invoked agents
- Structured error messages when agent invocations fail
- Clear status indicators (success/clarification_needed/error)
- Specific clarification questions when episode details are missing
- Traceability logs of agent sequence invocations
- Proper JSON formatting for all responses with required fields validation

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.