Skills Orchestrator

Overview

The skills-orchestrator skill designs, implements, and optimizes growth loops across the skill portfolio. It connects usage, feedback, improvement, and adoption into self-reinforcing cycles that drive sustainable growth.

When to Use

• - Designing growth strategies for skills
• Creating viral or referral loops
• Optimizing skill adoption funnels
• Building user engagement mechanisms
• Planning portfolio growth initiatives
• Analyzing growth metrics and loops
• Troubleshooting growth stagnation
• Designing network effects

Core Concepts

Growth Loop Types

Type	Mechanism	Example
INLINECODE1	Users bring new users	Share results, invite others
INLINECODE2

Usage creates content | Public outputs, templates | | network | More users = more value | Collaborative features | | engagement | Usage drives more usage | Habits, streaks, rewards | | feedback | Usage improves product | Learning from actions |

Loop Components

Every growth loop has:

1. 1. Input: Users, actions, or content entering the loop
2. Action: What users do within the loop
3. Output: Results that feed back into the loop
4. Conversion: How outputs become new inputs
5. Amplification: What makes the loop grow

Loop Metrics

Metric	Description	Target
INLINECODE6	Time for one loop iteration	< 7 days
INLINECODE7

% that complete the loop | > 20% | | viral_coefficient | New users per existing user | > 0.3 | | retention | % who continue looping | > 40% | | amplification | Growth rate per cycle | > 10% |

Input

Accepts:

• - Target growth goals
• Loop design parameters (type, target user, value proposition)
• Skill portfolio context (optional, for portfolio-level analysis)

Note: This skill generates simulated metrics and design templates. It does not ingest real user behavior data or live analytics. To analyze actual usage data, you would need to provide the data as input and extend the scripts accordingly.

Output

Produces:

• - Growth loop designs (markdown templates)
• Orchestration plans (step-by-step guidance)
• Simulated metric reports (for prototyping)
• Optimization recommendations (based on loop patterns)
• A/B test plans (template structure)

Note: The "dashboards" and "metrics" produced are simulated examples for design purposes, not live data visualizations.

Workflow

Designing a Growth Loop

1. 1. Identify Core Value

- What value do users get? - What can they share or create? - What would others want?

1. 2. Map User Journey

- Entry points - Key actions - Sharing moments - Conversion paths

1. 3. Design the Loop

- Input source - Key action - Output creation - Distribution mechanism - Conversion back to input

1. 4. Add Amplification

- Incentives - Friction reduction - Network effects - Social proof

1. 5. Measure and Optimize

- Define target metrics (simulation targets) - Identify potential bottlenecks - Test improvements in design - Scale what works

Analyzing Existing Loops

1. 1. Map Current State

- Identify existing loops (conceptual) - Define expected performance - Find broken connections

1. 2. Diagnose Issues

- Where might users drop off? - What's blocking conversion? - Where is friction highest?

1. 3. Generate Solutions

- Fix broken connections - Reduce friction - Add amplification

1. 4. Test and Validate

- A/B test plans (template) - Measure impact (simulated) - Iterate quickly

Commands

Design Growth Loop

CODEBLOCK0

Analyze Current Loops

CODEBLOCK1

Track Growth Metrics

CODEBLOCK2

Run Tests

CODEBLOCK3

Output Format

Growth Loop Design

CODEBLOCK4

Components

Input

• - Source: User creates content
• Volume: ~50 outputs/day (example)
• Quality: High (user-generated)

Action

• - What: User shares output
• Where: Social, email, link
• Friction: Medium (requires action)

Output

• - Type: Sharable result
• Format: Image, link, export
• Value: Demonstrates skill capability

Conversion

• - Mechanism: View → Try
• Rate: 15% (target: 25%)
• Time: Within 24 hours

Amplification

• - Social proof: "X people used this"
• Incentive: Free credits for sharing
• Network: Collaborative features

Metrics

Metric	Example Target
Cycle Time	< 1 day
Conversion Rate

> 25% | | Viral Coefficient | > 0.5 | | Retention | > 50% |

Optimization Plan

Immediate (This Week)

1. 1. Add one-click sharing
2. Create shareable templates
3. Add social proof badges

Near-term (This Month)

1. 1. Implement referral rewards
2. Add collaboration features
3. Create public gallery

Long-term (This Quarter)

1. 1. Build network effects
2. Add team features
3. Create marketplace

Success Criteria

• - Viral coefficient > 0.5
• Cycle time < 24 hours
• 1,000 new users/month from loop

Loop Performance Dashboard (Example Template)

CODEBLOCK5

Loop Patterns

Viral Loop Pattern

Use → Create → Share → View → Signup → Use

Keys: Easy sharing, valuable output, low friction signup

Content Loop Pattern

Use → Publish → Index → Search → View → Use

Keys: SEO-friendly, public by default, discoverable

Network Loop Pattern

Join → Invite → Collaborate → Value ↑ → More Invite

Keys: Collaboration value, invite incentives, team features

Engagement Loop Pattern

Use → Reward → Habit → Daily Use → Reward

Keys: Meaningful rewards, streaks, progress

Feedback Loop Pattern

Use → Feedback → Improve → Better Experience → Use

Keys: Easy feedback, fast iteration, visible improvements

Quality Rules

• - Design loops that add value, not just growth
• Measure full loop, not just parts
• Optimize for sustainable growth
• Test before scaling
• Monitor for gaming/abuse
• Balance growth with quality

Good Trigger Examples

• - "Design a growth loop for this skill"
• "How can we make this skill viral?"
• "Analyze our current growth loops"
• "What's blocking our growth?"
• "Design a referral program"
• "How can we increase user engagement?"
• "Track our growth metrics"
• "Optimize our conversion funnel"
• "Create a network effect"

Limitations

• - Simulated data only: This skill generates simulated metrics for design/prototyping purposes. It does not connect to live analytics or ingest real user behavior data.
• Growth loops take time to validate
• Network effects need critical mass
• Viral loops are hard to predict
• Metrics can be gamed
• Growth without value is unsustainable
• Requires usage data (external) for meaningful real-world analysis

Related Skills

• - learning-evolution - For iterating on loops
• INLINECODE12 - For capturing growth insights
• INLINECODE13 - For growth strategy decisions
• INLINECODE14 - For market-based growth

Resources

scripts/

• - design-loop.sh - Design new growth loops
• INLINECODE16 - Analyze existing loops (template-based)
• INLINECODE17 - Generate simulated metric reports
• INLINECODE18 - Run validation tests

data/

• - Sample loop designs and metrics for reference