organic-growth-advisor

Identify which organic growth path to pursue — new segments, geographies, channels, or products. Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

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

The skill delivers highly actionable, clearly sequenced interactive guidance with concrete prompts and a reusable recommendation template. Its main weaknesses are verbosity from inline philosophy and worked examples, and a monolithic single-file structure where some detailed material could be split into reference files.

Suggestions

Move the "Why This Order Matters" and "The Knowledge Principle" rationale into a condensed callout or a reference file, keeping the main flow to the matrix, paths, and questions.

Split the four worked examples and/or the path-specific guidance into a separate EXAMPLES.md or PATHS.md, leaving SKILL.md as an overview that links one level deep.

Trim the five Common Pitfalls to the highest-leverage two or three and fold the rest into the relevant path's "Watch out for" note to reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and domain-specific, but sections like "Why This Order Matters" and "The Knowledge Principle" add philosophy beyond what the workflow requires, and four full worked examples plus five pitfalls are carried inline. It could be tightened without losing clarity, so it sits below the lean/efficient anchor.	2 / 3
Actionability	Provides exact question prompts, three enumerated options per step, a copy-ready recommendation template, and per-path diagnostic questions, first experiments, and watch-outs — concrete and immediately executable guidance for an instruction-only interactive skill.	3 / 3
Workflow Clarity	The three adaptive questions are clearly sequenced (Q1 context → Q2 context familiarity → Q3 product change → recommendation), with an explicit output pattern and a referenced facilitation protocol; this advisory triage context does not require destructive-operation validation loops.	3 / 3
Progressive Disclosure	Headers are well organized and cross-skill links (workshop-facilitation, related skills) are one level deep, but the single ~365-line file carries all detailed material — path-specific guidance, examples, and pitfalls — inline rather than splitting into reference files, so it is not an overview pointing to detailed materials.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is concise, third-person, and explicitly pairs a concrete capability statement with a clear "Use when" trigger, covering all four growth paths and the McKinsey framework reference. It is distinct from sibling skills and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Lists four concrete growth actions — "new segments, geographies, channels, or products" — matching the anchor for multiple specific concrete actions rather than a single domain mention.	3 / 3
Completeness	Explicitly answers both what ("Identify which organic growth path to pursue…") and when via a clear "Use when diagnosing where a growth constraint lives…" clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Combines natural PM phrasings ("growth constraint", "new segments", "geographies", "channels", "products") with the specific framework trigger ("McKinsey growth level"), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to organic growth path triage across McKinsey levels L2–L5, a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/organic-growth-advisor/SKILL.md
Commit: 9971018

Reviewed: 3 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.