orchestrator
Skill7 starsChanged 10 months agoMITView on GitHub
Autonomous decision engine for generating complete animations from high-level descriptions. Use when you need to parse natural language animation requests, apply narrative intentionality, resolve parameters, select Disney principles, and output production-ready code with story coherence.
80 other projects use a version of this.
Adopted by
Most recently taken up by
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- Veeiy/agent-skillstheir own version, first seen Nov 8, 2026
- Mehul72/skillstheir own version, first seen Nov 8, 2026
- pietz/skillstheir own version, first seen Nov 8, 2026
- kcns008/cluster-skillstheir own version, first seen Nov 8, 2026
- johnarks/helix-looptheir own version, first seen Nov 8, 2026
Used with
Projects with it also use worker, reviewer and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
stotihvSkillworker
Execute beads autonomously within a track. Handles bead-to-bead context persistence via Agent Mail, uses preferred tools from AGENTS.md, and reports progress to orchestrator.
Also in 3 projects that use this
MicrosoftSkillreviewer
ASP.NET Core ハンドブックの記事をレビューする。Use when: 記事をレビューする、ドキュメントを校正する、コードレビューする、PRをレビューする。技術ドキュメントのレビュー、品質チェック、校正。
Also in 4 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 4 projects that use this
yakatotechSkilladvisor
Provide improvement suggestions and advice on work content. Use for document review, efficiency suggestions, and best practices
Also in 3 projects that use this
AWSSkillplanning
Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.
Also in 3 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
Other versions80 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 80
- nubjs/nub★ 4.4ksame name
- SirAllap/agentglass★ 347same name
- DylXBT/claude-orchestrator-skills★ 114same name
- nwiizo/claudelytics★ 88same name
- nahisaho/MUSUBI★ 74same name
- olivieropinotti/orchestrator-skill★ 70same name
- sanky369/vibe-building-skills★ 30same name
- felvieira/claude-skills-fv★ 27same name
- robertbstillwell/marketing-skills★ 26same name
- kcns008/cluster-agent-swarm-skills★ 25same name
70 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository87 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- motion-designSkill
- 3d-transformsSkill
- accessibilitySkill
- android-nativeSkill
- animation-recipesSkill
- anticipationSkill
- arc-motionSkill
- attention-choreographySkill
- attentionSkill
- audio-reactiveSkill
- blurSkill
- brand-animationSkill
- cameraSkill
- characterSkill
- choice-resolutionSkill
- cinematicSkill
- code-generationSkill
- colorSkill
- component-animationsSkill
- compositingSkill
- consequenceSkill
- container-transformSkill
- css-advancedSkill
- data-visualizationSkill
- depthSkill
- distortionSkill
- dramaturgySkill
- durationSkill
- easingSkill
- emotional-journeySkill
- emotion-mappingSkill
- emotion-selectionSkill
- empty-statesSkill
- entrance-patternsSkill
- exaggerationSkill
- exit-patternsSkill
- exportSkill
- figma-integrationSkill
- follow-throughSkill
- frame-timingSkill
- gesture-motionSkill
- glow-shadowSkill
- intentSkill
- ios-nativeSkill
- loading-statesSkill
- loopingSkill
- lottieSkill
- masksSkill
- microstateSkill
- morphingSkill
- motion-auditSkill
- motion-blurSkill
- motion-principlesSkill
- motion-specsSkill
- narrative-arcSkill
- notificationsSkill
- onboardingSkill
- opacitySkill
- particlesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 289
When generating animations autonomously:
- Distinctive: line 293
Apply emotion: if specified or inferred
“Common” is measured: kept by at least 6 in 10 of the 66 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Motion Orchestrator
Autonomous decision engine for generating complete animations from high-level descriptions. The orchestrator parses input, applies narrative intentionality, resolves parameters via unified pipeline, selects appropriate Disney principles, and outputs production-ready code.
Orchestration Pipeline (v3.0 — Narrative + Resolution)
Input Description
│
▼
┌──────────────────┐
│ Input Parser │ → Extract: element, action, emotion, brand, platform
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Intent Parser │ → What PURPOSE? (clarify/guide/confirm/warn/celebrate/reveal)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Journey State │ → Where emotionally? (curious/engaged/accomplished)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Narrative Arc │ → What story phase? (exposition/rising/climax/resolution)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Scene Composer │ → Dramaturgical structure (beats, pauses, rhythm)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Attention Path │ → Reading order (F-pattern/Z-pattern/center-out)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Consequence │ → Cause-effect chains (direct/ripple/cascade/echo)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Microstate │ → Component state machines (idle→active→success)
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Recipe Matcher │ → Find matching recipe or compose new
└────────┬─────────┘
│
▼
┌──────────────────┐
│Parameter Resolver│ → Merge recipe + emotion + brand + platform
└────────┬─────────┘
│
▼
┌──────────────────┐
│Principle Select │ → Which Disney principles apply?
└────────┬─────────┘
│
▼
┌──────────────────┐
│Conflict Resolver │ → Handle competing requirements
└────────┬─────────┘
│
▼
┌──────────────────┐
│ Code Generator │ → Output for target platform
└────────┬─────────┘
│
▼
Complete Animation with StoryNarrative Layer (v3.0)
Intent Detection
Parse semantic purpose from the request:
| Keywords | Intent | Speed | Intensity |
| explain, show, reveal | clarify | measured | 0.4 |
| lead, direct, point | guide | deliberate | 0.5 |
| done, saved, submitted | confirm | responsive | 0.6 |
| error, danger, alert | warn | urgent | 0.8 |
| success, complete, win | celebrate | expressive | 1.0 |
| unveil, discover, unlock | reveal | dramatic | 0.7 |
Journey State Detection
Determine user's emotional position:
| Context | Journey State | Next States |
| First interaction | curious | engaged, confused |
| Active engagement | engaged | accomplished, frustrated |
| Task completed | accomplished | delighted, engaged |
| Multiple successes | delighted | neutral |
Arc Phase Selection
Map to Freytag's pyramid for UI:
| Duration | Arc Preset | Phases |
| <400ms | micro | incident → climax → resolution |
| 400-800ms | short | exposition → rising → climax → resolution |
| 800-2000ms | medium | all five phases |
| >2000ms | extended | full with sub-beats |
Consequence Chain Selection
| Pattern | Timing | Use Case |
direct | 0ms | Immediate feedback |
ripple | 30ms/step | Radiating effects |
cascade | 50ms/step | Sequential flow |
echo | 200ms | Delayed reflection |
Phase 1: Input Parser
Element Detection
| Keywords | Element Type |
| button, btn, cta | button |
| card, tile, panel | card |
| modal, dialog, overlay | modal |
| list, items, grid | list |
| toast, notification | toast |
| menu, dropdown | dropdown |
Action Detection
| Keywords | Action Type |
| click, press, tap | press |
| hover, mouse over | hover |
| enter, appear, show | entrance |
| exit, leave, close | exit |
| error, fail | error |
| success, complete | success |
Emotion Detection
| Keywords | Emotion |
| bouncy, fun, playful | playful |
| elegant, refined, subtle | professional |
| celebratory, exciting | celebratory |
| calming, gentle | calming |
| urgent, important | urgent |
Phase 2: Parameter Resolution
Resolution Order
Recipe (base) → Emotion (modifier) → Brand (constraint) → Platform (adaptation) → Bounds → Accessibility (override)Resolution Algorithm
function resolveParameters(
recipe: Recipe,
emotions: WeightedEmotion[],
brand: Brand,
platform: Platform,
context: Context
): ResolvedParams {
// 1. Start with recipe base
let duration = recipe.duration;
let easing = recipe.easing;
let exaggeration = recipe.exaggeration ?? 1.0;
// 2. Blend emotions (weighted average for numeric, dominant for discrete)
const blendedEmotion = blendEmotions(emotions);
// 3. Apply blended emotion as modifier
if (blendedEmotion) {
duration *= blendedEmotion.durationMultiplier;
easing = blendedEmotion.easing ?? easing;
exaggeration *= blendedEmotion.exaggerationBoost ?? 1.0;
}
// 4. Apply brand constraints (caps, not multipliers)
if (brand) {
exaggeration = Math.min(exaggeration, brand.maxExaggeration);
if (!brand.allowsSquashStretch) squashStretch = "none";
}
// 5. Apply platform adaptation
duration *= platform.durationMultiplier;
// 6. Clamp to bounds
duration = clamp(duration, platform.minDuration, platform.maxDuration);
// 7. Accessibility override (bypasses all above)
if (context.reducedMotion) {
return recipe.reducedMotion ?? DEFAULT_REDUCED_MOTION;
}
return { duration, easing, exaggeration, ... };
}Platform Multipliers
| Platform | Duration | Max | Min |
| web | 1.0× | 600ms | 50ms |
| video | 0.6× | 400ms | 50ms |
| mobile | 1.1× | 500ms | 50ms |
Resolution Checklist
- Emotions blended before applying (prevents stacking)
- Brand constraints enforced (caps exaggeration, disables features)
- Platform multiplier applied
- Duration clamped to bounds
- Reduced motion checked last (overrides all)
Phase 3: Principle Selection
Decision Tree
Does it bounce or impact?
Yes -> SQUASH-STRETCH
No -> Skip
Does it move through space?
Yes -> ARC-MOTION
No -> Linear path OK
Is it a significant action?
Yes -> ANTICIPATION (15-25% of total)
No -> Skip
Are there secondary elements?
Yes -> FOLLOW-THROUGH (10-30% stagger)
No -> Single elementPhase 4: Conflict Resolution
Priority Rules
- Accessibility > Everything - Reduced motion always wins
- Brand > Emotion - Brand consistency trumps momentary emotion
- Context > Defaults - Device capability limits animations
- Duration Conflicts - Average within brand bounds
function resolveConflicts(params: Parameters, context: Context): Parameters {
if (context.reducedMotion) {
params = applyReducedMotionLimits(params);
}
params = clampToBrandLimits(params, context.brand);
params = clampToDeviceLimits(params, context.device);
return params;
}Phase 5: Output Generation
Platform Selection
| Platform | Output Format |
| CSS | Keyframes + transitions + media queries |
| GSAP | Timeline with tweens |
| Framer Motion | Variants + transitions |
| Remotion | Interpolate functions + spring |
Autonomous Generation Workflow
When generating animations autonomously:
- Parse the request using keyword detection
- Match to recipe or compose from principles
- Apply emotion if specified or inferred
- Apply brand constraints
- Check accessibility requirements
- Generate code for all platforms
- Include reduced motion alternative
- Document token references
Decision Checklist
- Element type identified
- Action type identified
- Platform identified (web/video/mobile)
- Emotion determined (explicit or inferred)
- Emotions blended if multiple
- Parameters resolved via resolution pipeline
- Brand constraints applied (caps, not stacking)
- Duration within platform bounds (50-600ms web, 50-400ms video)
- Intent parsed (clarify/guide/confirm/warn/celebrate/reveal)
- Journey state identified (curious/engaged/accomplished)
- Narrative arc selected (micro/short/medium/extended)
- Attention path planned (F-pattern/Z-pattern/center-out)
- Consequence chain defined (direct/ripple/cascade/echo)
- Microstate machine configured (component states + transitions)
- Disney principles selected
- Conflicts resolved
- Code generated for target platform
- Reduced motion included
- Performance considerations noted
- Determinism verified (same inputs = same outputs)
Related Skills
Core
choice-resolution/- Unified parameter resolution pipelinemotion-principles/- Disney 12 principleseasing/- Easing curve selectionduration/- Duration token selectionaccessibility/- Reduced motion requirementsanimation-recipes/- Recipe definitions and selectionemotion-mapping/- Emotion-to-parameter mappingplatform-adaptation/- Platform-specific adjustmentstools/- Platform-specific code generation
Narrative (v3.0)
intent/- Semantic motion purposeemotional-journey/- User emotional state machinenarrative-arc/- Story structure for motiondramaturgy/- Scene composition and pacingattention-choreography/- Reading order and gaze pathsconsequence/- Cause-effect animation chainsmicrostate/- Component state orchestration
See references/ for complete recipe matching tables and emotion mapping.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

