Skill detail
grow-website
Guided journey from a website with traffic it under-converts to a research-driven growth engine, orchestrating eight skills across CRO, messaging, offers, and referrals.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: grow-website description: 'Guided journey from a website with traffic it under-converts to a research-driven growth engine that captures more leads, persuades more buyers, sells a sharper offer, and earns referrals. Orchestrates eight skills phase by phase - cro-methodology, scorecard-marketing, storybrand-messaging, made-to-stick, influence-psychology, hundred-million-offers, contagious, one-page-marketing - asking the user questions at every decision point and recording results in the project docs/ folder (WEBSITE.md, OFFER.md, MARKETING.md, GROW-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to raise conversion on a site that already has traffic, capture more leads, sharpen a weak offer, add referral loops, or says ''my site gets visitors but nobody buys''. If a broken funnel or usability friction is the real blocker, run improve-website first; if there is no site yet, use create-website; for one leaking flow, conversion-optimization. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.2" --- # Grow a Website Take a site that already has traffic and under-monetizes it, and turn it into a research-driven growth engine: more leads captured, more buyers persuaded, a sharper offer, and visitors who bring more visitors. This journey runs eight phases — the agent asks before it decides at every fork, and all state lives in `docs/` so you can stop and resume across sessions. It sequences the work; it does not redesign the site on a hunch. ## Core Principle **Most traffic problems are conversion problems in costume: capture and convert the visitors you have before buying more.** This skill sequences the phases, asks the decision questions, and records every choice in `docs/`. The constituent skills carry the method — invoke them rather than improvising their frameworks. Research comes before optimization, and the offer comes before the page polish, always. ## Journey Map | Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1. Discover why visitors leave | cro-methodology | Why do visitors not convert, and what is worth testing? | Extends docs/WEBSITE.md, docs/METRICS.md, docs/EXPERIMENTS.md | | 2. Capture the not-ready 97% | scorecard-marketing | How do we keep the leads who aren't ready to buy? | Extends docs/WEBSITE.md, docs/MARKETING.md | | 3. Clarify the message | storybrand-messaging | Can a stranger tell what we do in five seconds? | Extends docs/POSITIONING.md | | 4. Make the message stick | made-to-stick | Will they remember it when they are ready to buy? | Extends docs/POSITIONING.md, docs/WEBSITE.md | | 5. Add proof and triggers | influence-psychology | Why should they believe us, and act now? | Extends docs/WEBSITE.md | | 6. Rebuild the offer | hundred-million-offers | Is the thing we sell irresistible? | Extends docs/OFFER.md, docs/EXPERIMENTS.md | | 7. Engineer shareability | contagious | Will visitors bring us more visitors? | Extends docs/MARKETING.md, docs/WEBSITE.md | | 8. Connect the lifecycle | one-page-marketing | Do the wins link into one compounding engine? | Extends docs/MARKETING.md, docs/METRICS.md | ## Operating Rules 1. **Resume first.** Before anything else, read `docs/GROW-WEBSITE-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-WEBSITE-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 GARead the full source on GitHub (opens external page)