dotfiles/dot_config/skillshare/skills/growth-loops/SKILL.md
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.
npx skillsauth add pkking/dotfiles growth-loopsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Identify and design growth loops (flywheels) that create sustainable traction. This skill evaluates five proven growth loop mechanisms to reduce reliance on paid acquisition and build product-led growth.
Product content created by users gets shared on external platforms, bringing new users back to the product.
Users create content or value within the product, then share it, which invites new users or drives re-engagement.
Users invite colleagues to co-create or collaborate within the product, expanding the user base within organizations.
Users discover new content or features through other users' creations, then create and share their own content.
Users invite other potential users in exchange for rewards, incentives, or social recognition.
Clarify the core value users experience:
Assess which growth loops align with your product:
Create specific loop implementation:
Estimate growth velocity:
Implement the highest-leverage loop first:
Use $ARGUMENTS to pass:
A growth loops analysis including:
Based on growth loops research by Ognjen Bošković. Focuses on compounding user acquisition through built-in, product-native sharing and collaboration mechanisms.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
data-ai
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
development
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
development
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.