Comprehensive growth strategy combining technical SEO/SMO/CRO implementation with strategic growth frameworks.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongrowth-strategyExecute the skills CLI command in your project's root directory to begin installation:
Fetches growth-strategy from manojbajaj95/claude-gtm-plugin 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 growth-strategy. Access via /growth-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
29
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
29
stars
Comprehensive growth strategy combining technical SEO/SMO/CRO implementation with strategic growth frameworks.
| Situation | Use This Skill For |
|---|---|
| SEO/SMO/CRO implementation | Technical Optimization |
| Building growth engines | Growth Loops Framework |
| Strategic growth planning | Strategy & Frameworks |
| Distribution strategy | Channel & Platform Strategy |
| Network effects | Product-Led Growth |
Growth is the systematic application of product, engineering, and data to create compounding user acquisition, activation, and retention. It's a mindset, not a department.
Funnels: Linear. Pour effort in, get results out, start over. Loops: Each cycle generates fuel for the next cycle.
The key shift: Move from "How do we get more users?" to "How does each user we acquire generate more users?"
| Loop Type | Description |
|---|---|
| Content Loops | Users create content → attracts more users → more content |
| Viral Loops | Users invite others → exponential spread |
| Sales Loops | Customers generate revenue → fund more acquisition |
| Pattern | Insight |
|---|---|
| Funnels vs Loops | Funnels are linear; loops compound |
| Paid ≠ Loop | Paid acquisition doesn't compound — it's buying users |
| Founder-Led First | Can't outsource finding growth model |
| Product Must Own Growth | Can't be marketing-only function |
| One Primary Loop | Others supplement but won't save you |
| Earned Over Paid | Invest 80%+ in earned/owned channels |
New platforms open, then close. Time your bets correctly:
Page-Level
<title> — unique, 50-60 chars, primary keyword<meta name="description"> — 150-160 chars<link rel="canonical"> — self-referencing<h1> with primary keywordalt text on all imagesSite-Level
robots.txt not blocking important resourcessitemap.xml up to date<meta property="og:type" content="website">
<meta property="og:title" content="Page Title">
<meta property="og:description" content="Description">
<meta property="og:image" content="https://example.com/og-image.png">
<meta property="twitter:card" content="summary_large_image">
| Pillar | Goal | Key Metrics |
|---|---|---|
| SEO | Be found | Organic traffic, rankings |
| SMO | Be shared | Social CTR, shares |
| CRO | Convert | Signup rate, completion |
LTV = (Average Revenue Per Customer × Average Customer Lifespan) - CAC
| Metric | Definition |
|---|---|
| Acquisition | Users come from |
| Activation | First meaningful use |
| Retention | Users come back |
| Referral | Users invite others |
| Revenue | Users pay |
| Type | Description |
|---|---|
| Direct | More users → more value (social networks) |
| Indirect | More users → more options → more value (marketplaces) |
| Two-sided | Supply and demand sides benefit (platforms) |
| Data | More data → better product → more users |
| Metric | Target |
|---|---|
| Activation rate | > 40% |
| Time to value | < 5 minutes |
| Weekly active ratio | > 20% |
| Expansion revenue | > 20% of total |
| Factor | Score (1-10) |
|---|---|
| Impact | Could this double growth? |
| Confidence | How sure will this work? |
| Ease | How easy to implement? |
| Stage | Growth Focus |
|---|---|
| Pre-PMF | Founder-led, iterate on product |
| Finding PMF | First 100 customers, understand channels |
| Validated PMF | First growth hire, build experiments |
| Scaling | Full growth team, channel expansion |
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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
growth-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: growth-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added growth-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in growth-strategy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: growth-strategy is focused, and the summary matches what you get after install.
growth-strategy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
growth-strategy has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added growth-strategy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
growth-strategy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: growth-strategy is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 30