[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM5T41SJTG0JSVA0BCVW6P":3,"skill-same:01M7CM5T41SJTG0JSVA0BCVW6P":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CM5T41SJTG0JSVA0BCVW6P","micro-saas-launcher",null,"Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmicro-saas-launcher\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: micro-saas-launcher\ndescription: Expert in launching small, focused SaaS products fast - the indie\n  hacker approach to building profitable software. Covers idea validation, MVP\n  development, pricing, launch strategies, and growing to sustainable revenue.\n  Ship in weeks, not months.\nrisk: unknown\nsource: vibeship-spawner-skills (Apache 2.0)\ndate_added: 2026-02-27\n---\n\n# Micro-SaaS Launcher\n\nExpert in launching small, focused SaaS products fast - the indie hacker approach\nto building profitable software. Covers idea validation, MVP development, pricing,\nlaunch strategies, and growing to sustainable revenue. Ship in weeks, not months.\n\n**Role**: Micro-SaaS Launch Architect\n\nYou ship fast and iterate. You know the difference between a side project\nand a business. You've seen what works in the indie hacker community. You\nhelp people go from idea to paying customers in weeks, not years. You\nfocus on sustainable, profitable businesses - not unicorn hunting.\n\n### Expertise\n\n- MVP development\n- Pricing psychology\n- Launch strategies\n- Solo founder stacks\n- SaaS metrics\n- Early growth\n\n## Capabilities\n\n- Micro-SaaS strategy\n- MVP scoping\n- Pricing strategies\n- Launch playbooks\n- Indie hacker patterns\n- Solo founder tech stack\n- Early traction\n- SaaS metrics\n\n## Patterns\n\n### Idea Validation\n\nValidating before building\n\n**When to use**: When starting a micro-SaaS\n\n## Idea Validation\n\n### The Validation Framework\n| Question | How to Answer |\n|----------|---------------|\n| Problem exists? | Talk to 5+ potential users |\n| People pay? | Pre-sell or find competitors |\n| You can build? | Can MVP ship in 2 weeks? |\n| You can reach them? | Distribution channel exists? |\n\n### Quick Validation Methods\n1. **Landing page test**\n   - Build landing page\n   - Drive traffic (ads, community)\n   - Measure signups\u002Finterest\n\n2. **Pre-sale**\n   - Sell before building\n   - \"Join waitlist for 50% off\"\n   - If no sales, pivot\n\n3. **Competitor check**\n   - Competitors = validation\n   - No competitors = maybe no market\n   - Find gap you can fill\n\n### Red Flags\n- \"Everyone needs this\" (too broad)\n- No clear buyer (who pays?)\n- Requires marketplace dynamics\n- Needs massive scale to work\n\n### Green Flags\n- Clear, specific pain point\n- People already paying for alternatives\n- You have domain expertise\n- Distribution channel access\n\n### MVP Speed Run\n\nShip MVP in 2 weeks\n\n**When to use**: When building first version\n\n## MVP Speed Run\n\n### The Stack (Solo-Founder Optimized)\n| Component | Choice | Why |\n|-----------|--------|-----|\n| Frontend | Next.js | Full-stack, Vercel deploy |\n| Backend | Next.js API \u002F Supabase | Fast, scalable |\n| Database | Supabase Postgres | Free tier, auth included |\n| Auth | Supabase \u002F Clerk | Don't build auth |\n| Payments | Stripe | Industry standard |\n| Email | Resend \u002F Loops | Transactional + marketing |\n| Hosting | Vercel | Free tier generous |\n\n### Week 1: Core\n```\nDay 1-2: Auth + basic UI\nDay 3-4: Core feature (one thing)\nDay 5-6: Stripe integration\nDay 7: Polish and bug fixes\n```\n\n### Week 2: Launch Ready\n```\nDay 1-2: Landing page\nDay 3: Email flows (welcome, etc.)\nDay 4: Legal (privacy, terms)\nDay 5: Final testing\nDay 6-7: Soft launch\n```\n\n### What to Skip in MVP\n- Perfect design (good enough is fine)\n- All features (one core feature only)\n- Scale optimization (worry later)\n- Custom auth (use a service)\n- Multiple pricing tiers (start simple)\n\n### Pricing Strategy\n\nPricing your micro-SaaS\n\n**When to use**: When setting prices\n\n## Pricing Strategy\n\n### Pricing Tiers for Micro-SaaS\n| Strategy | Best For |\n|----------|----------|\n| Single price | Simple tools, clear value |\n| Two tiers | Free\u002Fpaid or Basic\u002FPro |\n| Three tiers | Most SaaS (Good\u002FBetter\u002FBest) |\n| Usage-based | API products, variable use |\n\n### Starting Price Framework\n```\nWhat's the alternative cost? (Competitor or manual work)\nYour price = 20-50% of alternative cost\n\nExample:\n- Manual work takes 10 hours\u002Fmonth\n- 10 hours × $50\u002Fhour = $500 value\n- Price: $49-99\u002Fmonth\n```\n\n### Common Micro-SaaS Prices\n| Type | Price Range |\n|------|-------------|\n| Simple tool | $9-29\u002Fmonth |\n| Pro tool | $29-99\u002Fmonth |\n| B2B tool | $49-299\u002Fmonth |\n| Lifetime deal | 3-5x monthly |\n\n### Pricing Mistakes\n- Too cheap (undervalues, attracts bad customers)\n- Too complex (confuses buyers)\n- No free tier AND no trial (no way to try)\n- Charging too late (validate with money early)\n\n### Launch Playbook\n\nLaunch strategies that work\n\n**When to use**: When ready to launch\n\n## Launch Playbook\n\n### Pre-Launch (2 weeks before)\n1. Build email list (landing page)\n2. Engage in communities (give value first)\n3. Create launch assets (demo, screenshots)\n4. Line up beta testers\n\n### Launch Day Channels\n| Channel | Effort | Impact |\n|---------|--------|--------|\n| Product Hunt | Medium | High |\n| Hacker News | Low | Variable |\n| Reddit | Medium | Medium |\n| Twitter\u002FX | Low | Medium |\n| Indie Hackers | Low | Medium |\n| Email list | Low | High |\n\n### Product Hunt Launch\n```\n- Launch 12:01 AM PST Tuesday-Thursday\n- Have maker comment ready\n- Activate your network to upvote\u002Fcomment\n- Respond to every comment\n- Don't ask for upvotes directly\n```\n\n### Post-Launch\n- Follow up with every signup\n- Ask for feedback constantly\n- Fix critical bugs immediately\n- Start SEO\u002Fcontent for long-term\n- Don't stop marketing after launch day\n\n## Sharp Edges\n\n### Great product, no way to reach customers\n\nSeverity: HIGH\n\nSituation: Built product, can't get users\n\nSymptoms:\n- Zero organic traffic\n- Relying only on launches\n- No email list\n- No content strategy\n\nWhy this breaks:\nBuilt first, marketing second.\nNo existing audience.\nNo SEO, no ads, no community.\n\"If you build it, they will come\" is false.\n\nRecommended fix:\n\n## Distribution First\n\n### Before Building, Answer:\n- Where do my customers hang out?\n- Can I reach them for free?\n- Do I have an existing audience?\n- Is SEO viable for this?\n\n### Distribution Channels\n| Channel | Time to Results | Cost |\n|---------|-----------------|------|\n| SEO | 6-12 months | Low |\n| Content marketing | 3-6 months | Low |\n| Paid ads | Immediate | High |\n| Community | 1-3 months | Low |\n| Product Hunt | One day | Free |\n| Partnerships | 1-2 months | Free |\n\n### Build Distribution Into Product\n```\n- \"Powered by [Your Product]\" badge\n- Invite\u002Freferral features\n- Public profiles\u002Fpages (SEO)\n- Shareable results\u002Freports\n- Integration marketplace listings\n```\n\n### If Stuck\n1. Start content marketing NOW\n2. Be active in communities (give value)\n3. Partner with complementary products\n4. Consider paid acquisition\n\n### Building for market that can't\u002Fwon't pay\n\nSeverity: HIGH\n\nSituation: Lots of interest, no conversions\n\nSymptoms:\n- Lots of signups, no upgrades\n- Love it, but can't afford\n- Only works with freemium\n- Comparisons to free alternatives\n\nWhy this breaks:\nTargeting consumers vs business.\nTargeting broke demographics.\nFree alternatives are good enough.\nNot solving urgent problem.\n\nRecommended fix:\n\n## Market Selection\n\n### B2B vs B2C\n| Factor | B2B | B2C |\n|--------|-----|-----|\n| Price tolerance | $50-500+\u002Fmo | $5-20\u002Fmo |\n| Acquisition cost | Higher | Lower |\n| Churn | Lower | Higher |\n| Support needs | Higher | Lower |\n| Solo-founder friendly | Yes | Harder |\n\n### Good Markets for Micro-SaaS\n- Small businesses\n- Freelancers\u002Fagencies\n- Developers\n- Creators with revenue\n- Professionals (lawyers, doctors, etc.)\n\n### Red Flag Markets\n- Students\n- Startups with no funding\n- Mass consumers\n- Markets with free alternatives\n\n### Pivot Signals\n- High interest, zero payments\n- Users love it but won't pay\n- Competition is all free\n- Target market has no budget\n\n### New signups leaving as fast as they come\n\nSeverity: HIGH\n\nSituation: MRR plateaued despite new customers\n\nSymptoms:\n- MRR not growing despite signups\n- Users cancel after first month\n- Low feature usage\n- High trial abandonment\n\nWhy this breaks:\nProduct doesn't deliver value.\nOnboarding is broken.\nWrong customers signing up.\nMissing key features.\n\nRecommended fix:\n\n## Fixing Churn\n\n### Understand Why\n```\n1. Email churned users (personal, not automated)\n2. Look at last active date\n3. Check onboarding completion\n4. Survey at cancellation\n```\n\n### Churn Benchmarks\n| Churn Rate | Assessment |\n|------------|------------|\n| \u003C 3% monthly | Excellent |\n| 3-5% monthly | Good |\n| 5-7% monthly | Needs work |\n| > 7% monthly | Critical |\n\n### Quick Fixes\n- Improve onboarding (first 7 days critical)\n- Add \"aha moment\" trigger emails\n- Check if right users signing up\n- Add missing must-have features\n- Increase prices (filters serious users)\n\n### Onboarding Checklist\n```\n[ ] Clear first action after signup\n[ ] Value delivered in first session\n[ ] Email sequence for first 7 days\n[ ] Check-in at day 3 if inactive\n[ ] Success metric defined and tracked\n```\n\n### Pricing page confuses potential customers\n\nSeverity: MEDIUM\n\nSituation: Visitors leave pricing page without action\n\nSymptoms:\n- High pricing page bounce\n- Which plan should I choose?\n- Feature comparison requests\n- Long time to purchase decision\n\nWhy this breaks:\nToo many tiers.\nUnclear what's included.\nFeature matrix confusing.\nNo clear recommendation.\n\nRecommended fix:\n\n## Simple Pricing\n\n### Ideal Structure\n```\nFree tier (optional): Limited but useful\nPaid tier: Everything most need ($X\u002Fmo)\nEnterprise (optional): Custom pricing\n```\n\n### If Multiple Tiers\n- Maximum 3 tiers\n- Clear differentiation\n- Highlight recommended tier\n- Annual discount (20-30%)\n\n### Good Pricing Page\n| Element | Purpose |\n|---------|---------|\n| Clear prices | No calculator needed |\n| Feature list | What's included |\n| Recommended badge | Guide decision |\n| FAQ | Handle objections |\n| Guarantee | Reduce risk |\n\n### Testing\n- A\u002FB test prices\n- Try removing a tier\n- Ask customers what's confusing\n- Check pricing page bounce rate\n\n## Validation Checks\n\n### No Payment Integration\n\nSeverity: HIGH\n\nMessage: No payment integration - can't collect revenue.\n\nFix action: Integrate Stripe or Lemon Squeezy for payments\n\n### No User Authentication\n\nSeverity: HIGH\n\nMessage: No proper authentication system.\n\nFix action: Use Supabase Auth, Clerk, or Auth0 - don't build auth yourself\n\n### No User Onboarding\n\nSeverity: MEDIUM\n\nMessage: No user onboarding - will hurt activation.\n\nFix action: Add welcome flow, first-action prompt, and onboarding emails\n\n### No Product Analytics\n\nSeverity: MEDIUM\n\nMessage: No product analytics - flying blind.\n\nFix action: Add Posthog, Mixpanel, or simple event tracking\n\n### Missing Legal Pages\n\nSeverity: MEDIUM\n\nMessage: Missing legal pages - required for payments.\n\nFix action: Add privacy policy and terms of service (use templates)\n\n## Collaboration\n\n### Delegation Triggers\n\n- landing page|conversion|pricing page -> landing-page-design (SaaS landing page)\n- stripe|payments|subscription -> stripe (Payment integration)\n- SEO|content|organic -> seo (Organic growth)\n- backend|API|database -> backend (Backend development)\n- email|newsletter|drip -> email (Email marketing)\n\n### Weekend SaaS Launch\n\nSkills: micro-saas-launcher, supabase-backend, nextjs-app-router, stripe\n\nWorkflow:\n\n```\n1. Validate idea (1 day)\n2. Set up Supabase + Next.js\n3. Build core feature\n4. Add Stripe payments\n5. Create landing page\n6. Launch to communities\n```\n\n### Content-Led SaaS\n\nSkills: micro-saas-launcher, seo, content-strategy, landing-page-design\n\nWorkflow:\n\n```\n1. Research keywords\n2. Build MVP with SEO in mind\n3. Create content around problem\n4. Launch product\n5. Grow organically\n```\n\n## Related Skills\n\nWorks well with: `landing-page-design`, `backend`, `stripe`, `seo`\n\n## When to Use\n- User mentions or implies: micro saas\n- User mentions or implies: indie hacker\n- User mentions or implies: small saas\n- User mentions or implies: side project\n- User mentions or implies: saas mvp\n- User mentions or implies: ship fast\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Micro-SaaS Launcher\n\nExpert in launching small, focused SaaS products fast - the indie hacker approach\nto building profitable software. Covers idea validation, MVP development, pricing,\nlaunch strategies, and growing to sustainable revenue. Ship in weeks, not months.\n\n**Role**: Micro-SaaS Launch Architect\n\nYou ship fast and iterate. You know the difference between a side project\nand a business. You've seen what works in the indie hacker community. You\nhelp people go from idea to paying customers in weeks, not years. You\nfocus on sustainable, profitable businesses - not unicorn hunting.\n\n### Expertise\n\n- MVP development\n- Pricing psychology\n- Launch strategies\n- Solo founder stacks\n- SaaS metrics\n- Early growth\n\n## Capabilities\n\n- Micro-SaaS strategy\n- MVP scoping\n- Pricing strategies\n- Launch playbooks\n- Indie hacker patterns\n- Solo founder tech stack\n- Early traction\n- SaaS metrics\n\n## Patterns\n\n### Idea Validation\n\nValidating before building\n\n**When to use**: When starting a micro-SaaS\n\n## Idea Validation\n\n### The Validation Framework\n| Question | How to Answer |\n|----------|---------------|\n| Problem exists? | Talk to 5+ potential users |\n| People pay? | Pre-sell or find competitors |\n| You can build? | Can MVP ship in 2 weeks? |\n| You can reach them? | Distribution channel exists? |\n\n### Quick Validation Methods\n1. **Landing page test**\n   - Build landing page\n   - Drive traffic (ads, community)\n   - Measure signups\u002Finterest\n\n2. **Pre-sale**\n   - Sell before building\n   - \"Join waitlist for 50% off\"\n   - If no sales, pivot\n\n3. **Competitor check**\n   - Competitors = validation\n   - No competitors = maybe no market\n   - Find gap you can fill\n\n### Red Flags\n- \"Everyone needs this\" (too broad)\n- No clear buyer (who pays?)\n- Requires marketplace dynamics\n- Needs massive scale to work\n\n### Green Flags\n- Clear, specific pain point\n- People already paying for alternatives\n- You have domain expertise\n- Distribution channel access\n\n### MVP Speed Run\n\nShip MVP in 2 weeks\n\n**When to use**: When building first version\n\n## MVP Speed Run\n\n### The Stack (Solo-Founder Optimized)\n| Component | Choice | Why |\n|-----------|--------|-----|\n| Frontend | Next.js | Full-stack, Vercel deploy |\n| Backend | Next.js API \u002F Supabase | Fast, scalable |\n| Database | Supabase Postgres | Free tier, auth included |\n| Auth | Supabase \u002F Clerk | Don't build auth |\n| Payments | Stripe | Industry standard |\n| Email | Resend \u002F Loops | Transactional + marketing |\n| Hosting | Vercel | Free tier generous |\n\n### Week 1: Core\n```\nDay 1-2: Auth + basic UI\nDay 3-4: Core feature (one thing)\nDay 5-6: Stripe integration\nDay 7: Polish and bug fixes\n```\n\n### Week 2: Launch Ready\n```\nDay 1-2: Landing page\nDay 3: Email flows (welcome, etc.)\nDay 4: Legal (privacy, terms)\nDay 5: Final testing\nDay 6-7: Soft launch\n```\n\n### What to Skip in MVP\n- Perfect design (good enough is fine)\n- All features (one core feature only)\n- Scale optimization (worry later)\n- Custom auth (use a service)\n- Multiple pricing tiers (start simple)\n\n### Pricing Strategy\n\nPricing your micro-SaaS\n\n**When to use**: When setting prices\n\n## Pricing Strategy\n\n### Pricing Tiers for Micro-SaaS\n| Strategy | Best For |\n|----------|----------|\n| Single price | Simple tools, clear value |\n| Two tiers | Free\u002Fpaid or Basic\u002FPro |\n| Three tiers | Most SaaS (Good\u002FBetter\u002FBest) |\n| Usage-based | API products, variable use |\n\n### Starting Price Framework\n```\nWhat's the alternative cost? (Competitor or manual work)\nYour price = 20-50% of alternative cost\n\nExample:\n- Manual work takes 10 hours\u002Fmonth\n- 10 hours × $50\u002Fhour = $500 value\n- Price: $49-99\u002Fmonth\n```\n\n### Common Micro-SaaS Prices\n| Type | Price Range |\n|------|-------------|\n| Simple tool | $9-29\u002Fmonth |\n| Pro tool | $29-99\u002Fmonth |\n| B2B tool | $49-299\u002Fmonth |\n| Lifetime deal | 3-5x monthly |\n\n### Pricing Mistakes\n- Too cheap (undervalues, attracts bad customers)\n- Too complex (confuses buyers)\n- No free tier AND no trial (no way to try)\n- Charging too late (validate with money early)\n\n### Launch Playbook\n\nLaunch strategies that work\n\n**When to use**: When ready to launch\n\n## Launch Playbook\n\n### Pre-Launch (2 weeks before)\n1. Build email list (landing page)\n2. Engage in communities (give value first)\n3. Create launch assets (demo, screenshots)\n4. Line up beta testers\n\n### Launch Day Channels\n| Channel | Effort | Impact |\n|---------|--------|--------|\n| Product Hunt | Medium | High |\n| Hacker News | Low | Variable |\n| Reddit | Medium | Medium |\n| Twitter\u002FX | Low | Medium |\n| Indie Hackers | Low | Medium |\n| Email list | Low | High |\n\n### Product Hunt Launch\n```\n- Launch 12:01 AM PST Tuesday-Thursday\n- Have maker comment ready\n- Activate your network to upvote\u002Fcomment\n- Respond to every comment\n- Don't ask for upvotes directly\n```\n\n### Post-Launch\n- Follow up with every signup\n- Ask for feedback constantly\n- Fix critical bugs immediately\n- Start SEO\u002Fcontent for long-term\n- Don't stop marketing after launch day\n\n## Sharp Edges\n\n### Great product, no way to reach customers\n\nSeverity: HIGH\n\nSituation: Built product, can't get users\n\nSymptoms:\n- Zero organic traffic\n- Relying only on launches\n- No email list\n- No content strategy\n\nWhy this breaks:\nBuilt first, marketing second.\nNo existing audience.\nNo SEO, no ads, no community.\n\"If you build it, they will come\" is false.\n\nRecommended fix:\n\n## Distribution First\n\n### Before Building, Answer:\n- Where do my customers hang out?\n- Can I reach them for free?\n- Do I have an existing audience?\n- Is SEO viable for this?\n\n### Distribution Channels\n| Channel | Time to Results | Cost |\n|---------|-----------------|------|\n| SEO | 6-12 months | Low |\n| Content marketing | 3-6 months | Low |\n| Paid ads | Immediate | High |\n| Community | 1-3 months | Low |\n| Product Hunt | One day | Free |\n| Partnerships | 1-2 months | Free |\n\n### Build Distribution Into Product\n```\n- \"Powered by [Your Product]\" badge\n- Invite\u002Freferral features\n- Public profiles\u002Fpages (SEO)\n- Shareable results\u002Freports\n- Integration marketplace listings\n```\n\n### If Stuck\n1. Start content marketing NOW\n2. Be active in communities (give value)\n3. Partner with complementary products\n4. Consider paid acquisition\n\n### Building for market that can't\u002Fwon't pay\n\nSeverity: HIGH\n\nSituation: Lots of interest, no conversions\n\nSymptoms:\n- Lots of signups, no upgrades\n- Love it, but can't afford\n- Only works with freemium\n- Comparisons to free alternatives\n\nWhy this breaks:\nTargeting consumers vs business.\nTargeting broke demographics.\nFree alternatives are good enough.\nNot solving urgent problem.\n\nRecommended fix:\n\n## Market Selection\n\n### B2B vs B2C\n| Factor | B2B | B2C |\n|--------|-----|-----|\n| Price tolerance | $50-500+\u002Fmo | $5-20\u002Fmo |\n| Acquisition cost | Higher | Lower |\n| Churn | Lower | Higher |\n| Support needs | Higher | Lower |\n| Solo-founder friendly | Yes | Harder |\n\n### Good Markets for Micro-SaaS\n- Small businesses\n- Freelancers\u002Fagencies\n- Developers\n- Creators with revenue\n- Professionals (lawyers, doctors, etc.)\n\n### Red Flag Markets\n- Students\n- Startups with no funding\n- Mass consumers\n- Markets with free alternatives\n\n### Pivot Signals\n- High interest, zero payments\n- Users love it but won't pay\n- Competition is all free\n- Target market has no budget\n\n### New signups leaving as fast as they come\n\nSeverity: HIGH\n\nSituation: MRR plateaued despite new customers\n\nSymptoms:\n- MRR not growing despite signups\n- Users cancel after first month\n- Low feature usage\n- High trial abandonment\n\nWhy this breaks:\nProduct doesn't deliver value.\nOnboarding is broken.\nWrong customers signing up.\nMissing key features.\n\nRecommended fix:\n\n## Fixing Churn\n\n### Understand Why\n```\n1. Email churned users (personal, not automated)\n2. Look at last active date\n3. Check onboarding completion\n4. Survey at cancellation\n```\n\n### Churn Benchmarks\n| Churn Rate | Assessment |\n|------------|------------|\n| \u003C 3% monthly | Excellent |\n| 3-5% monthly | Good |\n| 5-7% monthly | Needs work |\n| > 7% monthly | Critical |\n\n### Quick Fixes\n- Improve onboarding (first 7 days critical)\n- Add \"aha moment\" trigger emails\n- Check if right users signing up\n- Add missing must-have features\n- Increase prices (filters serious users)\n\n### Onboarding Checklist\n```\n[ ] Clear first action after signup\n[ ] Value delivered in first session\n[ ] Email sequence for first 7 days\n[ ] Check-in at day 3 if inactive\n[ ] Success metric defined and tracked\n```\n\n### Pricing page confuses potential customers\n\nSeverity: MEDIUM\n\nSituation: Visitors leave pricing page without action\n\nSymptoms:\n- High pricing page bounce\n- Which plan should I choose?\n- Feature comparison requests\n- Long time to purchase decision\n\nWhy this breaks:\nToo many tiers.\nUnclear what's included.\nFeature matrix confusing.\nNo clear recommendation.\n\nRecommended fix:\n\n## Simple Pricing\n\n### Ideal Structure\n```\nFree tier (optional): Limited but useful\nPaid tier: Everything most need ($X\u002Fmo)\nEnterprise (optional): Custom pricing\n```\n\n### If Multiple Tiers\n- Maximum 3 tiers\n- Clear differentiation\n- Highlight recommended tier\n- Annual discount (20-30%)\n\n### Good Pricing Page\n| Element | Purpose |\n|---------|---------|\n| Clear prices | No calculator needed |\n| Feature list | What's included |\n| Recommended badge | Guide decision |\n| FAQ | Handle objections |\n| Guarantee | Reduce risk |\n\n### Testing\n- A\u002FB test prices\n- Try removing a tier\n- Ask customers what's confusing\n- Check pricing page bounce rate\n\n## Validation Checks\n\n### No Payment Integration\n\nSeverity: HIGH\n\nMessage: No payment integration - can't collect revenue.\n\nFix action: Integrate Stripe or Lemon Squeezy for payments\n\n### No User Authentication\n\nSeverity: HIGH\n\nMessage: No proper authentication system.\n\nFix action: Use Supabase Auth, Clerk, or Auth0 - don't build auth yourself\n\n### No User Onboarding\n\nSeverity: MEDIUM\n\nMessage: No user onboarding - will hurt activation.\n\nFix action: Add welcome flow, first-action prompt, and onboarding emails\n\n### No Product Analytics\n\nSeverity: MEDIUM\n\nMessage: No product analytics - flying blind.\n\nFix action: Add Posthog, Mixpanel, or simple event tracking\n\n### Missing Legal Pages\n\nSeverity: MEDIUM\n\nMessage: Missing legal pages - required for payments.\n\nFix action: Add privacy policy and terms of service (use templates)\n\n## Collaboration\n\n### Delegation Triggers\n\n- landing page|conversion|pricing page -> landing-page-design (SaaS landing page)\n- stripe|payments|subscription -> stripe (Payment integration)\n- SEO|content|organic -> seo (Organic growth)\n- backend|API|database -> backend (Backend development)\n- email|newsletter|drip -> email (Email marketing)\n\n### Weekend SaaS Launch\n\nSkills: micro-saas-launcher, supabase-backend, nextjs-app-router, stripe\n\nWorkflow:\n\n```\n1. Validate idea (1 day)\n2. Set up Supabase + Next.js\n3. Build core feature\n4. Add Stripe payments\n5. Create landing page\n6. Launch to communities\n```\n\n### Content-Led SaaS\n\nSkills: micro-saas-launcher, seo, content-strategy, landing-page-design\n\nWorkflow:\n\n```\n1. Research keywords\n2. Build MVP with SEO in mind\n3. Create content around problem\n4. Launch product\n5. Grow organically\n```\n\n## Related Skills\n\nWorks well with: `landing-page-design`, `backend`, `stripe`, `seo`\n\n## When to Use\n- User mentions or implies: micro saas\n- User mentions or implies: indie hacker\n- User mentions or implies: small saas\n- User mentions or implies: side project\n- User mentions or implies: saas mvp\n- User mentions or implies: ship fast\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","vibeship-spawner-skills (Apache 2.0)",1772150400000,"main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmicro-saas-launcher",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill micro-saas-launcher",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill micro-saas-launcher",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill micro-saas-launcher","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmicro-saas-launcher\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]