CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced interactive triage skill with concrete questions, templates, and worked examples. Its main weaknesses are redundancy between the per-path "Watch out for" and "Common Pitfalls" sections and a long monolithic body that does not leverage progressive disclosure via bundle files.

Suggestions

Collapse the "Common Pitfalls" section or the per-path "Watch out for" blocks into one location to remove the near-duplicate content and recover tokens.

Move the four worked examples and/or the path-specific guidance into a reference file (e.g., references/path-guidance.md) and link to it from SKILL.md to improve progressive disclosure.

Tighten the "Knowledge Principle" and "Why This Order Matters" prose to bullet-level directives so the body assumes more of Claude's competence.

DimensionReasoningScore

Conciseness

The body is mostly efficient and the McKinsey/matrix content is genuinely domain-specific, but the "Common Pitfalls" section substantially duplicates the per-path "Watch out for" guidance (Pitfall 1↔L5, 2↔L4, 3↔L3, 4↔L2), and prose like the Knowledge Principle could be tightened.

3 / 5

Actionability

It provides three concrete adaptive questions with enumerated options, a copy-paste recommendation template, path-specific diagnostic questions and first experiments (e.g., "Add a subtle 'Made with [Product]' watermark"), plus four fully worked examples — concrete and execution-ready for an instruction-only skill.

5 / 5

Workflow Clarity

The Q1→Q2→Q3→Recommendation sequence is clearly ordered with adaptive handling of ambiguous answers (Q3 option 3 "Somewhere in between — Describe"), but there is only a soft feedback loop ("if the recommendation does not feel right") rather than explicit validation checkpoints.

4 / 5

Progressive Disclosure

Structure is well-sectioned and the workshop-facilitation reference is one level deep and clearly signaled, but with no bundle files the ~370-line body inlines examples, pitfalls, and path-specific guidance that could be split into reference files, leaving organization short of the well-split anchor.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

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, third-person description that clearly states both capability and trigger conditions with concrete, domain-specific language. It is distinguishable and well-targeted, with only minor room to add more action verbs or synonym triggers.

DimensionReasoningScore

Specificity

"Identify which organic growth path to pursue — new segments, geographies, channels, or products" names the domain and enumerates four concrete path types, but relies on a single action verb rather than listing multiple distinct actions, so it sits just below the comprehensive multi-action anchor.

4 / 5

Completeness

It explicitly answers both what ("Identify which organic growth path to pursue — new segments, geographies, channels, or products") and when ("Use when diagnosing where a growth constraint lives and which McKinsey growth level to act on next") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"diagnosing where a growth constraint lives" and "which McKinsey growth level to act on next" are natural trigger phrases a PM would plausibly say, with good keyword coverage, though common variations like "growth is stalling" are absent.

4 / 5

Distinctiveness Conflict Risk

"organic growth path," "McKinsey growth level," and the four enumerated paths carve a clear niche with distinct triggers and minimal overlap risk against generic strategy skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.