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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A well-structured, highly actionable strategy skill with a clear 7-step workflow and concrete deliverables. It is let down by verbosity in the fundamentals section and a monolithic structure with no progressive disclosure to reference files.

Suggestions

Trim the 'PLG Fundamentals That Still Hold' section to non-obvious points only — the product-as-salesperson, PQL-vs-MQL, and time-to-value concepts are already known to Claude; keep the AI-era 'What Has Changed' content, which is genuinely current.

Move the 'Domain Context' exposition and detailed per-step definitions into a reference file (e.g. references/plg-context.md), keeping SKILL.md a lean overview plus the 7-step prompt, so progressive disclosure is one level deep.

Cut rhetorical framing that does not change behavior, e.g. 'Do not hedge. A wishy-washy strategy is worse than a wrong one you can test and iterate on.'

Dimension	Reasoning	Score
Conciseness	The ~200-line body is mostly efficient, but the 'PLG Fundamentals That Still Hold' section re-explains concepts Claude already knows (product-as-salesperson, PQL vs MQL, time-to-value) and adds rhetorical padding ('Do not hedge. A wishy-washy strategy is worse than a wrong one'), matching the score-2 anchor rather than the lean score-3 case.	2 / 3
Actionability	Provides concrete, specific guidance throughout — a 7-step process with defined terms (PQA/PQL, five pricing models with tradeoffs, five moat strategies) and a deliverable checklist ('Top 3 actions… Start each with a verb… start executing tomorrow') — matching the score-3 anchor for an instruction-only skill.	3 / 3
Workflow Clarity	Steps 1–7 are clearly sequenced and synthesize into an 8-item deliverable checklist; no validation checkpoints are present, but the rubric's feedback-loop cap applies only to destructive/batch operations, which strategy generation is not.	3 / 3
Progressive Disclosure	The skill is a monolithic ~200-line file with no references/scripts/assets bundle files present, and the inline 'Domain Context' / 'What Has Changed' exposition could be split into a reference file — matching the score-2 anchor rather than the one-level-deep reference pattern at score 3.	2 / 3
	Total	10 / 12 Passed

Description

90%

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

A strong, concrete description with explicit trigger guidance and natural domain keywords occupying a distinct niche. The only weakness is second-person voice ('your product'), which costs it one point on specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('classify your PLG motion, define activation and monetization architecture, choose distribution channels, plan the PLG-to-sales bridge, and build defensibility') matching the score-3 anchor, but the description uses second-person voice ('for your product'), which the rubric penalizes by reducing specificity by one.	2 / 3
Completeness	Explicitly answers both what (the concrete actions) and when via the 'Use when building or overhauling a growth strategy.' clause, satisfying the score-3 anchor and avoiding the missing-trigger cap at 2.	3 / 3
Trigger Term Quality	Contains natural domain terms a user would actually say — 'product-led growth', 'PLG motion', 'growth strategy', 'distribution channels', 'monetization' — giving good coverage matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (product-led growth / self-serve architecture) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor rather than the overlapping score-2 case.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 2 days 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.