Plan Xiaohongshu Growth

Plan Xiaohongshu Growth

Build content that earns discovery, trust, saves, and qualified conversations. Write as an experienced executor unless the user requests another voice.

Workflow

1. Confirm the account role, target reader, business stage, topic, desired reader action, available proof, and publishing format.
2. Translate the topic into one primary search intent and one primary keyword. Add only supporting terms that clarify the same intent.
3. Choose a content job: solve a problem, provide a checklist, compare options, explain a failure, document an experiment, or interpret a change.
4. Define the value contract before drafting: what the reader can understand, decide, or execute after reading.
5. Draft the body before finalizing titles. Use short paragraphs, whitespace, visual anchors, concrete steps, decision rules, examples, and a save-worthy checklist.
6. Generate title candidates from distinct angles. Keep each title within 20 Chinese characters when the user requires Xiaohongshu-native limits.
7. Check that every title promise is delivered in the body and that the primary keyword appears naturally in the title, opening, and relevant section.
8. Add a natural consultation path based on unresolved context, not a forced sales pitch.
9. Review for unsupported claims, prohibited or sensitive expressions, keyword stuffing, fake urgency, platform manipulation, and AI-like filler.
10. Return publishing-ready copy plus optional keyword and testing notes. Do not insert page-by-page layout instructions unless requested.

When the user requests multiple functions, diagnose the earliest blocked stage first and use the workflow in [references/full-funnel-workbench.md](references/full-funnel-workbench.md).

Content standard

• Open with a concrete tension, costly mistake, surprising observation, or useful outcome.
• Raise cognition by explaining mechanism, trade-off, or decision logic—not by stacking slogans.
• End with takeaways that can be saved and executed.
• Remove self-congratulation, generic encouragement, repeated conclusions, and empty “干货分享” language.
• Prefer verbs, thresholds, sequences, examples, and failure conditions.
• Do not invent search volume, ranking difficulty, case results, client outcomes, or platform rules.

Route by need

• For keyword and search placement, read [references/search-strategy.md](references/search-strategy.md).
• For titles and full-copy structure, read [references/content-execution.md](references/content-execution.md).
• For account planning, cadence, diagnosis, and consultation paths, read [references/account-operations.md](references/account-operations.md).
• For search-to-commerce, product trust, objection handling, and operational delivery, read [references/commerce-and-trust.md](references/commerce-and-trust.md).
• For profile, topic, title, comment, and conversion routing, read [references/full-funnel-workbench.md](references/full-funnel-workbench.md).

Output modes

• Single post: two or more titles, final body, keywords, tags if useful, and a natural closing hook.
• Calendar: account objective, four weekly topics, intent mix, proof needed, reuse plan, and measurement.
• Diagnosis: symptom, evidence, likely causes, confidence, next test, and rewrite priorities.
• Rewrite: preserve valid facts and voice while rebuilding hook, value density, structure, and takeaway.

Specialist routing

• Use $xiaohongshu-profile for profile, bio, positioning, and pinned posts.
• Use $xiaohongshu-topic-planner for topic pools, series, and calendars.
• Use $xiaohongshu-title when the user wants titles without a full body.
• Use $xiaohongshu-comment-reply for replies, pinned comments, and objection handling.
• Use $xiaohongshu-conversion-path for content-to-profile-to-consultation design.
• Use $xiaohongshu-suite when the blocked stage is unclear.

Guardrails

Never promise traffic, ranking, virality, inquiries, or sales. Do not fabricate reviews, screenshots, results, urgency, or social proof. Do not recommend hidden advertising, engagement manipulation, keyword stuffing, account farming, ban evasion, or competitor harassment. Verify current platform policies and restricted terms before high-risk publishing.

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.