SkillAgentSearch skills...

grow-app

Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts.

Install / Use

npx skills add wondelai/skills --skill grow-app

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of grow-app

grow-app scores 87/100 on our quality scale, 394th of 604 Data & Analytics skills we index.

Its SKILL.md is 22 KB long, well organised into 17 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so grow-app is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

grow-app compared with similar skills

All 4 of these similar skills score higher than grow-app; compare them before choosing.

SkillScoreStarsUpdatedFormat
grow-app (this skill)by wondelai872.2k2mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install grow-app?
Run npx skills add wondelai/skills --skill grow-app. The install tabs above show the steps for each supported agent.
Which AI agents does grow-app work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is grow-app safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is grow-app still maintained?
The repository was last updated about 2 months ago, so grow-app is actively maintained.

name: grow-app description: 'Guided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says ''users sign up then disappear''. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.2"

Grow an App

Your app has users who sign up and then quietly disappear β€” cohorts decay, daily actives are flat, the activation funnel leaks where it always has, and nothing looks obviously broken. This journey seals the bucket: it turns first-time users into activated, then habitual, then would-miss-it users across eight interactive phases. The agent asks before every decision and records the outcome in docs/, so the work resumes across sessions instead of restarting. Growth here is an engineering and design problem, not a bigger ad budget.

Core Principle

Fix the leaky bucket before pouring in acquisition: habit, activation, and retention come before any growth spend. This skill sequences the eight phases, asks every decision question, and records each choice in docs/. The constituent skills carry the method β€” invoke them rather than improvising their frameworks.

Journey Map

| Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | hooked-ux | Why do users come back without us paying? | Extends docs/PRODUCT.md | | 2 | improve-retention | Why don't new users reach the loop? | Extends docs/PRODUCT.md | | 3 | continuous-discovery | What do our own users actually need? | Extends docs/PRODUCT.md + docs/CUSTOMER.md | | 4 | lean-ux | Which bet is worth building? | Extends docs/EXPERIMENTS.md | | 5 | inspired-product | Is the team building the right things? | Extends docs/PRODUCT.md | | 6 | lean-analytics | Which single number tells the truth? | Creates docs/METRICS.md β€” sets the Rule 8 bar | | 7 | microinteractions | Does it feel alive in the hand? | Extends docs/DESIGN.md | | 8 | drive-motivation | Will engagement last, or curdle? | Extends docs/PRODUCT.md |

Phases 1-2 seal the loop and the funnel; 3-5 steer with evidence; 6 is the instrument panel; 7-8 are the finish and the ethical backstop. Take the lean-analytics baseline (Phase 6) early β€” before the Phase 1-2 fixes land β€” so every change is read against a pre-change number, then keep updating it. Habit formation is slow: read Phase 1's success against the "5% rule" (a habit has formed when 5%+ of users return unprompted), not a single cohort.

Operating Rules

  1. Resume first. Before anything else, read docs/GROW-APP-PLAN.md and every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted.
  2. Intake on first run only. No tracker: run the Intake below, then create docs/GROW-APP-PLAN.md with every phase statused pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan.
  3. Phase entry. Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defer β€” phases marked GATE may be deferred, never skipped. Mark the phase in-progress on proceed. Done when the user chose.
  4. Skill invocation and fallback. Load the phase's skill and use it: each phase's Invoke line names the skill by slug β€” use that skill to run the phase. If it is not available, offer: npx skills add wondelai/skills/<slug> --global. If the user declines, run the phase from its Brief β€” the minimum viable method. State which mode you are in.
  5. In-phase decisions. Ask every question under "Decide with the user" β€” with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.
  6. Phase exit. Present the draft artifact content for sign-off before writing. On approval: write or extend the docs/ files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows done.
  7. Artifact discipline. Read before writing; create a file only if missing, otherwise extend β€” add or update your sections, preserve everyone else's. Files are UPPERCASE in docs/. Every recommendation lands as a checkbox or a table row with owner and priority. See references/artifact-templates.md when creating a docs/ file for the first time β€” create it from the full skeleton (all section headings), then fill the sections your phase names.
  8. Retention before acquisition. Acquisition-oriented phases β€” the optional cold-start-problem, contagious, and crossing-the-chasm, plus any paid-growth work β€” stay locked while activation and retention sit below the bar set at intake; unlock them only once the cohort curve clears that bar. Every habit loop and reward must pass the Manipulation Matrix: build only what the maker would use and honestly believes materially improves users. When a tactic needs manufactured anxiety or loss aversion, replace it with one built on real value.

Intake

Run only on first start (no tracker). Ask:

  1. What does the app do, and what core action does a retained user repeat? (defines the Hook loop and the OMTM)
  2. What are the current retention numbers β€” day-1/7/30 or week-4 cohorts? (sets the Rule 8 acquisition bar; feeds lean-analytics)
  3. Where does the activation funnel leak, and what is the first-run flow? (gates improve-retention)
  4. Solo/small team or a full product trio (PM, designer, engineer)? (scales continuous-discovery and inspired-product)
  5. Is the app a network/marketplace product, and do engaged users fail to convert to revenue? (flags optional cold-start-problem / monetizing-innovation)
  6. What analytics and instrumentation exist today? (gates lean-analytics and every experiment)
  7. Is retention broken by UX or performance rather than missing engagement? (if yes, route to improve-app first)

Skip heuristics: skip Phase 5 for a solo founder with no team to realign; defer Phase 7 until the loop and activation clear their bars; run Phase 3's cadence degraded if no user access exists yet. Then create the tracker from references/artifact-templates.md with every phase statused, and confirm the plan.

Done when docs/GROW-APP-PLAN.md exists with every phase statused and the user has confirmed the plan.

Phases

Phase 1 β€” Design the habit loop that brings users back (hooked-ux)

Purpose: Build the engine of return β€” a Hook loop strong enough that users come back on an internal trigger, not a paid notification.

Brief (fallback): The Hook Model runs Trigger β†’ Action β†’ Variable Reward β†’ Investment. Migrate external triggers (push, email) to internal ones (an emotion β€” boredom, FOMO, anxiety). Make the action trivially simple. Make the reward variable across tribe/hunt/self. Sequence investment after the reward so it raises switching cost and loads the next trigger. A loop with one weak phase stalls, not half-works.

Invoke: Use the hooked-ux skill with the core loop and how daily-active users return today. Ask it to (a) map the loop across all four phases, rate each 0-10, and name the weakest, and (b) design honest variable-reward concepts powered by data you already have, each checked against the Manipulation Matrix.

Decide with the user:

  • Which internal trigger (emotion) should pull users back β€” confirm one.
  • Which single phase is weakest and gets the highest-leverage fix now β€” or defer if the loop is already forming (5%+ unprompted return).
  • Which reward type to strengthen β€” tribe (social), hunt (resources), or self (mastery) β€” rejecting any concept that fails the Manipulation Matrix.

Artifact: Extend docs/PRODUCT.md ## Hook Model (trigger β†’ action β†’ variable reward β†’ investment; weakest phase named). Update the tracker.

Done when: PRODUCT.md names the internal trigger and all four phases, the weakest phase and its fix are recorded, onboarding is re-engineered so a new user completes one full Hook cycle in the first session, and the user picked the fix to ship.

Phase 2 β€” Fix activation by making the first action almost effortless (improve-retention)

Purpose: Get new users to the loop by making the first meaningful action almost effortless.

Brief (fallback): B=MAP β€” behavior fires only when Motivation, Ability, and a Prompt converge. Motivation is unreliable; raise Ability instead. Simplicity is capped by the scarcest of six resources: time, money, physical effort, mental effort, social deviance, non-routineness. Shrink the target to a Starter Step that delivers value in under 30s, anchor it to an existing routine, and celebrate the win immediately.

Invoke: Use the improve-retention skill with the real activation flow step by step and the day-1/7/30 drop-offs. Ask for a B=MAP friction audit rating all six Ability-Chain factors, the scarcest resource named, a Starter Step redesign, and event-based prompt rules.

Decide with the user:

  • Which is the scarcest Ability resource for the first action β€” fix that link first, not the obvious one.
  • The Starter Step (tiniest valuable action) and its celebration moment.
  • Which time-based prompts convert to event-based, dropping any that fail "would I appreciate this now?".

Artifact: Extend docs/PRODUCT.md ## Activation & Retention Plan (friction/moment | fix | owner | status). Update the tracker.

Done when: the scarcest resource is named, the Starter Step, celebration, and prompt changes are rows with owners, each day-1/7/30 drop-off is mapped to its likely B=MAP failure, and the user approved the fix list.

Phase 3 β€” Run continuous discovery so you stop guessing (continuous-discovery)

Purpose: Replace generic best-practice with a weekly stream of evidence about your own users.

Brief (fallback): Aim for at least one customer touchpoint per week. Build an Opportunity Solution Tree: outcome at the top β†’ customer opportunities (needs/pains in the customer's words) β†’ candidate solutions/experiments. Never leap outcomeβ†’solution. Interviews are story-based ("tell me about the last time you…"), captured as one-page snapshots. Test the riskiest leap-of-faith assumption first, cheaply.

Invoke: Use the continuous-discovery skill with the retention outcome and known churn patterns. Ask for an Opportunity Solution Tree, a current-state experience map of how churned users try to succeed today, a weekly story-based interview snapshot template, and an assumption map for the next planned feature.

Decide with the user:

  • The single outcome at the top of the tree.
  • Which two or three opportunities to pursue first.
  • The weekly cadence and recruitment mechanism the team can actually sustain β€” set it now or run degraded.
  • The riskiest leap-of-faith assumption inside the next feature (desirability, viability, feasibility, usability) and the cheapest test for it.

Artifact: Extend docs/PRODUCT.md ## Opportunity Solution Tree Notes, ## Outcome Roadmap (outcome/problem | job served | priority | status), and ## Discovery Cadence; extend docs/CUSTOMER.md ## Interview Evidence (date | who |

Truncated for display β€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryData
Updated2mo ago
Forks228

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
grow-app β€” Universal Skill: Install & Safety Check | SkillAgent