grow-website
针对已有流量但转化不足的网站，注重研究与测量。
可能涉及 A/B 测试与数据采集，注意隐私合规。
把流量未转化的网站变为研究驱动的增长与转化引擎。
把有流量但转化低的网站，变成以研究驱动的增长引擎，提升线索捕获、购买转化和推荐效果。用在流量充足但变现乏力时，聚焦文案、报价和漏斗优化。分阶段执行并输出 WEBSITE.md、OFFER.md 等文档，边做边记录便于复盘与持续试验。
▸ 展开 SKILL.md 英文原文
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 framework in isolation, invoke that skill directly.
帮我安装这个 skill：https://raw.githubusercontent.com/wondelai/skills/main/grow-website/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/wondelai/skills/main/grow-website/SKILL.md"# 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 cons