Skill: orime/micro-saas-launchpack (version 1.0.0)

--- name: micro-saas-launchpack version: 1.0.0 description: | Turn a rough product idea into a practical money-making launch pack. Use when the user wants to validate an idea, find a niche, design an MVP, set pricing, write landing-page copy, choose distribution channels, or build a 7-30 day launch plan for a solo product or AI side project. No external APIs or setup required. --- # Micro SaaS Launch Pack Turn a vague idea into something a solo builder can actually ship and sell. This skill is for moments like: - "I have an idea but don't know if it's worth building" - "Help me find a niche that can make money" - "How should I price this?" - "What's the smallest MVP I can ship this week?" - "Write my landing page" - "Give me a launch plan" ## Core principles 1. Revenue beats novelty. 2. Narrow beats broad. 3. Fast validation beats long planning. 4. Painkiller beats vitamin. 5. A simple offer with a clear buyer is usually enough for version 1. ## What to do When the user gives an idea, market, audience, or messy brainstorm, produce a structured launch pack. ### Step 1: clarify the business in one line Compress the idea into this format: `We help [specific user] achieve [valuable outcome] without [main frustration].` If the idea is too broad, narrow it. If the user gave multiple audiences, pick the most painful and easiest-to-reach one. ### Step 2: score the idea quickly Give 1-10 scores with one-sentence reasoning for: - urgency of pain - willingness to pay - ease of reaching users - speed to MVP - defensibility / wedge - founder fit (if user background is known) Then give: - overall verdict: `build now`, `test first`, or `skip` - biggest risk - fastest validation test ### Step 3: define the smallest sellable MVP Design the MVP around the minimum result a buyer would pay for. Return exactly these sections: - `Buyer` - `Pain` - `Promise` - `Inputs required from user` - `Core workflow` - `What v1 must include` - `What to cut from v1` - `Success metric in first 14 days` Bias hard toward things that can be built by one person in days, not months. ### Step 4: pricing and offer design Provide 3 pricing options: - low-friction starter - main offer - premium / done-with-you / team For each option include: - price range - who it is for - what is included - why someone would choose it If recurring SaaS is a bad fit, say so and suggest a service-first or hybrid offer. ### Step 5: landing page copy Write a simple landing page using this structure: 1. headline 2. subheadline 3. 3 benefit bullets 4. who it is for / not for 5. how it works (3 steps max) 6. offer / pricing summary 7. CTA 8. FAQ (3-5 questions) Rules: - plain language - specific outcomes - no fake hype - no empty buzzwords ### Step 6: distribution plan Choose the 3 best channels for this idea. Examples: - X / Twitter - Reddit - cold DM / cold email - indie communities - creator partnerships - SEO - short-form content - existing audience / client base - marketplaces For each chosen channel provide: - why it fits - first action to take - example post / pitch / outreach angle ### Step 7: 7-day launch plan Give a day-by-day plan with one concrete outcome per day. Use this structure: - Day 1: decision + scope - Day 2: MVP skeleton - Day 3: offer + payment path - Day 4: landing page - Day 5: outreach content - Day 6: distribution push - Day 7: feedback + iteration If the idea is not good enough yet, convert the 7-day plan into a 7-day validation sprint instead. ## Output format Use this exact top-level structure: # One-line business # Scorecard # MVP definition # Pricing and offer # Landing page copy # Distribution plan # 7-day plan # Brutal truth In `Brutal truth`, say the uncomfortable thing that most matters. Examples: - the market is too broad - buyer is unclear - this should be a service first - distribution is harder than the build - this only works if the user already has an audience ## Special cases ### If the user only has a domain, trend, or interest Generate 3 business angles and rank them. Then continue with the best one. ### If the user wants "something that can make money fast" Prefer: - B2B niche tools - workflow automation - reporting / monitoring - compliance / content operations - lead-gen helpers - internal productivity tools with clear ROI Avoid ideas that require: - two-sided marketplaces - heavy network effects - lots of content before value exists - complex mobile apps as v1 - deep infrastructure before first payment ### If the user asks for code/app planning too Add a short appendix: - tech stack recommendation - build order - fastest no-code / low-code fallback ## Style Be commercially sharp. Act like a pragmatic founder friend who wants the thing to earn its first money, not win an innovation award. Prefer directness over politeness when the tradeoff matters. ## Example trigger inputs - "I want to build an AI tool for restaurant owners" - "Help me validate a side project idea" - "I have a product idea but don't know how to price it" - "Turn this idea into a launch plan" - "Find me a niche AI SaaS idea for HR teams"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)