orchestrator

Route marketing requests to recommended skill sequences via decision-tree routing.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/hoodfav5/hoodfav --skill orchestrator-hoodfav5
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/hoodfav5/hoodfav/tree/main/Vibe-Skills-Claude-Code-v-2/orchestrator
Command: npx skills add https://github.com/hoodfav5/hoodfav --skill orchestrator-hoodfav5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Orchestrator provides a guided decision layer that routes marketing requests to the appropriate skills, reducing confusion and delivering a coherent plan.

Core Features & Use Cases

  • Qualifying questions to diagnose needs
  • Decision-tree routing to recommended skill sequences
  • Pre-built workflows and handoff protocol to maintain context across steps
  • State tracking to surface gaps and next actions

Quick Start

Answer the qualifying questions to determine the goal, then run the first recommended skill.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I route a vague marketing request to the right workflow?▼

To route a vague marketing request, the Orchestrator applies a guided decision tree with qualifying questions to diagnose needs and direct users to the appropriate skill sequence. It ensures context-sensitive data passing to maintain focused outputs across multi-step workflows.

What is the best way to manage multi-step marketing automation when unsure where to start?▼

The best way to manage multi-step marketing automation is using a guided decision layer that tracks state and surface gaps. It provides a handoff protocol to maintain context across steps, ensuring you start with the correct recommended skill sequence.

Does this marketing workflow orchestrator work without external dependencies?▼

Yes, this marketing workflow orchestrator works without external dependencies. It uses an internal decision tree and state tracking to route requests and manage context passing, requiring no additional components to deliver a coherent plan.

When do I need a decision tree for marketing task routing?▼

You need a decision tree for marketing task routing when handling vague requests or complex, multi-step workflows. It diagnoses your specific needs through qualifying questions and enforces minimal, context-sensitive data passing to keep outputs focused.

Can I use context passing to connect different marketing skills in a sequence?▼

Yes, you can use context passing to connect different marketing skills in a sequence. The Orchestrator enforces minimal, context-sensitive data passing and uses a pre-built handoff protocol to maintain context and state tracking across all steps.

Why does my marketing automation workflow lack a coherent plan?▼

Your marketing automation workflow lacks a coherent plan because it misses a guided decision layer. Adding a decision tree with state tracking and a handoff protocol routes requests to the right skills and maintains context across steps.