Launch Content Account

Launch Content Account

Treat launch as a learning system that produces a clear audience promise, comparable content samples, owned knowledge assets, and qualified business signals. Do not optimize for follower count alone.

Workflow

1. Confirm business objective, platform, target audience, account role, offer or future value, available proof, production capacity, time horizon, and compliance constraints.
2. Define one audience promise: who the account helps, which recurring problem it addresses, what evidence supports it, and what it will not cover.
3. Audit or build the profile: identity, description, pinned content, recurring series, visible proof, and permitted next action must tell one coherent story.
4. Create three to five content pillars from customer questions, work processes, cases, mistakes, tools, research, objections, and product use—not from generic trend lists alone.
5. Give every content item one job: discovery, search, trust, proof, conversation, conversion, or retention.
6. Write a brief before production: audience state, viewing or reading reason, promise, evidence, structure, format, CTA, and risk check.
7. Run a small comparable sample. Keep audience and core promise stable while changing only one or two variables such as topic, hook, format, proof, or series device.
8. Review by failure stage: eligibility and exposure → open or hold → completion → useful interaction → profile visit → follow → qualified conversation → business outcome.
9. Read qualitative evidence: questions, objections, repeated language, reasons for sharing, and reasons for not acting. Do not reduce comments to volume.
10. Turn useful replies and high-signal items into durable assets: follow-up posts, series, articles, templates, FAQs, cases, or product improvements.
11. Set the next experiment, owner, review date, stop rule, and scale rule. Use a 30/60/90-day roadmap only after the first evidence cycle.

Platform routing

• For platform selection and the shared launch system, read [references/core-launch-system.md](references/core-launch-system.md).
• For WeChat Official Accounts, read [references/wechat-official-account.md](references/wechat-official-account.md).
• For Douyin and WeChat Channels, read [references/short-video-accounts.md](references/short-video-accounts.md).
• For X/Twitter, read [references/x-twitter.md](references/x-twitter.md).
• For Xiaohongshu, use $plan-xiaohongshu-growth and read its account-operation references.
• For public benchmark analysis, use $distill-creator-playbook.
• For full copy creation, use $create-marketing-content.

Output modes

• Launch plan: promise, profile, pillars, source-material plan, first sample, metrics, review cadence, and risk register.
• Account audit: observed symptom, evidence, likely causes, confidence, priority repair, and next test.
• Content system: pillar map, topic backlog, brief template, production workflow, reuse map, and calendar.
• Experiment: controlled variables, sample items, early and business signals, review date, stop/continue rule.
• Weekly review: results by stage, qualitative learning, reusable assets, failed assumptions, and next actions.

Guardrails

Never promise followers, views, revenue, virality, recommendation, or monetization eligibility. Do not prescribe universal posting frequency, hook duration, content ratios, account-warming behavior, engagement thresholds, or algorithm weights. Do not use bought or coordinated engagement, hidden promotion, spam replies, copied content, ban evasion, undisclosed sponsorship, fabricated identity, or manipulative private-domain distribution. Verify current official platform rules before advising on AI labels, advertising, commerce, live streaming, external links, private messages, monetization, or sensitive categories.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: ShenyuanNext
• Source: ShenyuanNext/wepr-growth-skills
• License: MIT

Install and usage instructions live in the source repository linked above.