opencode-skills-collection 4.0.52 → 4.0.54

package/bundled-skills/micro-saas-launcher/references/detailed-guide.md

@@ -0,0 +1,491 @@
+# Micro-SaaS Launcher - Detailed Guide
+
+> This file contains the detailed procedure and reference material extracted from `SKILL.md` for focused loading. The root skill defines activation, examples, safety constraints, and limitations.
+
+## Capabilities
+
+- Micro-SaaS strategy
+- MVP scoping
+- Pricing strategies
+- Launch playbooks
+- Indie hacker patterns
+- Solo founder tech stack
+- Early traction
+- SaaS metrics
+
+
+## Patterns
+
+### Idea Validation
+
+Validating before building
+
+**When to use**: When starting a micro-SaaS
+
+
+## Idea Validation
+
+### The Validation Framework
+| Question | How to Answer |
+|----------|---------------|
+| Problem exists? | Talk to 5+ potential users |
+| People pay? | Pre-sell or find competitors |
+| You can build? | Can MVP ship in 2 weeks? |
+| You can reach them? | Distribution channel exists? |
+
+### Quick Validation Methods
+1. **Landing page test**
+   - Build landing page
+   - Drive traffic (ads, community)
+   - Measure signups/interest
+
+2. **Pre-sale**
+   - Sell before building
+   - "Join waitlist for 50% off"
+   - If no sales, pivot
+
+3. **Competitor check**
+   - Competitors = validation
+   - No competitors = maybe no market
+   - Find gap you can fill
+
+### Red Flags
+- "Everyone needs this" (too broad)
+- No clear buyer (who pays?)
+- Requires marketplace dynamics
+- Needs massive scale to work
+
+### Green Flags
+- Clear, specific pain point
+- People already paying for alternatives
+- You have domain expertise
+- Distribution channel access
+
+### MVP Speed Run
+
+Ship MVP in 2 weeks
+
+**When to use**: When building first version
+
+
+## MVP Speed Run
+
+### The Stack (Solo-Founder Optimized)
+| Component | Choice | Why |
+|-----------|--------|-----|
+| Frontend | Next.js | Full-stack, Vercel deploy |
+| Backend | Next.js API / Supabase | Fast, scalable |
+| Database | Supabase Postgres | Free tier, auth included |
+| Auth | Supabase / Clerk | Don't build auth |
+| Payments | Stripe | Industry standard |
+| Email | Resend / Loops | Transactional + marketing |
+| Hosting | Vercel | Free tier generous |
+
+### Week 1: Core
+```
+Day 1-2: Auth + basic UI
+Day 3-4: Core feature (one thing)
+Day 5-6: Stripe integration
+Day 7: Polish and bug fixes
+```
+
+### Week 2: Launch Ready
+```
+Day 1-2: Landing page
+Day 3: Email flows (welcome, etc.)
+Day 4: Legal (privacy, terms)
+Day 5: Final testing
+Day 6-7: Soft launch
+```
+
+### What to Skip in MVP
+- Perfect design (good enough is fine)
+- All features (one core feature only)
+- Scale optimization (worry later)
+- Custom auth (use a service)
+- Multiple pricing tiers (start simple)
+
+### Pricing Strategy
+
+Pricing your micro-SaaS
+
+**When to use**: When setting prices
+
+
+## Pricing Strategy
+
+### Pricing Tiers for Micro-SaaS
+| Strategy | Best For |
+|----------|----------|
+| Single price | Simple tools, clear value |
+| Two tiers | Free/paid or Basic/Pro |
+| Three tiers | Most SaaS (Good/Better/Best) |
+| Usage-based | API products, variable use |
+
+### Starting Price Framework
+```
+What's the alternative cost? (Competitor or manual work)
+Your price = 20-50% of alternative cost
+
+Example:
+- Manual work takes 10 hours/month
+- 10 hours × $50/hour = $500 value
+- Price: $49-99/month
+```
+
+### Common Micro-SaaS Prices
+| Type | Price Range |
+|------|-------------|
+| Simple tool | $9-29/month |
+| Pro tool | $29-99/month |
+| B2B tool | $49-299/month |
+| Lifetime deal | 3-5x monthly |
+
+### Pricing Mistakes
+- Too cheap (undervalues, attracts bad customers)
+- Too complex (confuses buyers)
+- No free tier AND no trial (no way to try)
+- Charging too late (validate with money early)
+
+### Launch Playbook
+
+Launch strategies that work
+
+**When to use**: When ready to launch
+
+
+## Launch Playbook
+
+### Pre-Launch (2 weeks before)
+1. Build email list (landing page)
+2. Engage in communities (give value first)
+3. Create launch assets (demo, screenshots)
+4. Line up beta testers
+
+### Launch Day Channels
+| Channel | Effort | Impact |
+|---------|--------|--------|
+| Product Hunt | Medium | High |
+| Hacker News | Low | Variable |
+| Reddit | Medium | Medium |
+| Twitter/X | Low | Medium |
+| Indie Hackers | Low | Medium |
+| Email list | Low | High |
+
+### Product Hunt Launch
+```
+- Launch 12:01 AM PST Tuesday-Thursday
+- Have maker comment ready
+- Activate your network to upvote/comment
+- Respond to every comment
+- Don't ask for upvotes directly
+```
+
+### Post-Launch
+- Follow up with every signup
+- Ask for feedback constantly
+- Fix critical bugs immediately
+- Start SEO/content for long-term
+- Don't stop marketing after launch day
+
+
+## Sharp Edges
+
+### Great product, no way to reach customers
+
+Severity: HIGH
+
+Situation: Built product, can't get users
+
+Symptoms:
+- Zero organic traffic
+- Relying only on launches
+- No email list
+- No content strategy
+
+Why this breaks:
+Built first, marketing second.
+No existing audience.
+No SEO, no ads, no community.
+"If you build it, they will come" is false.
+
+Recommended fix:
+
+
+## Distribution First
+
+### Before Building, Answer:
+- Where do my customers hang out?
+- Can I reach them for free?
+- Do I have an existing audience?
+- Is SEO viable for this?
+
+### Distribution Channels
+| Channel | Time to Results | Cost |
+|---------|-----------------|------|
+| SEO | 6-12 months | Low |
+| Content marketing | 3-6 months | Low |
+| Paid ads | Immediate | High |
+| Community | 1-3 months | Low |
+| Product Hunt | One day | Free |
+| Partnerships | 1-2 months | Free |
+
+### Build Distribution Into Product
+```
+- "Powered by [Your Product]" badge
+- Invite/referral features
+- Public profiles/pages (SEO)
+- Shareable results/reports
+- Integration marketplace listings
+```
+
+### If Stuck
+1. Start content marketing NOW
+2. Be active in communities (give value)
+3. Partner with complementary products
+4. Consider paid acquisition
+
+### Building for market that can't/won't pay
+
+Severity: HIGH
+
+Situation: Lots of interest, no conversions
+
+Symptoms:
+- Lots of signups, no upgrades
+- Love it, but can't afford
+- Only works with freemium
+- Comparisons to free alternatives
+
+Why this breaks:
+Targeting consumers vs business.
+Targeting broke demographics.
+Free alternatives are good enough.
+Not solving urgent problem.
+
+Recommended fix:
+
+
+## Market Selection
+
+### B2B vs B2C
+| Factor | B2B | B2C |
+|--------|-----|-----|
+| Price tolerance | $50-500+/mo | $5-20/mo |
+| Acquisition cost | Higher | Lower |
+| Churn | Lower | Higher |
+| Support needs | Higher | Lower |
+| Solo-founder friendly | Yes | Harder |
+
+### Good Markets for Micro-SaaS
+- Small businesses
+- Freelancers/agencies
+- Developers
+- Creators with revenue
+- Professionals (lawyers, doctors, etc.)
+
+### Red Flag Markets
+- Students
+- Startups with no funding
+- Mass consumers
+- Markets with free alternatives
+
+### Pivot Signals
+- High interest, zero payments
+- Users love it but won't pay
+- Competition is all free
+- Target market has no budget
+
+### New signups leaving as fast as they come
+
+Severity: HIGH
+
+Situation: MRR plateaued despite new customers
+
+Symptoms:
+- MRR not growing despite signups
+- Users cancel after first month
+- Low feature usage
+- High trial abandonment
+
+Why this breaks:
+Product doesn't deliver value.
+Onboarding is broken.
+Wrong customers signing up.
+Missing key features.
+
+Recommended fix:
+
+
+## Fixing Churn
+
+### Understand Why
+```
+1. Email churned users (personal, not automated)
+2. Look at last active date
+3. Check onboarding completion
+4. Survey at cancellation
+```
+
+### Churn Benchmarks
+| Churn Rate | Assessment |
+|------------|------------|
+| < 3% monthly | Excellent |
+| 3-5% monthly | Good |
+| 5-7% monthly | Needs work |
+| > 7% monthly | Critical |
+
+### Quick Fixes
+- Improve onboarding (first 7 days critical)
+- Add "aha moment" trigger emails
+- Check if right users signing up
+- Add missing must-have features
+- Increase prices (filters serious users)
+
+### Onboarding Checklist
+```
+[ ] Clear first action after signup
+[ ] Value delivered in first session
+[ ] Email sequence for first 7 days
+[ ] Check-in at day 3 if inactive
+[ ] Success metric defined and tracked
+```
+
+### Pricing page confuses potential customers
+
+Severity: MEDIUM
+
+Situation: Visitors leave pricing page without action
+
+Symptoms:
+- High pricing page bounce
+- Which plan should I choose?
+- Feature comparison requests
+- Long time to purchase decision
+
+Why this breaks:
+Too many tiers.
+Unclear what's included.
+Feature matrix confusing.
+No clear recommendation.
+
+Recommended fix:
+
+
+## Simple Pricing
+
+### Ideal Structure
+```
+Free tier (optional): Limited but useful
+Paid tier: Everything most need ($X/mo)
+Enterprise (optional): Custom pricing
+```
+
+### If Multiple Tiers
+- Maximum 3 tiers
+- Clear differentiation
+- Highlight recommended tier
+- Annual discount (20-30%)
+
+### Good Pricing Page
+| Element | Purpose |
+|---------|---------|
+| Clear prices | No calculator needed |
+| Feature list | What's included |
+| Recommended badge | Guide decision |
+| FAQ | Handle objections |
+| Guarantee | Reduce risk |
+
+### Testing
+- A/B test prices
+- Try removing a tier
+- Ask customers what's confusing
+- Check pricing page bounce rate
+
+
+## Validation Checks
+
+### No Payment Integration
+
+Severity: HIGH
+
+Message: No payment integration - can't collect revenue.
+
+Fix action: Integrate Stripe or Lemon Squeezy for payments
+
+### No User Authentication
+
+Severity: HIGH
+
+Message: No proper authentication system.
+
+Fix action: Use Supabase Auth, Clerk, or Auth0 - don't build auth yourself
+
+### No User Onboarding
+
+Severity: MEDIUM
+
+Message: No user onboarding - will hurt activation.
+
+Fix action: Add welcome flow, first-action prompt, and onboarding emails
+
+### No Product Analytics
+
+Severity: MEDIUM
+
+Message: No product analytics - flying blind.
+
+Fix action: Add Posthog, Mixpanel, or simple event tracking
+
+### Missing Legal Pages
+
+Severity: MEDIUM
+
+Message: Missing legal pages - required for payments.
+
+Fix action: Add privacy policy and terms of service (use templates)
+
+
+## Collaboration
+
+### Delegation Triggers
+
+- landing page|conversion|pricing page -> landing-page-design (SaaS landing page)
+- stripe|payments|subscription -> stripe (Payment integration)
+- SEO|content|organic -> seo (Organic growth)
+- backend|API|database -> backend (Backend development)
+- email|newsletter|drip -> email (Email marketing)
+
+### Weekend SaaS Launch
+
+Skills: micro-saas-launcher, supabase-backend, nextjs-app-router, stripe
+
+Workflow:
+
+```
+1. Validate idea (1 day)
+2. Set up Supabase + Next.js
+3. Build core feature
+4. Add Stripe payments
+5. Create landing page
+6. Launch to communities
+```
+
+### Content-Led SaaS
+
+Skills: micro-saas-launcher, seo, content-strategy, landing-page-design
+
+Workflow:
+
+```
+1. Research keywords
+2. Build MVP with SEO in mind
+3. Create content around problem
+4. Launch product
+5. Grow organically
+```
+
+
+## Related Skills
+
+Works well with: `landing-page-design`, `backend`, `stripe`, `seo`

package/bundled-skills/minecraft-bukkit-pro/SKILL.md

@@ -122,6 +122,12 @@ You are a Minecraft plugin development master specializing in Bukkit, Spigot, an
 
 Always leverage WebSearch and WebFetch to ensure best practices and find existing solutions. Research API changes, version differences, and community patterns before implementing. Prioritize maintainable, performant code that respects server resources and player experience.
 
+## Example
+
+**User request:**
+
+> Use @minecraft-bukkit-pro for this task: Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/minimalist-ui/SKILL.md

@@ -19,6 +19,12 @@ tools: [claude, cursor, codex, antigravity]
 - Use when designing warm monochrome interfaces with crisp borders, generous whitespace, muted pastel accents, and quiet motion.
 - Use when the task should avoid gradients, heavy shadows, saturated colors, pill-heavy components, and generic SaaS visuals.
 
+## Example
+
+**User request:**
+
+> Review this interface with @minimalist-ui, identify the highest-impact design problems, and propose an implementation-ready improvement.
+
 ## Limitations
 
 - Minimalism can hide hierarchy when content is dense; validate scannability, contrast, and navigation clarity with real content.

package/bundled-skills/moatmri/SKILL.md

@@ -27,6 +27,12 @@ Ask if not provided:
 - **Entity type** (e.g., "independent broker", "solo practitioner", "regional franchise")
 - **Target name** (optional — specific organization for named analysis)
 
+## Example
+
+**User request:**
+
+> Assess where this business is most exposed to AI disruption and produce a prioritized 90-day defensive plan.
+
 ## Limitations
 
 - Produces strategic risk analysis, not audited market research or investment advice.

package/bundled-skills/molykit/SKILL.md

@@ -7,6 +7,7 @@ description: |
   Chat widget, Messages, PromptInput, Avatar, LLM
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # MolyKit Skill

package/bundled-skills/monday-automation/SKILL.md

@@ -235,6 +235,12 @@ Different column types require different value formats:
 ## When to Use
 This skill is applicable to execute the workflow or actions described in the overview.
 
+## Example
+
+**User request:**
+
+> Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio).
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/monopoly/SKILL.md

@@ -4,6 +4,7 @@ description: >
   MONOPOLY is a Senior System Design Engineer skill for architecting, reviewing, and scaling systems. Triggers on requests involving architecture, databases, scaling, microservices, or infrastructure design. Proactively engages to design resilient backend systems.
 risk: none
 source: community
+date_added: "2026-09-04"
 ---
 
 # MONOPOLY — Senior System Design Engineer

package/bundled-skills/monopoly/patterns/SKILL.md

@@ -2,6 +2,7 @@
 name: patterns
 description: Reference document for monopoly patterns.
 source: community
+date_added: "2026-09-04"
 risk: safe
 reports-to: monopoly
 ---

package/bundled-skills/monopoly/scale-benchmarks/SKILL.md

@@ -2,6 +2,7 @@
 name: scale-benchmarks
 description: Reference document for monopoly scale-benchmarks.
 source: community
+date_added: "2026-09-04"
 risk: safe
 reports-to: monopoly
 ---

package/bundled-skills/monopoly/security-checklist/SKILL.md

@@ -2,6 +2,7 @@
 name: security-checklist
 description: Reference document for monopoly security-checklist.
 source: community
+date_added: "2026-09-04"
 risk: safe
 reports-to: monopoly
 ---
@@ -68,6 +69,11 @@ reports-to: monopoly
 - [ ] HIPAA: if health data — encryption, audit logs, BAA with vendors
 - [ ] SOC 2 Type II: access control, availability, confidentiality evidence
 
+## Example
+
+**User request:**
+
+> Review this Monopoly implementation against its security checklist and report each failed control with evidence.
 
 ## Limitations
 - This is a reference document and may not cover all edge cases. Always verify architectures before production.

package/bundled-skills/monopoly/tech-matrix/SKILL.md

@@ -2,6 +2,7 @@
 name: tech-matrix
 description: Reference document for monopoly tech-matrix.
 source: community
+date_added: "2026-09-04"
 risk: safe
 reports-to: monopoly
 ---

package/bundled-skills/monorepo-architect/SKILL.md

@@ -63,6 +63,12 @@ Expert in monorepo architecture, build systems, and dependency management at sca
 - Document the dependency graph
 - Set up code ownership rules
 
+## Example
+
+**User request:**
+
+> Set up a new monorepo from scratch.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/monte-carlo-analyze-root-cause/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: monte-carlo-analyze-root-cause
-description: "Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling. Activates when a user asks about data issues, incidents, alerts, or..."
+description: "Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling."
 risk: critical
 source: https://github.com/monte-carlo-data/mc-agent-toolkit/tree/main/skills/analyze-root-cause
 source_repo: monte-carlo-data/mc-agent-toolkit

package/bundled-skills/monte-carlo-performance-diagnosis/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: monte-carlo-performance-diagnosis
-description: "Diagnoses pipeline performance issues -- slow jobs, expensive queries, latency trends -- using Monte Carlo's cross-platform observability. Uses a tiered investigation approach: discover problems, bridge to affected tables, then drill into root causes. Activates when a user asks about..."
+description: "Diagnoses pipeline performance issues -- slow jobs, expensive queries, latency trends -- using Monte Carlo's cross-platform observability. Uses a tiered investigation approach: discover problems, bridge to affected tables, then drill into root causes."
 risk: critical
 source: https://github.com/monte-carlo-data/mc-agent-toolkit/tree/main/skills/performance-diagnosis
 source_repo: monte-carlo-data/mc-agent-toolkit
@@ -146,6 +146,12 @@ Structure your response as:
 - **Never expose MCONs, UUIDs, or internal identifiers** to the user. Use human-readable names.
 - **Cross-platform**: This skill works across Airflow, dbt, and Databricks. Note which platform each finding comes from.
 
+## Example
+
+**User request:**
+
+> Diagnose why this pipeline became slow, identify the bottleneck from the available telemetry, and propose the smallest verified fix.
+
 ## Limitations
 
 - Use this skill only when the task clearly matches its upstream source and local project context.