aios-writing-social
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseWriting Social — Orchestrator
社交媒体写作 — 协调器
Purpose
用途
Route social media requests to the correct platform skill. Handles multi-platform batches, content calendars, and requests where the platform is unspecified. Owns the shared quality gates, context loading, and compliance checks that all platform skills reference.
将社交媒体需求路由到对应的平台专属技能。支持处理多平台批量内容、内容日历，以及未指定发布平台的需求。负责所有平台技能都需遵循的通用质量门槛、上下文加载和合规检查逻辑。
When to Use
适用场景
- User asks to write social content without specifying a platform
- User asks for a content calendar or batch of social posts across platforms
- User asks for multi-platform content repurposing
- User says "write me a social post" or "create some content"
- 用户要求撰写社交媒体内容，但未指定发布平台
- 用户需求为跨平台的内容日历或批量社交媒体帖子
- 用户要求做多平台内容复用
- 用户表述为「帮我写一篇社交帖子」或「创作一些内容」
Do NOT Use For
不适用场景
- Platform-specific requests (use aios-writing-linkedin, aios-writing-twitter, etc.)
- Blog posts or long-form (use writing-blog)
- Email sequences (use writing-email)
- Ad copy for paid campaigns (use writing-ads)
- 指定平台的需求（请使用aios-writing-linkedin、aios-writing-twitter等对应技能）
- 博客文章或长内容创作（请使用writing-blog）
- 邮件序列创作（请使用writing-email）
- 付费活动的广告文案创作（请使用writing-ads）
Context Loading
上下文加载
Always Read (Before Every Post)
每次生成帖子前必须读取的文件
- — positioning, differentiators, personality
companies/claim-supply/brand.md - — who we write for
companies/claim-supply/audiences.md - — how we sound, words to use/avoid
companies/claim-supply/voice-and-tone.md - — pillars, platform rules, content mix
companies/claim-supply/content-strategy.md
- — 品牌定位、差异化优势、品牌个性
companies/claim-supply/brand.md - — 内容面向的受众群体
companies/claim-supply/audiences.md - — 品牌话术风格、推荐/禁用词汇
companies/claim-supply/voice-and-tone.md - — 内容支柱、平台规则、内容组合
companies/claim-supply/content-strategy.md
Read If Relevant
按需读取的相关文件
- — align with current objectives
companies/claim-supply/goals.md - — timely topics or blackout periods
companies/claim-supply/calendar.md - — if referencing a specific product/service
companies/claim-supply/products.md - — if writing as/about the founder
companies/claim-supply/founder.md - — if writing competitive content
companies/claim-supply/competitors.md
- — 对齐当前业务目标
companies/claim-supply/goals.md - — 时效性话题或停更期
companies/claim-supply/calendar.md - — 内容涉及特定产品/服务时读取
companies/claim-supply/products.md - — 以创始人名义创作或内容涉及创始人时读取
companies/claim-supply/founder.md - — 创作竞品相关内容时读取
companies/claim-supply/competitors.md
Always Reference
必须参考的文件
- — character limits, image sizes, posting rules
shared/platform-specs.md - — legal disclaimers, TCPA, ABA rules
shared/compliance-rules.md - — universal writing standards
shared/writing-rules.md
- — 字符限制、图片尺寸、发布规则
shared/platform-specs.md - — 法律免责声明、TCPA、ABA规则
shared/compliance-rules.md - — 通用写作标准
shared/writing-rules.md
Deduplication Check
去重检查
- Query Supabase — last 14 days
content_log - Query Supabase — what is already planned
publishing_queue
- 查询Supabase — 近14天数据
content_log - 查询Supabase — 已规划的待发布内容
publishing_queue
Process
执行流程
Step 1: Determine Platform
步骤1：确定发布平台
If user specifies a platform, delegate immediately to the platform skill:
- LinkedIn → use aios-writing-linkedin
- Twitter/X → use aios-writing-twitter
- Instagram → use aios-writing-instagram
- Facebook → use aios-writing-facebook
- Threads → use aios-writing-threads
If no platform specified, ask: "Which platform? LinkedIn, Twitter/X, Instagram, Facebook, or Threads? Or want me to create for multiple?"
If user says "all" or "multiple" or "batch":
- Generate one post per platform using platform-specific skills
- Cycle through content pillars: Pillar 1 (30%), Pillar 2 (25%), Pillar 3 (25%), Pillar 4 (20%)
- Alternate audiences across posts
如果用户指定了发布平台，立即委托给对应平台的技能处理：
- LinkedIn → 使用aios-writing-linkedin
- Twitter/X → 使用aios-writing-twitter
- Instagram → 使用aios-writing-instagram
- Facebook → 使用aios-writing-facebook
- Threads → 使用aios-writing-threads
如果未指定平台，询问用户：「您需要发布到哪个平台？LinkedIn、Twitter/X、Instagram、Facebook还是Threads？或者需要我为多个平台创作内容？」
如果用户回复「全部」、「多个」或「批量」：
- 调用对应平台的专属技能，为每个平台生成1篇帖子
- 按比例分配内容支柱：支柱1（30%）、支柱2（25%）、支柱3（25%）、支柱4（20%）
- 不同帖子面向不同受众，交替覆盖
Step 2: Batch / Calendar Mode
步骤2：批量/内容日历模式
For content calendar requests:
- Ask for timeframe (1 week, 2 weeks, 1 month)
- Distribute across platforms per content-strategy.md allocation
- Balance content pillars and audiences
- Output as a table with date, platform, pillar, audience, topic
针对内容日历的需求：
- 询问用户需要的时间范围（1周、2周、1个月）
- 按照content-strategy.md中的分配规则，在各个平台之间分配内容
- 平衡内容支柱和受众覆盖
- 输出为表格，包含日期、平台、支柱、受众、主题
Step 3: Apply Shared Quality Gates
步骤3：应用通用质量门槛
Every post from every platform skill must pass these checks before output:
所有平台技能生成的帖子在输出前必须通过以下检查：
Voice Check
风格检查
- Does this sound like the brand? Compare against voice-and-tone.md examples
- Are any words to avoid present? Remove them
- Does the post challenge the industry/system, not the reader?
- Is the CTA an invitation, not a command?
- 内容是否符合品牌调性？和voice-and-tone.md中的示例对比确认
- 是否存在禁用词汇？如有则删除
- 帖子是否是针对行业/体系提出质疑，而非针对读者？
- CTA是否是邀请性质，而非命令性质？
Audience Check
受众检查
- Written for the target audience, not a general audience?
- Addresses their pain points from audiences.md?
- Would this audience find it valuable or shareable?
- 内容是为目标受众撰写，而非面向泛受众？
- 是否回应了audiences.md中列出的受众痛点？
- 目标受众是否会觉得内容有价值或愿意分享？
Strategy Check
策略检查
- Aligns with a content pillar from content-strategy.md?
- Content mix balance maintained?
- Clear CTA or takeaway?
- 是否符合content-strategy.md中列出的某一条内容支柱？
- 是否维持了内容组合的平衡？
- 是否有明确的CTA或核心收获？
Data Integrity Check
数据准确性检查
- Every statistic sourced or qualified
- No unsourced percentage or multiplier claims stated as fact
- Proprietary data labeled as such
- 所有统计数据都有来源或限定说明
- 没有将无来源的百分比或乘数主张作为事实陈述
- 专有数据已做对应标注
Compliance Check
合规检查
- No false or misleading claims
- No guaranteed outcomes or settlement amounts
- Appropriate disclaimers for legal services
- No real lead/client data exposed
- Compliant with ABA Model Rules
- 无虚假或误导性声明
- 无保证结果或和解金额的表述
- 法律服务相关内容带有适当的免责声明
- 未泄露真实的线索/客户数据
- 符合ABA Model Rules要求
Writing Quality Check
写作质量检查
- Strong opening hook?
- Every sentence earns its place?
- Active voice? Specific over vague? No filler?
- 开头是否有足够吸引人的钩子？
- 每一句话都有存在的意义？
- 是否使用主动语态？表述具体而非模糊？无冗余内容？
Output Format
输出格式
Delegates to platform-specific skill output formats. For multi-platform batches, output each post with its platform header.
委托对应平台的专属技能使用其输出格式。针对多平台批量内容，每个帖子前标注对应平台的标题。
References
参考文件
- — proven opening hooks
references/hook-patterns.md - — platform-specific structure templates
references/post-templates.md - — character limits, image sizes
shared/platform-specs.md - — legal and regulatory rules
shared/compliance-rules.md - — universal writing standards
shared/writing-rules.md
- — 经过验证的开头钩子模板
references/hook-patterns.md - — 各平台专属的内容结构模板
references/post-templates.md - — 字符限制、图片尺寸
shared/platform-specs.md - — 法律和监管规则
shared/compliance-rules.md - — 通用写作标准
shared/writing-rules.md