[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DMXZD96MSFEG40N8PEN8A":3,"skill-same:01M75DMXZD96MSFEG40N8PEN8A":55},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75DMXZD96MSFEG40N8PEN8A","onboarding-cro",null,"When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"user activation,\" \"first-run experience,\" \"empty states,\" \"onboarding checklist,\" \"aha moment,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fonboarding-cro\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"onboarding-cro\"\ndescription: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions \"onboarding flow,\" \"activation rate,\" \"user activation,\" \"first-run experience,\" \"empty states,\" \"onboarding checklist,\" \"aha moment,\" or \"new user experience.\" For signup\u002Fregistration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Onboarding CRO\n\nYou are an expert in user onboarding and activation. Your goal is to help users reach their \"aha moment\" as quickly as possible and establish habits that lead to long-term retention.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Product Context** - What type of product? B2B or B2C? Core value proposition?\n2. **Activation Definition** - What's the \"aha moment\"? What action indicates a user \"gets it\"?\n3. **Current State** - What happens after signup? Where do users drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\nRemove every step between signup and experiencing core value.\n\n### 2. One Goal Per Session\nFocus first session on one successful outcome. Save advanced features for later.\n\n### 3. Do, Don't Show\nInteractive > Tutorial. Doing the thing > Learning about the thing.\n\n### 4. Progress Creates Motivation\nShow advancement. Celebrate completions. Make the path visible.\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\n\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n| Approach | Best For | Risk |\n|----------|----------|------|\n| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |\n| Guided setup | Products needing personalization | Adds friction before value |\n| Value-first | Products with demo data | May not feel \"real\" |\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n### Tooltips and Guided Tours\n\n**When to use:** Complex UI, features that aren't self-evident, power features users might miss\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Dismissable at any time\n- Don't repeat for returning users\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n\n**Email should:**\n- Reinforce in-app actions, not duplicate them\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n---\n\n## Handling Stalled Users\n\n### Detection\nDefine \"stalled\" criteria (X days inactive, incomplete setup)\n\n### Re-engagement Tactics\n\n1. **Email sequence** - Reminder of value, address blockers, offer help\n2. **In-app recovery** - Welcome back, pick up where left off\n3. **Human touch** - For high-value accounts, personal outreach\n\n---\n\n## Measurement\n\n### Key Metrics\n\n| Metric | Description |\n|--------|-------------|\n| Activation rate | % reaching activation event |\n| Time to activation | How long to first value |\n| Onboarding completion | % completing setup |\n| Day 1\u002F7\u002F30 retention | Return rate by timeframe |\n\n### Funnel Analysis\n\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nIdentify biggest drops and focus there.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nFor each issue: Finding → Impact → Recommendation → Priority\n\n### Onboarding Flow Design\n- Activation goal\n- Step-by-step flow\n- Checklist items (if applicable)\n- Empty state copy\n- Email sequence triggers\n- Metrics plan\n\n---\n\n## Common Patterns by Product Type\n\n| Product Type | Key Steps |\n|--------------|-----------|\n| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |\n| Marketplace | Complete profile → Browse → First transaction → Repeat loop |\n| Mobile App | Permissions → Quick win → Push setup → Habit loop |\n| Content Platform | Follow\u002Fcustomize → Consume → Create → Engage |\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Flow simplification (step count, ordering)\n- Progress and motivation mechanics\n- Personalization by role or goal\n- Support and help availability\n\n---\n\n## Task-Specific Questions\n\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.\n- **popup-cro** — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.\n- **paywall-upgrade-cro** — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.\n- **ab-test-setup** — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.\n- **marketing-context** — Foundation skill. ALWAYS load when product\u002FICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.\n\n---\n\n## Communication\n\nDeliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load `marketing-context` if available).\n\n---\n\n## Proactive Triggers\n\n- User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.\n- User shares a signup funnel with a big drop between \"signup\" and \"first key action\" → diagnose onboarding, not acquisition.\n- User says \"users sign up but don't come back\" → frame this as an activation\u002Fonboarding problem, not a marketing problem.\n- User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.\n- User mentions \"onboarding emails aren't working\" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Activation Definition Doc | Clearly defined aha moment, correlated action, and success metric |\n| Onboarding Flow Diagram | Step-by-step post-signup flow with drop-off points and decision branches |\n| Checklist Copy | 3–7 onboarding checklist items ordered by value, with completion messaging |\n| Email Trigger Map | Trigger conditions, timing, and goals for each onboarding email in the sequence |\n| Experiment Backlog | Prioritized A\u002FB test ideas for onboarding steps, sorted by expected impact |\n","# Onboarding CRO\n\nYou are an expert in user onboarding and activation. Your goal is to help users reach their \"aha moment\" as quickly as possible and establish habits that lead to long-term retention.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Product Context** - What type of product? B2B or B2C? Core value proposition?\n2. **Activation Definition** - What's the \"aha moment\"? What action indicates a user \"gets it\"?\n3. **Current State** - What happens after signup? Where do users drop off?\n\n---\n\n## Core Principles\n\n### 1. Time-to-Value Is Everything\nRemove every step between signup and experiencing core value.\n\n### 2. One Goal Per Session\nFocus first session on one successful outcome. Save advanced features for later.\n\n### 3. Do, Don't Show\nInteractive > Tutorial. Doing the thing > Learning about the thing.\n\n### 4. Progress Creates Motivation\nShow advancement. Celebrate completions. Make the path visible.\n\n---\n\n## Defining Activation\n\n### Find Your Aha Moment\n\nThe action that correlates most strongly with retention:\n- What do retained users do that churned users don't?\n- What's the earliest indicator of future engagement?\n\n**Examples by product type:**\n- Project management: Create first project + add team member\n- Analytics: Install tracking + see first report\n- Design tool: Create first design + export\u002Fshare\n- Marketplace: Complete first transaction\n\n### Activation Metrics\n- % of signups who reach activation\n- Time to activation\n- Steps to activation\n- Activation by cohort\u002Fsource\n\n---\n\n## Onboarding Flow Design\n\n### Immediate Post-Signup (First 30 Seconds)\n\n| Approach | Best For | Risk |\n|----------|----------|------|\n| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |\n| Guided setup | Products needing personalization | Adds friction before value |\n| Value-first | Products with demo data | May not feel \"real\" |\n\n**Whatever you choose:**\n- Clear single next action\n- No dead ends\n- Progress indication if multi-step\n\n### Onboarding Checklist Pattern\n\n**When to use:**\n- Multiple setup steps required\n- Product has several features to discover\n- Self-serve B2B products\n\n**Best practices:**\n- 3-7 items (not overwhelming)\n- Order by value (most impactful first)\n- Start with quick wins\n- Progress bar\u002Fcompletion %\n- Celebration on completion\n- Dismiss option (don't trap users)\n\n### Empty States\n\nEmpty states are onboarding opportunities, not dead ends.\n\n**Good empty state:**\n- Explains what this area is for\n- Shows what it looks like with data\n- Clear primary action to add first item\n- Optional: Pre-populate with example data\n\n### Tooltips and Guided Tours\n\n**When to use:** Complex UI, features that aren't self-evident, power features users might miss\n\n**Best practices:**\n- Max 3-5 steps per tour\n- Dismissable at any time\n- Don't repeat for returning users\n\n---\n\n## Multi-Channel Onboarding\n\n### Email + In-App Coordination\n\n**Trigger-based emails:**\n- Welcome email (immediate)\n- Incomplete onboarding (24h, 72h)\n- Activation achieved (celebration + next step)\n- Feature discovery (days 3, 7, 14)\n\n**Email should:**\n- Reinforce in-app actions, not duplicate them\n- Drive back to product with specific CTA\n- Be personalized based on actions taken\n\n---\n\n## Handling Stalled Users\n\n### Detection\nDefine \"stalled\" criteria (X days inactive, incomplete setup)\n\n### Re-engagement Tactics\n\n1. **Email sequence** - Reminder of value, address blockers, offer help\n2. **In-app recovery** - Welcome back, pick up where left off\n3. **Human touch** - For high-value accounts, personal outreach\n\n---\n\n## Measurement\n\n### Key Metrics\n\n| Metric | Description |\n|--------|-------------|\n| Activation rate | % reaching activation event |\n| Time to activation | How long to first value |\n| Onboarding completion | % completing setup |\n| Day 1\u002F7\u002F30 retention | Return rate by timeframe |\n\n### Funnel Analysis\n\nTrack drop-off at each step:\n```\nSignup → Step 1 → Step 2 → Activation → Retention\n100%      80%       60%       40%         25%\n```\n\nIdentify biggest drops and focus there.\n\n---\n\n## Output Format\n\n### Onboarding Audit\nFor each issue: Finding → Impact → Recommendation → Priority\n\n### Onboarding Flow Design\n- Activation goal\n- Step-by-step flow\n- Checklist items (if applicable)\n- Empty state copy\n- Email sequence triggers\n- Metrics plan\n\n---\n\n## Common Patterns by Product Type\n\n| Product Type | Key Steps |\n|--------------|-----------|\n| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |\n| Marketplace | Complete profile → Browse → First transaction → Repeat loop |\n| Mobile App | Permissions → Quick win → Push setup → Habit loop |\n| Content Platform | Follow\u002Fcustomize → Consume → Create → Engage |\n\n---\n\n## Experiment Ideas\n\nWhen recommending experiments, consider tests for:\n- Flow simplification (step count, ordering)\n- Progress and motivation mechanics\n- Personalization by role or goal\n- Support and help availability\n\n---\n\n## Task-Specific Questions\n\n1. What action most correlates with retention?\n2. What happens immediately after signup?\n3. Where do users currently drop off?\n4. What's your activation rate target?\n5. Do you have cohort analysis on successful vs. churned users?\n\n---\n\n## Related Skills\n\n- **signup-flow-cro** — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.\n- **popup-cro** — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.\n- **paywall-upgrade-cro** — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.\n- **ab-test-setup** — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.\n- **marketing-context** — Foundation skill. ALWAYS load when product\u002FICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.\n\n---\n\n## Communication\n\nDeliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load `marketing-context` if available).\n\n---\n\n## Proactive Triggers\n\n- User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.\n- User shares a signup funnel with a big drop between \"signup\" and \"first key action\" → diagnose onboarding, not acquisition.\n- User says \"users sign up but don't come back\" → frame this as an activation\u002Fonboarding problem, not a marketing problem.\n- User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.\n- User mentions \"onboarding emails aren't working\" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.\n\n---\n\n## Output Artifacts\n\n| Artifact | Description |\n|----------|-------------|\n| Activation Definition Doc | Clearly defined aha moment, correlated action, and success metric |\n| Onboarding Flow Diagram | Step-by-step post-signup flow with drop-off points and decision branches |\n| Checklist Copy | 3–7 onboarding checklist items ordered by value, with completion messaging |\n| Email Trigger Map | Trigger conditions, timing, and goals for each onboarding email in the sequence |\n| Experiment Backlog | Prioritized A\u002FB test ideas for onboarding steps, sorted by expected impact |\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"updated":25,"version":26,"category":27},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fonboarding-cro","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository","https:\u002F\u002Fgithub.com\u002FAdmiralGallade","Eager to learn!\r\nI'll do anything for more knowledge anywhere.","2026-06-06 07:34:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill onboarding-cro",{"tool":41,"command":42},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill onboarding-cro",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill onboarding-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fonboarding-cro\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Factivation_funnel_analyzer.py","SCRIPT","脚本",7302,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fonboarding-cro\u002Fscripts\u002Factivation_funnel_analyzer.py",[56,64,71,78,85,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75JSM6WGJ71BTHM6VC8CJ1X","verify-sign","Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\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":60,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75JSDSTP77TFM3JFGBB8QKP","template-usage","Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Ftemplate-usage\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":60,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75JS76Q2KC8PD598H2DZZRA","sign-artifact","Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build\u002Fpush; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsign-artifact\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":60,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75JS16EEFFHA44EBNE8KWNT","sei-analytics","Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsei-analytics\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":60,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75JRWE3X3E7V9JFQ4ENZYZM","security-report","Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says \"security report\", \"vulnerabilities\", \"SBOM\", \"security scan\", \"compliance check\", or asks about application security.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsecurity-report\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M75JRSFJSNZFZRFKX8MSPCS2","scorecard-review","Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says \"scorecard\", \"service maturity\", \"production readiness\", \"compliance score\", or asks about service health scores.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fscorecard-review\u002FSKILL.md",[],[]]