orchestrator

Diagnose vague marketing requests and route users to sequenced execution skills.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/rbrown101010/skillings --skill orchestrator-rbrown101010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/rbrown101010/skillings/tree/main/orchestrator
Command: npx skills add https://github.com/rbrown101010/skillings --skill orchestrator-rbrown101010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Orchestrator provides the strategic layer for marketing workflows by diagnosing vague requests and routing users to the appropriate Skill Units in the correct sequence. It reduces guesswork, clarifies next steps, and ensures dependencies are respected so teams can move from intent to action without getting overwhelmed.

Core Features & Use Cases

  • Qualifying questions to determine user goals and current assets.
  • Dependency-aware routing that outputs a coherent skill sequence with clear handoffs.
  • State tracking and structured context for downstream skills to execute efficiently.

Use cases include: when a user doesn't know where to start, has a vague marketing request, or needs a multi-step workflow to achieve a cohesive marketing system.

Quick Start

Start by asking the user about their goal, what assets exist (brand voice, positioning, content), and timeline. Based on responses, propose the initial skill to run and outline the next steps. Pass only essential context to the next skill to keep outputs focused and actionable.

Frequently Asked Questions about orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sequence marketing tasks when I have a vague request and don't know where to start?

Sequencing marketing tasks from a vague request requires diagnosing your goals and assets first. The Orchestrator asks qualifying questions about your brand voice and timeline, then routes you to the appropriate execution skills in the correct dependency-aware order.

What is dependency-aware routing for multi-step marketing workflows?

Dependency-aware routing for marketing workflows validates prerequisites before advancing to the next step. It outputs a coherent skill sequence with clear handoffs, compressing context between skills so downstream execution stays focused and actionable.

Can I use this skill for multi-step marketing workflows with complex dependencies?

Yes, you can use this skill for multi-step marketing workflows with dependencies. It applies state tracking and structured context to coordinate downstream skills, ensuring prerequisites are met before the workflow advances to subsequent phases.

How do I compress context between marketing skills to keep outputs focused?

To compress context between marketing skills, pass only essential information to the next execution phase. The Orchestrator enforces context compression during handoffs, preventing downstream skills from getting overwhelmed by irrelevant data.

When should I use a marketing task orchestrator instead of individual skills?

You should use a marketing task orchestrator when you are unsure where to start, have vague marketing requests, or need a multi-step workflow. It provides the strategic layer that reduces guesswork and clarifies next steps without manually managing skill dependencies.

What limitations are there when routing vague marketing requests through an orchestrator?

A limitation of routing through an orchestrator is that it depends on the quality of your initial answers to qualifying questions. If goals, existing assets, and timelines are unclear, the proposed skill sequence and dependency-aware routing may lack precision.