plg-strategy

plg-strategy is a skill for Claude Code from ranjeeetvimal/growth-skills. It costs 185 tokens per session (1,473 once invoked), scanned A, original, MIT.

A product-led growth strategy skill for planning how a product can attract, activate, retain, and convert users through the product itself. Product-led growth means the product is a main driver of adoption and expansion, rather than relying only on sales or advertising.

In plain words
What is it for?
Use it to design growth loops, improve activation and retention, plan monetization, address a growth ceiling, and create strategy, risk, decision, and timeline documents.
Why use it?
It helps founders make connected strategic choices instead of collecting isolated growth tactics. The output explains alternatives, risks, evidence, decisions, and an executable 30-day plan.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the plg-architect plugin — 7 skills shipped together

Good fit Use it to design growth loops, improve activation and retention, plan monetization, address a growth ceiling, and create strategy, risk, decision, and timeline documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ranjeeetvimal/growth-skills/plg-strategy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ranjeeetvimal/growth-skills --skill plg-strategy
Clone the repo
git clone --depth 1 https://github.com/ranjeeetvimal/growth-skills

Made for: Claude Code.

Or install plg-architect, the plugin that ships this one along with the rest of its 7 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for plg-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/ranjeeetvimal/growth-skills/plg-strategy/github.svg)](https://agentmods.dev/skills/ranjeeetvimal/growth-skills/plg-strategy)
Your own site
<a href="https://agentmods.dev/skills/ranjeeetvimal/growth-skills/plg-strategy"><img src="https://agentmods.dev/badge/skills/ranjeeetvimal/growth-skills/plg-strategy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for plg-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/ranjeeetvimal/growth-skills/plg-strategy"><img src="https://agentmods.dev/badge/skills/ranjeeetvimal/growth-skills/plg-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 185 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,473 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00185 $0.01473
Opus 5 $0.00093 $0.00737
Sonnet 5 $0.00037 $0.00295
Haiku 4.5 $0.00018 $0.00147

Measured 11d ago against content hash a3b51ff858e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

plg-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

PLG-Architect/skills/plg-strategy/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PLG Growth Architect — Founder Strategy Partner

You are a co-founder who has built and exited PLG companies. You don't just advise — you architect: legible reasoning, real alternatives, a plan concrete enough to execute Monday, and durable artifacts others build on.

Reference library (read on demand — pull the DEPTH into your output, don't just cite it)

  • references/plg-playbook.md — concrete moves menu (loops, activation, retention, monetization, breaking a ceiling).
  • references/plg-frameworks.md — macro thesis, quantified-bet format, red-team patterns.
  • references/architect-artifacts.md — templates for the Evidence Framework, Strategy Snapshot, Decision Log (ADR), Alternative Strategies, Risk/Unknowns registers, Kill/Pivot, and the Now/30/90/Post-PMF timeline. This is what makes you an architect, not an advisor.

Rules

  1. Elaborate — never summarize. Work every recommendation out in full: the step-by-step mechanic, a concrete worked example for THIS business, why it fits, and the expected outcome. A one-line bet or a bare table is a failure. Write like you're briefing the person who has to execute it Monday. Pull the real depth from the playbook.
  2. Connected, one narrative. The report has a through-line: problem → strategy → the specific plays → the 30-day plan. Build on each part; reference prior findings to advance the argument. Don't fragment into disconnected bullets, and don't pad with verbatim repeats.
  3. Give both — a specific plan AND the honest read, threaded. Label claims with the Evidence Framework ([Fact]/[Evidence]/[Inference]/[Assumption]/[Hypothesis]) + confidence. No strategy rests on an unlabeled assumption.
  4. Alternatives, not one thesis. Offer 2-3 viable strategies, pros/cons, win probability, and recommend one with the deciding factor.
  5. Every recommendation states its trade-off (gained vs sacrificed) and one second-order consequence.
  6. Respect constraints (budget, runway, team, founder strengths, eng capacity) from founder-context. Sequence by Impact × Confidence ÷ Effort, tie-broken by time-sensitivity and strategic importance.
  7. Answer the founder's fear. If it's a ceiling/scale fear, MODEL it (playbook). Don't just name it.

Read the full file on GitHub · 90 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 90 lines · 185 tokens per session scan A a3b51ff858e3

Subscribe to this mod's changes

plg-strategy is a skill published in the GitHub repository ranjeeetvimal/growth-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 185 tokens to every session and 1,473 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

research-seo-demand

A Chinese-language process for researching SEO opportunities, where SEO means improving pages so they can appear in search results. It studies user needs, keyword demand, search-result pages, and competing pages using Bing data.

tsingyuai/growth-lab · 102 tokens

create-seo-page

A Chinese-language workflow for creating and implementing search-focused pages in an existing product repository. SEO means improving a page so it can be found and understood through search engines.

tsingyuai/growth-lab · 93 tokens

review-seo-performance

A review process for evaluating search visibility and AI citations using Bing Webmaster data. It examines whether pages are indexed, how they appear in searches, and when AI-generated answers cite them.

tsingyuai/growth-lab · 85 tokens

xhs-render-cards

A production guide for turning approved Xiaohongshu drafts into reviewable image cards. Xiaohongshu is a social platform where these cards are published, and the guide covers copy, evidence, visual planning, and compliance.

tsingyuai/growth-lab · 89 tokens

run-seo-page-loop

Run an SEO page observation-action-review loop with persistent Memory by coordinating demand research, page creation, adversarial review, image generation, IndexNow submission, and performance review. Use when taking an SEO page from opportunity discovery through publication, measurement, iteration, or continuing a…

tsingyuai/growth-lab · 65 tokens

xiaohongshu-mcp

A browser-based, read-only process for researching posts on Xiaohongshu, a Chinese social platform for user-created lifestyle and product content. It can collect search results, candidate cover images, selected post details, and sanitized evidence.

tsingyuai/growth-lab · 78 tokens