Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For indie hacker context (first 100 users, Build in Public, Pieter Levels tactics), see indie-hacker-strategy.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncold-start-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches cold-start-strategy from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cold-start-strategy. Access via /cold-start-strategy in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For indie hacker context (first 100 users, Build in Public, Pieter Levels tactics), see indie-hacker-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and positioning.
Identify:
| Channel | Audience | Use | Notes |
|---|---|---|---|
| Product Hunt | Indie makers, early adopters | Launch-day buzz; community upvotes | ~3% conversion; traffic spike; see product-hunt-launch |
| AppSumo / LTD | Deal seekers, early adopters | Lifetime deal for fast revenue, validation | Quick cash; price-sensitive users; see discount-marketing-strategy for LTD structure, trade-offs |
| Subreddit-specific | r/AlphaAndBetaUsers, r/roastmystartup, r/devops, r/SaaS | 80/20 rule; 5+ months for traction; lead with story | |
| Indie Hackers | Indie makers, founders | Sustained engagement; authentic journey | ~23% conversion; 4–6 months; see indie-hacker-strategy for tactics |
| Hacker News | Tech, startups | Show HN launch | Luck + timing; front page = traffic spike |
| Directory submission | AI tools, product launch | Taaft, G2, niche directories | Validate PMF; seed users; see directory-submission |
| Founder-led outbound | B2B, high ACV | Cold email, LinkedIn; 10–15 personalized outreaches/day | Pre-$5K MRR; only reliable path when ACV >$500/mo |
| Community engagement | Target users | Forums, LinkedIn groups, Discord | 45–90 days; contribute value first |
Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough.
Search Twitter/X, LinkedIn, Reddit, and niche communities for demand signals:
| Signal | What to seek |
|---|---|
| Keywords | Industry terms, category keywords, "looking for [X] tool," "best alternative to [Y]" |
| Discussion | Industry threads, complaints about competitors, "anyone used…" or "recommend…" posts |
| Platform | Choose where your audience spends time (Twitter/X, LinkedIn, Reddit, Discord, vertical forums) |
| Step | Practice |
|---|---|
| Search | Service requests related to your product (e.g. "need logo design," "looking for video editor") |
| Identify | Buyers in job descriptions or comments who have related needs |
| Reach | Offer help or tool recommendation; introduce product politely |
Users often have clear need and budget; high intent.
| Practice | Guideline |
|---|---|
| Search | Brand, category, "looking for AI tool," "best alternative to…" |
| Reply | Comment on posts where users express need; avoid spam |
| Tone | Sincere; honest that it's your product; invite trial and feedback |
| Avoid | Hard sell; copy-paste; repeated posting |
Example outreach: "Hi, I'm building something similar. If you'd like to try it: [link]. Happy to hear any feedback—we're iterating actively."
Feedback collection: DM, email, survey, user interview, in-app feedback—choose by channel and context.
Coordinated launch across channels yields 5–6× more users than single-channel:
| Week | Focus |
|---|---|
| 1–2 | Audience building (LinkedIn 3×/week) |
| 3–4 | Beta; community engagement |
| 5 | Pre-launch countdown |
| 6 | Product Hunt + Reddit/Indie Hackers |
| 7 | Post-launch follow-up |
Build in public before launch—share progress, validate ideas, create invested audience. For indie hacker first 100 users, Build in Public content framework (40/30/20/10), Pieter Levels tactics → indie-hacker-strategy.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
cold-start-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend cold-start-strategy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in cold-start-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added cold-start-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in cold-start-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for cold-start-strategy matched our evaluation — installs cleanly and behaves as described in the markdown.
cold-start-strategy reduced setup friction for our internal harness; good balance of opinion and flexibility.
cold-start-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 72