Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongo-to-market-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches go-to-market-plan from ognjengt/founder-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 go-to-market-plan. Access via /go-to-market-plan 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
110
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
110
stars
Analyze the founder's business and current stage to deliver 3 specific, actionable go-to-market strategies that will drive measurable market penetration and customer acquisition.
Check $ARGUMENTS first to determine execution mode:
Respond with: "go-to-market-plan loaded, proceed with details about your product, target market, or current launch situation"
Then wait for the user to provide their requirements in the next message.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
Check if FOUNDER_CONTEXT.md exists in the project root.
Evaluate whether you have enough information to produce high-confidence, actionable go-to-market strategies:
Required information to proceed without questions:
If you have enough context: Proceed directly to Step 4.
If critical information is missing: Proceed to Step 3.
Use the AskUserQuestion tool to gather missing information. Ask between 3-10 questions based on what's needed:
Core GTM questions:
Context-specific questions:
IMPORTANT: Only ask questions for information you truly need. Don't ask for information you can infer from FOUNDER_CONTEXT.md or the user's initial message.
Based on the context gathered, analyze:
Critical analysis principles:
Create exactly 3 GTM strategies, ranked by fit and impact:
Selection criteria:
For each strategy, write:
Part A — The Strategy (What & Why)
Part B — The Exact Playbook (How)
Part C — First Action (Do This Today)
Hard constraints. No interpretation.
BAD: "Use content marketing"
GOOD: "Write 1 deep-dive case study per week showing how [Product] helped [Specific ICP] solve [Specific Problem]. Post on LinkedIn targeting [Job Titles]. Include ROI metrics. Repurpose into email sequence for outbound. Goal: 500 views/post, 20 inbound leads/month."
BAD: "Build a community"
GOOD: "Launch a private Slack community for [Specific ICP] called '[Community Name]'. Seed it with 20 hand-picked customers. Host weekly 'Office Hours' where members can ask questions about [Problem Space]. Incentivize referrals: invite 3 peers = lifetime discount. Goal: 100 members in 60 days, 30% weekly active."
BAD: "Partner with influencers"
GOOD: "Identify 10 YouTubers with 50k-200k subscribers in [Industry] who cover [Topic]. Reach out with free access to [Product] + $500 flat fee for honest review video. Track: views, click-through rate, signups from each video. Goal: 3 partnerships, 500+ signups in 90 days."
Pre-product-market fit: Focus on validation tactics (customer interviews, pilot programs, design partnerships, early adopter communities)
Post-product-market fit, pre-scale: Focus on repeatable acquisition (content engine, outbound playbook, referral loops, strategic partnerships)
Scaling stage: Focus on channel diversification, market expansion, brand building, enterprise upmarket moves
B2B SaaS: Prioritize outbound, content, product-led growth, partnerships, vertical events
B2C apps: Prioritize app store optimization, influencer marketing, viral loops, paid social
Marketplace: Prioritize supply-side first (harder to acquire), demand follows
Developer tools: Prioritize open source, technical content, developer communities, product-led growth
Category creation: Focus on education-first content, thought leadership, category naming/framing
Competitive market: Focus on wedge positioning, differentiated messaging, switching incentives
Before finalizing ANY strategy, ask:
## Your 3 Go-to-Market Strategies
Based on [Product Name]'s current stage and market position, here are your 3 best go-to-market strategies:
---
### Strategy 1: [Strategy Name]
**The Strategy:**
[2-3 sentences: What the GTM approach is, why it fits this product/market, what advantage it leverages]
**The Exact Playbook:**
**Step 1:** [Specific action with details]
**Step 2:** [Specific action with details]
**Step 3:** [Specific action with details]
**Step 4:** [Specific action with details]
**Metrics to Track:**
- [Specific metric 1]
- [Specific metric 2]
- [Specific metric 3]
**Expected Milestones:**
[Concrete outcomes with timeline, e.g., "50 qualified leads within 30 days, 10 customers by day 60"]
**Do This Today:**
[One 30-60 minute action they can take immediately]
---
### Strategy 2: [Strategy Name]
**The Strategy:**
[...]
**The Exact Playbook:**
[...]
**Metrics to Track:**
[...]
**Expected Milestones:**
[...]
**Do This Today:**
[...]
---
### Strategy 3: [Strategy Name]
**The Strategy:**
[...]
**The Exact Playbook:**
[...]
**Metrics to Track:**
[...]
**Expected Milestones:**
[...]
**Do This Today:**
[...]
---
## Execution Priority
**Start with:** Strategy [X] — [One sentence explaining why this is the highest priority right now]
**Why this order:** [2-3 sentences explaining the strategic sequencing — why doing these in this order maximizes market penetration and learning]
---
## Success Criteria
You'll know these strategies are working when:
- [Specific metric/outcome 1 with timeline]
- [Specific metric/outcome 2 with timeline]
- [Specific metric/outcome 3 with timeline]
If you don't see these results, revisit your execution or pivot to a different market segment.
Example:
## Your 3 Go-to-Market Strategies
Based on DevAnalytics's current stage (MVP launched, 12 beta users, targeting engineering managers at Series A-C startups), here are your 3 best go-to-market strategies:
---
### Strategy 1: Design Partnership Program with 5 Target Companies
**The Strategy:**
Position DevAnalytics as a co-creation partner for engineering leaders at high-growth startups who are struggling with team productivity visibility. Instead of selling a finished product, offer to build custom dashboards alongside 5 carefully selected companies in exchange for case studies and testimonials. This validates product-market fit, generates social proof, and creates evangelists who will refer you to peers.
**The Exact Playbook:**
**Step 1:** Identify 5 Series A-C startups (50-150 employees) in your network or LinkedIn 2nd connections who recently raised funding and are likely hiring aggressively. Focus on companies using your tech stack (GitHub, Jira, Linear).
**Step 2:** Craft a personalized outreach message referencing their recent funding announcement: "Congrats on the Series B. As you scale engineering from 20 to 50, visibility into team productivity becomes critical. I'm building DevAnalytics specifically for this problem. Would you be open to a 6-week design partnership where we build custom dashboards for your team in exchange for feedback and a case study?"
**Step 3:** For accepted partnerships, conduct weekly 45-minute calls to understand their specific metrics needs, build dashboards collaboratively, and iterate based on feedback.
**Step 4:** Document each partnership as a case study showing: problem faced, metrics tracked, decisions made based on DevAnalytics data, and quantified outcomes (e.g., "Reduced deployment time by 30%").
**Metrics to Track:**
- Outreach sent: 20 (to get 5 partnerships)
- Partnership acceptance rate (goal: 25%)
- Weekly active users per partnership (goal: >70%)
- Case study completion rate (goal: 100%)
**Expected Milestones:**
5 active design partnerships within 30 days, 3 completed case studies by day 60, 2 paid conversions by day 90.
**Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
mattpocock/skills
affaan-m/everything-claude-code
jwynia/agent-skills
mindrally/skills
kostja94/marketing-skills
github/awesome-copilot
go-to-market-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added go-to-market-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
go-to-market-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: go-to-market-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: go-to-market-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
go-to-market-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added go-to-market-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend go-to-market-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
go-to-market-plan fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in go-to-market-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 25