[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73APA29FBE76CNY99A7AFGT":3,"skill-same:01M73APA29FBE76CNY99A7AFGT":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M73APA29FBE76CNY99A7AFGT","onboarding-orchestrator",null,"Design and execute customer onboarding playbooks with milestones, success metrics, and automated touchpoints","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fonboarding-orchestrator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: onboarding-orchestrator\ndescription: Design and execute customer onboarding playbooks with milestones, success metrics, and automated touchpoints\nlicense: MIT\nmetadata:\n  author: ClawFu\n  version: 1.0.0\n  mcp-server: \"@clawfu\u002Fmcp-skills\"\n---\n\n# Onboarding Orchestrator\n\n> Create structured onboarding programs that drive rapid time-to-value through milestone-based playbooks, proactive touchpoints, and early success metrics.\n\n## When to Use This Skill\n\n- Designing new onboarding programs\n- Improving existing onboarding metrics\n- Creating segment-specific playbooks\n- Automating onboarding touchpoints\n- Measuring onboarding effectiveness\n\n## Methodology Foundation\n\nBased on **Lincoln Murphy's First Value Delivery** and **Gainsight Onboarding Best Practices**, focusing on:\n- Time to First Value (TTFV)\n- Milestone-based progression\n- Success criteria definition\n- Risk identification during ramp\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Designs milestone frameworks | Implementation timeline |\n| Creates touchpoint schedules | Resource allocation |\n| Identifies success metrics | Definition of \"success\" |\n| Suggests automation triggers | Tool selection |\n| Builds playbook templates | Customization per segment |\n\n## Instructions\n\n### Step 1: Define Onboarding Phases\n\n**Standard 4-Phase Model:**\n\n| Phase | Duration | Focus | Exit Criteria |\n|-------|----------|-------|---------------|\n| **Kickoff** | Week 1 | Alignment, access | Kickoff complete, logins work |\n| **Setup** | Week 2-3 | Configuration | Core setup done |\n| **Adoption** | Week 4-6 | First use case | TTFV achieved |\n| **Optimization** | Week 7-12 | Full rollout | Steady state reached |\n\n### Step 2: Map Milestones per Phase\n\n**Kickoff Milestones:**\n- [ ] Kickoff call completed\n- [ ] Success criteria documented\n- [ ] Admin account created\n- [ ] Integration requirements identified\n- [ ] Timeline agreed\n\n**Setup Milestones:**\n- [ ] Technical setup complete\n- [ ] Data migration (if needed)\n- [ ] Integrations connected\n- [ ] User accounts provisioned\n- [ ] Admin trained\n\n**Adoption Milestones:**\n- [ ] First workflow created\n- [ ] 50% users logged in\n- [ ] First value moment achieved\n- [ ] End user training complete\n- [ ] Champion identified\n\n**Optimization Milestones:**\n- [ ] 80% users active\n- [ ] Full use case deployed\n- [ ] Self-service adoption\n- [ ] QBR scheduled\n- [ ] Expansion discussed\n\n### Step 3: Design Touchpoint Cadence\n\n| Day | Type | Purpose | Owner |\n|-----|------|---------|-------|\n| 0 | Email | Welcome + next steps | Auto |\n| 1 | Call | Kickoff call | CSM |\n| 3 | Email | Setup checklist | Auto |\n| 7 | Call | Setup review | CSM |\n| 14 | Email | Training resources | Auto |\n| 21 | Call | Adoption check-in | CSM |\n| 30 | Email | 30-day survey | Auto |\n| 45 | Call | Value review | CSM |\n| 60 | Email | Optimization tips | Auto |\n| 90 | Call | QBR\u002FHealth check | CSM |\n\n### Step 4: Define Success Metrics\n\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| Time to Kickoff | \u003C3 days | Contract → Kickoff |\n| Time to Setup | \u003C14 days | Kickoff → Setup complete |\n| Time to First Value | \u003C30 days | Contract → First use case |\n| 30-day activation | >70% | Users logged in |\n| 60-day adoption | >50% | Users weekly active |\n| Onboarding CSAT | >4.5 | Survey score |\n| Onboarding NPS | >50 | Survey score |\n\n## Examples\n\n### Example 1: B2B SaaS Onboarding Playbook\n\n**Output:**\n```\n## Customer Onboarding Playbook: Enterprise Segment\n\n### Overview\n- **Segment**: Enterprise ($100K+ ARR)\n- **Target TTFV**: 45 days\n- **CSM:Account Ratio**: 1:15\n- **Onboarding Duration**: 90 days\n\n---\n\n### Phase 1: Kickoff (Days 0-7)\n\n**Objectives:**\n- Establish relationship and trust\n- Align on success criteria\n- Set expectations and timeline\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| Welcome email sent | Auto | 0 | |\n| Kickoff scheduled | CSM | 1 | |\n| Kickoff call completed | CSM | 3 | |\n| Success criteria doc sent | CSM | 4 | |\n| Technical requirements gathered | CSM | 5 | |\n| Project plan shared | CSM | 7 | |\n\n**Kickoff Call Agenda (60 min):**\n1. Introductions (5 min)\n2. Business objectives (15 min)\n3. Success criteria definition (15 min)\n4. Technical overview (10 min)\n5. Timeline and milestones (10 min)\n6. Q&A and next steps (5 min)\n\n**Success Criteria Template:**\n```markdown\n## [Customer] Success Criteria\n\n**Business Objectives:**\n1. [Primary goal]\n2. [Secondary goal]\n\n**Success Metrics:**\n| Metric | Baseline | Target | Timeline |\n|--------|----------|--------|----------|\n| [Metric 1] | X | Y | 90 days |\n\n**Key Stakeholders:**\n| Name | Role | Involvement |\n|------|------|-------------|\n\n**Risks\u002FDependencies:**\n-\n```\n\n**Exit Criteria → Phase 2:**\n- [ ] Kickoff call complete\n- [ ] Success criteria documented and signed off\n- [ ] Technical requirements understood\n- [ ] Project timeline agreed\n\n---\n\n### Phase 2: Setup (Days 8-21)\n\n**Objectives:**\n- Complete technical implementation\n- Configure product for use case\n- Provision and train admins\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| SSO\u002FAuth configured | Tech | 10 | |\n| Core integration connected | Tech | 12 | |\n| Data migration complete | Tech | 14 | |\n| Admin accounts created | CSM | 14 | |\n| Admin training session | CSM | 16 | |\n| Setup review call | CSM | 21 | |\n\n**Setup Check-In Call (Day 14, 30 min):**\n1. Progress review (10 min)\n2. Blocker resolution (10 min)\n3. Admin training preview (5 min)\n4. Next steps (5 min)\n\n**Admin Training Agenda (60 min):**\n1. Platform overview (15 min)\n2. User management (15 min)\n3. Core workflows (20 min)\n4. Reporting basics (10 min)\n\n**Exit Criteria → Phase 3:**\n- [ ] Technical setup 100% complete\n- [ ] At least 1 admin trained\n- [ ] Users provisioned\n- [ ] No open blockers\n\n---\n\n### Phase 3: Adoption (Days 22-45)\n\n**Objectives:**\n- Achieve first value moment\n- Drive user adoption\n- Establish usage patterns\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| End user training scheduled | CSM | 22 | |\n| First training session | CSM | 25 | |\n| First workflow live | Customer | 28 | |\n| 50% users logged in | - | 30 | |\n| First value achieved | - | 35 | |\n| Adoption review call | CSM | 45 | |\n\n**End User Training (60 min per session):**\n- Session 1: Core functionality\n- Session 2: Advanced features\n- Session 3: Best practices\n\n**First Value Checklist:**\n- [ ] Primary use case configured\n- [ ] First real work completed\n- [ ] Customer confirms value\n- [ ] Quote-worthy moment captured\n\n**30-Day Survey:**\n```\n1. How easy was onboarding? (1-5)\n2. Did you achieve your first goal? (Y\u002FN)\n3. What could we improve?\n4. NPS: How likely to recommend? (0-10)\n```\n\n**Exit Criteria → Phase 4:**\n- [ ] First value moment achieved\n- [ ] 50%+ users logged in\n- [ ] No critical blockers\n- [ ] Customer confirms progress\n\n---\n\n### Phase 4: Optimization (Days 46-90)\n\n**Objectives:**\n- Full use case deployment\n- Drive to steady-state adoption\n- Prepare for ongoing success\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| Second use case identified | CSM | 50 | |\n| Full team rollout | Customer | 60 | |\n| 80% adoption achieved | - | 75 | |\n| QBR scheduled | CSM | 80 | |\n| Handoff to ongoing success | CSM | 90 | |\n\n**60-Day Check-In (30 min):**\n1. Adoption metrics review (10 min)\n2. Value realization check (10 min)\n3. Expansion opportunities (5 min)\n4. Ongoing cadence (5 min)\n\n**90-Day QBR Handoff:**\n- Full value review\n- Health score baseline\n- Ongoing success plan\n- Expansion discussion\n\n---\n\n### Automation Triggers\n\n| Trigger | Action | Timing |\n|---------|--------|--------|\n| Contract signed | Welcome email | Immediate |\n| Day 3, no kickoff | Alert CSM | Day 3 |\n| Setup incomplete | Nudge email | Day 18 |\n| Day 30, \u003C25% login | Risk alert | Day 30 |\n| First value achieved | Celebration email | On event |\n| Day 45, low adoption | Intervention call | Day 45 |\n\n---\n\n### Risk Indicators\n\n| Signal | Risk Level | Response |\n|--------|------------|----------|\n| No kickoff by Day 5 | 🟠 High | Escalate internally |\n| Setup blocked >7 days | 🟠 High | Technical escalation |\n| \u003C25% login at Day 30 | 🔴 Critical | Intervention call |\n| Champion disengaged | 🟠 High | Find alternate contact |\n| No first value by Day 45 | 🔴 Critical | Executive involvement |\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Structuring onboarding programs\n- Defining milestones and metrics\n- Creating touchpoint schedules\n- Building playbook templates\n\n### What This Skill Cannot Do\n- Know your specific product setup\n- Execute onboarding automatically\n- Replace customer relationship skills\n- Predict implementation blockers\n\n### When to Escalate to Human\n- Technical implementation issues\n- Customer relationship problems\n- Scope changes or delays\n- Executive involvement needs\n\n## References\n\n- Lincoln Murphy's Customer Success Onboarding\n- Gainsight Onboarding Best Practices\n- Totango Time to First Value Guide\n- ChurnZero Onboarding Automation\n\n## Related Skills\n\n- `account-health` - Post-onboarding health\n- `churn-prediction` - Onboarding risk signals\n- `expansion-signals` - Early expansion opportunities\n\n## Skill Metadata\n\n- **Domain**: Customer Success\n- **Complexity**: Intermediate\n- **Mode**: cyborg\n- **Time to Value**: 2-4 hours for playbook design\n- **Prerequisites**: Product knowledge, segment definitions\n","# Onboarding Orchestrator\n\n> Create structured onboarding programs that drive rapid time-to-value through milestone-based playbooks, proactive touchpoints, and early success metrics.\n\n## When to Use This Skill\n\n- Designing new onboarding programs\n- Improving existing onboarding metrics\n- Creating segment-specific playbooks\n- Automating onboarding touchpoints\n- Measuring onboarding effectiveness\n\n## Methodology Foundation\n\nBased on **Lincoln Murphy's First Value Delivery** and **Gainsight Onboarding Best Practices**, focusing on:\n- Time to First Value (TTFV)\n- Milestone-based progression\n- Success criteria definition\n- Risk identification during ramp\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Designs milestone frameworks | Implementation timeline |\n| Creates touchpoint schedules | Resource allocation |\n| Identifies success metrics | Definition of \"success\" |\n| Suggests automation triggers | Tool selection |\n| Builds playbook templates | Customization per segment |\n\n## Instructions\n\n### Step 1: Define Onboarding Phases\n\n**Standard 4-Phase Model:**\n\n| Phase | Duration | Focus | Exit Criteria |\n|-------|----------|-------|---------------|\n| **Kickoff** | Week 1 | Alignment, access | Kickoff complete, logins work |\n| **Setup** | Week 2-3 | Configuration | Core setup done |\n| **Adoption** | Week 4-6 | First use case | TTFV achieved |\n| **Optimization** | Week 7-12 | Full rollout | Steady state reached |\n\n### Step 2: Map Milestones per Phase\n\n**Kickoff Milestones:**\n- [ ] Kickoff call completed\n- [ ] Success criteria documented\n- [ ] Admin account created\n- [ ] Integration requirements identified\n- [ ] Timeline agreed\n\n**Setup Milestones:**\n- [ ] Technical setup complete\n- [ ] Data migration (if needed)\n- [ ] Integrations connected\n- [ ] User accounts provisioned\n- [ ] Admin trained\n\n**Adoption Milestones:**\n- [ ] First workflow created\n- [ ] 50% users logged in\n- [ ] First value moment achieved\n- [ ] End user training complete\n- [ ] Champion identified\n\n**Optimization Milestones:**\n- [ ] 80% users active\n- [ ] Full use case deployed\n- [ ] Self-service adoption\n- [ ] QBR scheduled\n- [ ] Expansion discussed\n\n### Step 3: Design Touchpoint Cadence\n\n| Day | Type | Purpose | Owner |\n|-----|------|---------|-------|\n| 0 | Email | Welcome + next steps | Auto |\n| 1 | Call | Kickoff call | CSM |\n| 3 | Email | Setup checklist | Auto |\n| 7 | Call | Setup review | CSM |\n| 14 | Email | Training resources | Auto |\n| 21 | Call | Adoption check-in | CSM |\n| 30 | Email | 30-day survey | Auto |\n| 45 | Call | Value review | CSM |\n| 60 | Email | Optimization tips | Auto |\n| 90 | Call | QBR\u002FHealth check | CSM |\n\n### Step 4: Define Success Metrics\n\n| Metric | Target | Measurement |\n|--------|--------|-------------|\n| Time to Kickoff | \u003C3 days | Contract → Kickoff |\n| Time to Setup | \u003C14 days | Kickoff → Setup complete |\n| Time to First Value | \u003C30 days | Contract → First use case |\n| 30-day activation | >70% | Users logged in |\n| 60-day adoption | >50% | Users weekly active |\n| Onboarding CSAT | >4.5 | Survey score |\n| Onboarding NPS | >50 | Survey score |\n\n## Examples\n\n### Example 1: B2B SaaS Onboarding Playbook\n\n**Output:**\n```\n## Customer Onboarding Playbook: Enterprise Segment\n\n### Overview\n- **Segment**: Enterprise ($100K+ ARR)\n- **Target TTFV**: 45 days\n- **CSM:Account Ratio**: 1:15\n- **Onboarding Duration**: 90 days\n\n---\n\n### Phase 1: Kickoff (Days 0-7)\n\n**Objectives:**\n- Establish relationship and trust\n- Align on success criteria\n- Set expectations and timeline\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| Welcome email sent | Auto | 0 | |\n| Kickoff scheduled | CSM | 1 | |\n| Kickoff call completed | CSM | 3 | |\n| Success criteria doc sent | CSM | 4 | |\n| Technical requirements gathered | CSM | 5 | |\n| Project plan shared | CSM | 7 | |\n\n**Kickoff Call Agenda (60 min):**\n1. Introductions (5 min)\n2. Business objectives (15 min)\n3. Success criteria definition (15 min)\n4. Technical overview (10 min)\n5. Timeline and milestones (10 min)\n6. Q&A and next steps (5 min)\n\n**Success Criteria Template:**\n```markdown\n## [Customer] Success Criteria\n\n**Business Objectives:**\n1. [Primary goal]\n2. [Secondary goal]\n\n**Success Metrics:**\n| Metric | Baseline | Target | Timeline |\n|--------|----------|--------|----------|\n| [Metric 1] | X | Y | 90 days |\n\n**Key Stakeholders:**\n| Name | Role | Involvement |\n|------|------|-------------|\n\n**Risks\u002FDependencies:**\n-\n```\n\n**Exit Criteria → Phase 2:**\n- [ ] Kickoff call complete\n- [ ] Success criteria documented and signed off\n- [ ] Technical requirements understood\n- [ ] Project timeline agreed\n\n---\n\n### Phase 2: Setup (Days 8-21)\n\n**Objectives:**\n- Complete technical implementation\n- Configure product for use case\n- Provision and train admins\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| SSO\u002FAuth configured | Tech | 10 | |\n| Core integration connected | Tech | 12 | |\n| Data migration complete | Tech | 14 | |\n| Admin accounts created | CSM | 14 | |\n| Admin training session | CSM | 16 | |\n| Setup review call | CSM | 21 | |\n\n**Setup Check-In Call (Day 14, 30 min):**\n1. Progress review (10 min)\n2. Blocker resolution (10 min)\n3. Admin training preview (5 min)\n4. Next steps (5 min)\n\n**Admin Training Agenda (60 min):**\n1. Platform overview (15 min)\n2. User management (15 min)\n3. Core workflows (20 min)\n4. Reporting basics (10 min)\n\n**Exit Criteria → Phase 3:**\n- [ ] Technical setup 100% complete\n- [ ] At least 1 admin trained\n- [ ] Users provisioned\n- [ ] No open blockers\n\n---\n\n### Phase 3: Adoption (Days 22-45)\n\n**Objectives:**\n- Achieve first value moment\n- Drive user adoption\n- Establish usage patterns\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| End user training scheduled | CSM | 22 | |\n| First training session | CSM | 25 | |\n| First workflow live | Customer | 28 | |\n| 50% users logged in | - | 30 | |\n| First value achieved | - | 35 | |\n| Adoption review call | CSM | 45 | |\n\n**End User Training (60 min per session):**\n- Session 1: Core functionality\n- Session 2: Advanced features\n- Session 3: Best practices\n\n**First Value Checklist:**\n- [ ] Primary use case configured\n- [ ] First real work completed\n- [ ] Customer confirms value\n- [ ] Quote-worthy moment captured\n\n**30-Day Survey:**\n```\n1. How easy was onboarding? (1-5)\n2. Did you achieve your first goal? (Y\u002FN)\n3. What could we improve?\n4. NPS: How likely to recommend? (0-10)\n```\n\n**Exit Criteria → Phase 4:**\n- [ ] First value moment achieved\n- [ ] 50%+ users logged in\n- [ ] No critical blockers\n- [ ] Customer confirms progress\n\n---\n\n### Phase 4: Optimization (Days 46-90)\n\n**Objectives:**\n- Full use case deployment\n- Drive to steady-state adoption\n- Prepare for ongoing success\n\n**Milestones:**\n| Milestone | Owner | Day | Status |\n|-----------|-------|-----|--------|\n| Second use case identified | CSM | 50 | |\n| Full team rollout | Customer | 60 | |\n| 80% adoption achieved | - | 75 | |\n| QBR scheduled | CSM | 80 | |\n| Handoff to ongoing success | CSM | 90 | |\n\n**60-Day Check-In (30 min):**\n1. Adoption metrics review (10 min)\n2. Value realization check (10 min)\n3. Expansion opportunities (5 min)\n4. Ongoing cadence (5 min)\n\n**90-Day QBR Handoff:**\n- Full value review\n- Health score baseline\n- Ongoing success plan\n- Expansion discussion\n\n---\n\n### Automation Triggers\n\n| Trigger | Action | Timing |\n|---------|--------|--------|\n| Contract signed | Welcome email | Immediate |\n| Day 3, no kickoff | Alert CSM | Day 3 |\n| Setup incomplete | Nudge email | Day 18 |\n| Day 30, \u003C25% login | Risk alert | Day 30 |\n| First value achieved | Celebration email | On event |\n| Day 45, low adoption | Intervention call | Day 45 |\n\n---\n\n### Risk Indicators\n\n| Signal | Risk Level | Response |\n|--------|------------|----------|\n| No kickoff by Day 5 | 🟠 High | Escalate internally |\n| Setup blocked >7 days | 🟠 High | Technical escalation |\n| \u003C25% login at Day 30 | 🔴 Critical | Intervention call |\n| Champion disengaged | 🟠 High | Find alternate contact |\n| No first value by Day 45 | 🔴 Critical | Executive involvement |\n```\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Structuring onboarding programs\n- Defining milestones and metrics\n- Creating touchpoint schedules\n- Building playbook templates\n\n### What This Skill Cannot Do\n- Know your specific product setup\n- Execute onboarding automatically\n- Replace customer relationship skills\n- Predict implementation blockers\n\n### When to Escalate to Human\n- Technical implementation issues\n- Customer relationship problems\n- Scope changes or delays\n- Executive involvement needs\n\n## References\n\n- Lincoln Murphy's Customer Success Onboarding\n- Gainsight Onboarding Best Practices\n- Totango Time to First Value Guide\n- ChurnZero Onboarding Automation\n\n## Related Skills\n\n- `account-health` - Post-onboarding health\n- `churn-prediction` - Onboarding risk signals\n- `expansion-signals` - Early expansion opportunities\n\n## Skill Metadata\n\n- **Domain**: Customer Success\n- **Complexity**: Intermediate\n- **Mode**: cyborg\n- **Time to Value**: 2-4 hours for playbook design\n- **Prerequisites**: Product knowledge, segment definitions\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25,"mcp-server":26},"ClawFu","1.0.0","@clawfu\u002Fmcp-skills","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fonboarding-orchestrator",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add roohe\u002Fagentic-super-skills --skill onboarding-orchestrator",{"tool":41,"command":42},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill onboarding-orchestrator",{"tool":44,"command":45},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill onboarding-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fonboarding-orchestrator\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]