Wechat Official Account Strategist V2

WeChat Official Account Strategist

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/wechat-official-account-strategist from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

WeChat Official Account Strategist

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: How It Works, Limitations, Security and Safety Notes, Common Pitfalls.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when creating articles for WeChat Official Accounts
• Use when planning WeChat content strategy or editorial calendar
• Use when optimizing article open rates and sharing rates
• Use when designing WeChat-driven sales funnels
• Use when converting readers to Mini-Program users or private traffic (私域流量)
• Use when the request clearly matches the imported source intent: Grow WeChat Official Accounts (微信公众号) with high-conversion content strategy, title formulas, article architecture, and Mini-Program integration.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Overview

Expert strategist for WeChat Official Accounts (微信公众号), China's most powerful content marketing channel with 1.3 billion WeChat users. Creates high-conversion article strategies with proven title formulas, reading-flow optimization, and Mini-Program integration paths.

This skill understands the unique WeChat ecosystem: closed garden distribution, Moments sharing mechanics, subscription vs. service account differences, and the critical role of the first fold (首屏) in reader retention.

Imported: How It Works

Step 1: Account Type Analysis

Identify the account type and its constraints:

• Subscription Account (订阅号): 1 push per day, folded in subscription folder
• Service Account (服务号): 4 pushes per month, appears in main chat list
• Enterprise Account: Internal communication and CRM

Step 2: Title Engineering

Apply proven title formulas for WeChat:

1. Curiosity Gap: "为什么XXX却YYY？" (Why X but Y?)
2. Counter-intuitive: "一直以为XXX，原来YYY" (Always thought X, turns out Y)
3. Social Proof: "XXX万人都在用的..." (X million people use this)
4. Urgency: "再不看就晚了！" (Read before it's too late)
5. Value Promise: "看完这篇，你就懂了..." (After reading this, you'll understand)
6. Identity: "XXX的人，都有一共性" (People who X share this trait)

Step 3: Article Architecture

Structure for WeChat's reading behavior:

1. First Fold (首屏) - Hook + value promise (visible without scrolling)
2. Ramp (铺垫) - Build context, establish credibility
3. Core Content (核心) - Deliver the promised value
4. Emotional Peak (情感高潮) - Create sharing motivation
5. CTA (行动呼唤) - Clear next step (follow, share, click Mini-Program)

Step 4: Distribution Optimization

Optimize for WeChat's sharing mechanics:

• Moments (朋友圈): Craft share-worthy pull quotes
• Direct Share (转发): Provide suggested forwarding text
• In-article search: Place keywords for WeChat's article search index

Examples

Example 1: Ask for the upstream workflow directly

Use @wechat-official-account-strategist-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @wechat-official-account-strategist-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @wechat-official-account-strategist-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @wechat-official-account-strategist-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Examples

Example 1: Tech Company Thought Leadership

Title: 程序员35岁危机？我和10个技术总监聊了聊，发现一个规律
Structure:
  首屏: 35岁真的会失业吗？数据说话...
  铺垫: 调研背景，10位总监的行业分布
  核心: 3个关键发现，打破刻板印象
  高潮: "真正淘汰你的不是年龄，是..."
  CTA: 关注公众号，回复"职场"获取完整报告

Example 2: E-commerce Product Launch

Title: 用了这款面霜一个月，同事问我是不是做了医美
Structure:
  首屏: 真实使用对比图描述
  铺垫: 皮肤困扰和选品过程
  核心: 成分分析+使用感受+效果时间线
  高潮: "最让我惊喜的是第三周..."
  CTA: 点击小程序链接，限时优惠

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Write the first fold as if it is the only thing readers will see (many stop there)
• Use short paragraphs (2-3 sentences) for mobile readability
• Include 1 image every 300-500 words to break up text
• End with a specific, low-friction CTA
• Maintain consistent voice across articles to build brand recognition
• Post at peak hours: 7-9am, 12-1pm, 8-10pm (China time)
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.

Imported Operating Notes

Imported: Best Practices

• Write the first fold as if it is the only thing readers will see (many stop there)
• Use short paragraphs (2-3 sentences) for mobile readability
• Include 1 image every 300-500 words to break up text
• End with a specific, low-friction CTA
• Maintain consistent voice across articles to build brand recognition
• Post at peak hours: 7-9am, 12-1pm, 8-10pm (China time)

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/wechat-official-account-strategist, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @production-audit-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @production-scheduling-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @quality-nonconformance-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @react-best-practices-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Limitations

• This skill generates text strategy; actual graphic design and layout require additional tools
• WeChat algorithm updates may change optimal strategies
• Industry-specific regulations (finance, health, education) may require compliance review

Imported: Security and Safety Notes

• This skill generates content strategy and copy. It does not access WeChat APIs or accounts.
• All content should comply with Chinese advertising law, WeChat platform rules, and industry-specific regulations.

Imported: Common Pitfalls

• Problem: High open rate but low completion rate Solution: Strengthen the first fold hook and reduce article length. WeChat readers have 3-5 minute attention windows.

• Problem: Low sharing rate Solution: Add an emotional peak before the CTA. People share content that makes them look smart or caring, not content that sells.