build-plg-strategy

Design a product-led growth strategy for your product — classify your PLG motion, define activation and monetization architecture, choose distribution channels, plan the PLG-to-sales bridge, and build defensibility. Incorporates AI-era shifts in distribution, pricing, and user expectations. Use when building or overhauling a growth strategy.

Quality

60%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./growth-skills/skills/build-plg-strategy/SKILL.md

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly articulates specific capabilities and includes an explicit 'Use when' clause. The main weakness is that trigger terms could be broader to capture more natural user phrasings (e.g., 'GTM strategy', 'freemium model', 'self-serve growth'). The description also uses second person ('your product') which is a minor voice issue, though the core actions are described in imperative/third-person form.

Suggestions

Add more natural trigger terms users might say, such as 'go-to-market', 'GTM', 'freemium', 'self-serve', 'conversion funnel', or 'user acquisition strategy'.

Rephrase 'for your product' to third person (e.g., 'for a product') to maintain consistent voice.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: classify PLG motion, define activation and monetization architecture, choose distribution channels, plan PLG-to-sales bridge, and build defensibility. These are distinct, actionable steps.	3 / 3
Completeness	Clearly answers 'what' (classify PLG motion, define activation/monetization architecture, choose distribution channels, etc.) and 'when' ('Use when building or overhauling a growth strategy'). The 'when' clause is explicit though somewhat broad.	3 / 3
Trigger Term Quality	Includes relevant terms like 'product-led growth', 'PLG', 'growth strategy', 'activation', 'monetization', 'distribution channels', but misses common user variations like 'go-to-market', 'GTM', 'freemium', 'conversion funnel', 'onboarding', or 'self-serve'. The domain is somewhat niche, limiting natural keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The description is highly specific to product-led growth strategy, a distinct niche. Terms like 'PLG motion', 'PLG-to-sales bridge', and 'activation and monetization architecture' are unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive PLG strategy guide that reads more like a textbook chapter than a skill for Claude. Its main weakness is verbosity — extensive domain context and concept explanations that Claude doesn't need consume significant token budget. The workflow is well-structured but lacks validation checkpoints and concrete output examples (sample deliverables, scoring templates) that would make it truly actionable.

Suggestions

Cut the 'Domain Context' section by 70% — remove explanations of what PLG is and why activation matters; keep only the 'What Has Changed' bullets and 'When PLG Is Not Right' as brief filters. Claude knows PLG fundamentals.

Add a concrete example output for Step 7 — show a sample action plan with specific PQA/PQL definitions, a sample behavioral scoring table, and an example 30-day action list so Claude knows the expected format and depth.

Add validation checkpoints: after Step 1 (confirm classification with user before proceeding), after Step 2 (validate aha moment definition against user data), and after Step 7 (review plan against stated goals).

Move the 'PLG Fundamentals That Still Hold' and 'When to Use' sections into a separate reference file or collapse them into 3-4 bullet decision criteria at the top.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It explains PLG fundamentals Claude already knows (what PLG is, what activation means, basic pricing models), includes extensive domain context that could be summarized in a few bullets, and pads with unnecessary framing like 'not the 2018 playbook.' Much of the 'Domain Context' and 'When PLG Is Not Right' sections explain concepts rather than instruct.	1 / 3
Actionability	The skill provides structured steps and frameworks (classify motion, design activation, etc.) with specific questions to answer and deliverables to produce, but lacks concrete executable examples — no sample outputs, no template formats, no example PQA scoring rubric, no sample pricing table. It's strategic guidance rather than copy-paste-ready artifacts.	2 / 3
Workflow Clarity	The 7-step sequence is clearly ordered and Step 7 provides a concrete deliverable checklist. However, there are no validation checkpoints or feedback loops — no way to verify if the PLG classification is correct, no criteria for when to revisit activation architecture, and no explicit 'if X then reconsider Y' decision points within the workflow.	2 / 3
Progressive Disclosure	The skill references companion skills (north-star-metric, build-metric-tree, diagnose-activation, etc.) which is good progressive disclosure, but the main body is monolithic — the Domain Context section alone could be a separate reference file. With no bundle files, all content is inline, making the skill unnecessarily long for initial consumption.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: amplitude/builder-skills
Commit: 221ffaa

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.