Growth Skills by Ranjeet Vimal

Open-source agent skills for founder-led growth — PLG strategy, SEO, and X / social-media growth. Works in Claude Code, Cursor, Gemini CLI, GitHub Copilot, and Antigravity — any agent on the Agent Skills spec. Built by founders, for founders.

Skill suites

Each suite is self-contained — click through for its skills, run order, and copy-paste example prompts.

Suite	Skills	Status	What it covers
PLG-Architect →	7	✅ Live	Founder-context intake, PLG strategy, ICP research, competitive moats, viral loops, content strategy, growth metrics
SEO →	11	🚧 In progress	Gatekeeper (seo-context) live + tested; 10 specialists scaffolded (technical/AI-search audit, keyword & competitor research, strategy, on-page, content, link building, local, programmatic, analytics)
Social Media →	2	🚧 In progress	Platform-picking gatekeeper (social-context) + per-platform growth. x-growth (X / Twitter) live; LinkedIn, Instagram, TikTok, YouTube planned
Paid-Marketing	0	🚧 Coming soon	Meta Ads, Google Ads, TikTok Ads, creative testing, attribution
Analytics	0	🚧 Coming soon	Event tracking, cohort analysis, experiment design, data pipelines

Quick start

Zero to running a skill in four steps.

1. Install — one command installs all the skills. Works in Claude Code, Cursor, Gemini CLI, GitHub Copilot, and Antigravity (installs into .agents/skills/, shared across agents):

npx skills add ranjeeetvimal/growth-skills

Install the whole thing — that's the intended path. The suites are small, and the skills work together: gatekeepers like seo-context and social-context route you to their sibling skills, so installing just one leaves you with hand-offs that go nowhere (this trips people up).

• Want one whole suite? In Claude Code: /plugin install seo@growth-skills (or plg-architect / social-media) — installs every skill in that suite. See Other install methods.
• A single standalone skill? npx skills add ranjeeetvimal/growth-skills --skill <name> — only for a skill that doesn't route anywhere (e.g. founder-context).

2. Reload so the agent discovers the new skills — this is not a shell command:

• Claude Code: type /reload-skills in the session.
• Cursor / Gemini CLI / Copilot / Antigravity / others: restart the session.

3. Invoke by describing your goal — skills auto-activate by context, so you rarely name them:

Set up my founder context for ranjeetvimal.com — interview me about my business.

founder-context reads your site, auto-drafts your business (product, ICP, positioning), confirms it with you via quick options, and saves .claude/founder-context.md. Every other skill reads that file, so you explain your business only once — then it points you to the next skill.

4. Follow the hand-off. Each skill leaves a shared .claude/*.md file and recommends the next one, so context flows forward — Context → Research → Strategy → Execution — and you never re-enter the same information.

More examples — describe the goal, and the right skill activates:

I need a PLG strategy for my SaaS. We help [X] do [Y].     → plg-strategy
Validate my ICP — I think it's [target audience].          → icp-research
Find my real moats. We lose deals to [A] and [B].          → competitive-intel

The PLG-Architect suite (above) is fully live. SEO and Social are usable but still in progress — start at seo-suite/ (seo-context) or social-media/ (x-growth).

Other install methods

Claude Code native plugin — /plugin marketplace add …

Run these inside a Claude Code session (not the shell):

/plugin marketplace add ranjeeetvimal/growth-skills
/plugin install plg-architect@growth-skills       # or: seo@growth-skills · social-media@growth-skills

Browse interactively with /plugin. Later updates: /plugin marketplace update growth-skills then /plugin update <plugin>@growth-skills.

claude.ai web — ZIP upload, or org GitHub sync

• ZIP upload (any plan): ZIP an individual skill folder so SKILL.md sits at the ZIP root → claude.ai → Customize → Skills → Upload skill. Requires code execution enabled.
• Org GitHub sync (Team / Enterprise admins): Organization settings → Plugins → Add plugin → GitHub, in owner/repo format.

  ⚠️ Web GitHub sync only accepts private / internal repos with the Claude GitHub App installed. This repo is public — fork it private first, or just use the CLI / /plugin methods.

Project-local or Git submodule — team sharing

# Copy skills into your repo so the whole team gets them on clone
mkdir -p .claude/skills && cp -r /path/to/growth-skills/PLG-Architect/skills/* .claude/skills/

# ...or track this repo as a submodule
git submodule add https://github.com/ranjeeetvimal/growth-skills.git .claude/skills/growth-skills

Updating & reloading

npx skills add ranjeeetvimal/growth-skills   # pulls NEW skills and updates existing ones

Then reload (/reload-skills in Claude Code, or restart your agent).

Why add and not update?

npx skills update only refreshes skills you already have — it skips new skills added since your last install. Re-running add installs what's missing and overwrites the rest. A Failed to check for deleted skills warning is harmless.

• Plugin users: /plugin marketplace update growth-skills then /plugin update <plugin>@growth-skills.
• Verify / remove: npx skills list · npx skills remove --skill <name>.

Philosophy

Every skill follows the same principles:

1. Founder-first — hard questions before answers.
2. Bet-driven — every recommendation is a quantified bet, not a tactic list.
3. Sacrifice-focused — strategy is what you WON'T do, with reasons.
4. Evidence-typed — claims labeled Fact / Evidence / Inference / Assumption / Hypothesis, with confidence.
5. Human tone — short sentences, real opinions, "I think," "I worry."

Contributing

1. Fork the repo.
2. Add your skill under <Suite>/skills/<skill-name>/ (SKILL.md + evals/evals.json).
3. Follow an existing skill as the template — e.g. plg-strategy.
4. Run python3 scripts/validate_skills.py (CI runs it too), then open a PR.

Full guide in CONTRIBUTING.md.

License

MIT — Ranjeet Vimal. Changelog: the commit history.