Route multi-step marketing, product, or business challenges to the right sequence of ClawFu skills. Recommends which frameworks to combine, in what order, with handoff outputs between steps. Use when: planning a product launch end-to-end, combining positioning + offers + launch skills, running a customer-validation sprint, creating a content strategy pipeline, deciding which skills to chain for a complex project, or orchestrating a sales-enablement playbook.
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill skill-orchestrator
> Route multi-step challenges to the right sequence of ClawFu skills — recommending which frameworks to combine, in what order, with explicit handoff outputs between steps.
| Aspect | Details |
|--------|---------|
| Source | ClawFu Skills orchestration system |
| Core Principle | The right frameworks in the right order compound insights — sequencing matters more than any single skill |
| Sequencing Logic | Foundation → Analysis → Strategy → Creation → Validation → Execution |
| Claude Does | You Decide |
|-------------|------------|
| Recommends skill sequences for a challenge | Which skills to skip or substitute |
| Defines input/output handoffs between steps | Final strategic direction at each step |
| Creates custom workflows from the skill library | Resource allocation and timeline |
| Identifies when to branch or loop back | Go/no-go decisions at validation gates |
Classify the challenge type and context:
| Factor | Options |
|--------|---------|
| Type | Launch · Validation · Content · Positioning · Decision · Sales · Video |
| Stage | Idea · Early · Growth · Mature |
| Resources | Solo · Small team · Large team |
| Timeline | Urgent · Normal · Flexible |
Check pre-built workflows in WORKFLOWS.md. If none fits, build a custom sequence following this phase order:
| Phase | Skill Types | Purpose |
|-------|-------------|---------|
| 1. Foundation | first-principles, JTBD, audience-research | Understand reality |
| 2. Analysis | competitive-analysis, inversion, pre-mortem | Identify challenges |
| 3. Strategy | positioning, category-design, personas | Make strategic choices |
| 4. Creation | offers, copy, content | Build the deliverable |
| 5. Validation | six-thinking-hats, pricing-validation | Stress test |
| 6. Execution | launch-formula, sales-pitch | Go to market |
For each step in the sequence:
Validation checkpoint: Before moving to the next skill, confirm the output includes the specific artifacts the next step needs. If not, iterate or add an intermediate step.
After completing the sequence:
Challenge: Launching an AI writing tool for marketers in a competitive market (Jasper, Copy.ai)
Recommended sequence (modified Product Launch):
1. competitive-analysis → Map landscape (Jasper, Copy.ai, ChatGPT)
2. first-principles → Challenge "AI writing tool" category assumptions
3. persona-generator → Define specific segments (not just "marketers")
4. category-design → Can you own a new category?
5. positioning → Differentiate using competitive gaps
6. grand-slam-offers → Create irresistible offer structure
7. pre-mortem → What could kill the launch?
8. launch-formula → Sequence the mechanics
Handoff example: Step 3 (personas) feeds into Step 5 (positioning) — persona pain points define which competitive alternatives matter most.
See WORKFLOWS.md for all pre-built workflows (Product Launch, Customer Validation, Content Strategy, Competitive Positioning, Sales Enablement, Decision Making, AI Video Production).
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take guia-matthieu/skill-orchestrator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.