CtrlK
BlogDocsLog inGet started
Tessl Logo

growth-loops

Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-go-to-market/skills/growth-loops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is a well-structured, moderately actionable framework: clear five-step workflow, concrete input/output specifications, and good single-file organization. Its main weakness is token efficiency — redundant Overview/When to Use sections and re-explanations of well-known product concepts — plus a missing loop-coefficient formula at the heart of the quantitative step.

Suggestions

Remove or merge the Overview and When to Use sections (they restate the frontmatter description) and trim loop-type definitions to only the non-obvious taxonomy details to cut token cost.

Add the explicit loop coefficient formula (e.g., k = invites per user per cycle x conversion rate) with a short worked numeric example in Step 4, and add an explicit iterate/measure checkpoint in Step 5 for loops that underperform.

Consider moving the per-loop examples and Further Reading links into a references/ file (e.g., references/loop-examples.md) so SKILL.md stays a lean overview, consistent with progressive disclosure.

DimensionReasoningScore

Conciseness

The Overview and When to Use sections restate the frontmatter description, and loop definitions like "Users invite other potential users in exchange for rewards, incentives, or social recognition" largely restate product concepts Claude already knows. It is mostly efficient with no tutorial-style padding (not level 2), but the redundancy and re-explaining of known concepts keep it below level 4.

3 / 5

Actionability

Concrete specs are given for inputs ("Use $ARGUMENTS to pass: Product description and primary user action...") and outputs ("Ranked evaluation of all 5 loop types... 30-60-90 day implementation roadmap"), and Step 4 lists concrete variables ("Invites/shares per user per cycle", "Conversion rate of invites"). It misses level 5 because "Calculate Loop Coefficient" omits the actual formula and "Create specific loop implementation" stays abstract.

4 / 5

Workflow Clarity

"Step 1: Define Product Value" through "Step 5: Build the Loop" forms a clear, logically sequenced process with concrete sub-bullets at each step. It falls short of level 5 because validation is implicit ("Measure loop metrics and conversion rates") with no explicit iterate-on-underperformance checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well organized into Overview, loop taxonomy, process, Input Format, Output, and Tips with clearly signaled Further Reading links. At ~120 lines it exceeds the under-50-line simple-skill exception, so the per-loop examples and reading links could arguably move to a reference file, holding it below level 5.

4 / 5

Total

15

/

20

Passed

Description

83%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 description: it states concrete capabilities with an enumerated taxonomy, includes an explicit multi-trigger 'Use when...' clause, and occupies a distinct niche. The only gaps are a few missing natural synonyms (e.g., PLG, network effects) and slight overlap risk with general growth-strategy skills.

DimensionReasoningScore

Specificity

"Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral" names several specific actions and enumerates all five types. It falls short of the level-5 anchor's comprehensive concrete-action coverage (only two verbs — identify and evaluate), but exceeds level 3's '1-2 concrete actions' via the full type enumeration.

4 / 5

Completeness

It explicitly answers both what ("Identify growth loops... Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral") and when ("Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work") with concrete trigger phrases. This matches the level-5 anchor exactly; level 4's 'when could be more explicit' does not apply since the Use-when clause lists three distinct triggers.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "growth loops", "flywheels", "viral", "referral", "product-led traction", "designing growth mechanisms". A few common terms are missing ("PLG", "network effects", "viral coefficient", "user acquisition"), which keeps it below the comprehensive level-5 anchor but comfortably above the sparse level-3 example.

4 / 5

Distinctiveness Conflict Risk

"Growth loops (flywheels)" is a clear niche with distinctive triggers unlikely to fire the wrong skill. Minor overlap risk remains with broader growth-marketing or product-strategy skills, which keeps it just below the level-5 'minimal conflict risk' anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-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.