CtrlK
BlogDocsLog inGet started
Tessl Logo

map-growth-loops

Identify, map, and measure the self-reinforcing growth loops in your product — viral, content, paid, and usage loops. Understand cycle time, throughput, and where loops are broken. Use when a PM needs to move beyond linear funnel thinking and understand the compounding systems that drive sustainable growth.

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 detailed, highly actionable prompt-template skill with a clear sequenced workflow and concrete output spec. Its weaknesses are mild verbosity in the conceptual framing and a monolithic structure with no progressive disclosure of reference material.

Suggestions

Trim the conceptual framing in the intro and the "You are a growth strategist..." persona line, which a capable model does not need.

Consider moving the canonical loop-type taxonomy and the metrics/branching-factor reference into a separate reference file linked from the body, so the main template stays lean.

DimensionReasoningScore

Conciseness

The body is mostly efficient domain-specific structure (loop taxonomy, metrics, anti-plays), but the conceptual intro ("Funnels are useful for diagnosis but dangerous for strategy...") and persona framing add explanation a capable model does not need.

2 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance: canonical loop types with triggers, exact metrics (branching factor thresholds, a conversion-table example), named break types, and a fixed output format.

3 / 3

Workflow Clarity

A clearly sequenced five-step process (Identify → Measure → Find breaks → Assess interactions → Recommend) with a defined output checklist; the task is analytical rather than destructive/batch, so no validate-fix-retry loop is required.

3 / 3

Progressive Disclosure

Well organized with clear section headers and a numbered step hierarchy, but it is a long (>50 line) monolithic document with no external references to offload the detailed loop taxonomy or metrics reference material.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, third-person description that states concrete capabilities and an explicit "Use when" trigger. Its only gap is that the most common conversational trigger terms (flywheel, viral loop, network effects) live in suggest_when rather than the description field.

Suggestions

Fold one or two high-frequency trigger terms (e.g. "flywheel", "network effects") directly into the description so they are present in the evaluated field, not just suggest_when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Identify, map, and measure the self-reinforcing growth loops" and "Understand cycle time, throughput, and where loops are broken" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Identify, map, and measure... growth loops") and when ("Use when a PM needs to move beyond linear funnel thinking..."), matching the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Includes natural terms like "growth loops" and the loop-type names (viral, content, paid, usage), but common user variations such as "flywheel", "viral loop", and "network effects" appear only in suggest_when, not the description itself.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (compounding growth-loop systems vs. linear funnel tactics) with distinct triggers, and is differentiated from sibling skills like diagnose-acquisition and diagnose-retention.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
amplitude/builder-skills
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.