AIPDD Social Media Content Operations Master

What problem it solves

Multi-platform operations often scatter topic planning, copywriting, layout, rendering, publishing, comments, and analytics across separate tools. That creates fragmented workflows, inconsistent platform rules, weak pre-publish compliance checks, and data reviews that confuse correlation with causation. This skill connects Xiaohongshu, WeChat Official Accounts, Douyin short video, and private-domain operations into an executable pipeline focused on publishable output rather than copy-only drafts.

How it works

• Strategy and content: It first clarifies platforms, goals, audiences, assets, and deliverables, then generates platform-specific structures: Xiaohongshu titles and short-paragraph notes with hashtags; WeChat long-form articles with conclusion-first, supporting points, cases, and CTA; Douyin shot-by-shot scripts with a strong 3-second hook and conversion actions; private-domain content split into public-domain leads, community value, and direct-message conversion.
• WeChat production: It routes to aipdd-gzh for normalizing Markdown, .docx, or PDF input, assembling WeChat HTML from a theme component library, validating with validate_gzh_html.py, and handling imitation writing, AI-tone reduction, drafts, and publishing through official APIs.
• Xiaohongshu automation: It routes to xiaohongshu-auto to render 1080×1440 covers and multi-page cards with render_xhs.py, then checks external links, extreme claims, QR codes, and other risks with content_filter.py. It supports CDP/HTTP channels, draft verification, comment interaction, and platform-change self-healing.
• Monitoring and review: It combines wechat-mp-cn for article, competitor, and public-opinion tracking, then reviews core metrics for Xiaohongshu, WeChat, and Douyin, separating observed data, inferences, and the next A/B test actions.

Boundaries

It fits operators with a defined account positioning who need batch-ready publishing assets, but it does not promise viral growth or follower gains. Automated publishing is high-risk and should require explicit authorization; drafts may be stored only in browser local cache, so verification matters. Competitor analysis should borrow structure, not copy text or images; data access should use lawful APIs or authorized channels.