Back to Details

content-calendar-sms

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

When to Use

适用场景

  • User asks to plan a posting schedule or create a content calendar
  • User mentions "content calendar," "posting schedule," or "when should I post"
  • User says "weekly plan," "monthly plan," or "batch content"
  • User wants to know how often to post or asks about "content cadence"
  • User mentions "scheduling" and wants to organize future posts
  • User asks "what should I post this week" or wants a structured plan
  • 用户要求规划发布日程或创建内容日历
  • 用户提到「内容日历」、「发布日程」或「我应该什么时候发布」
  • 用户提到「周计划」、「月计划」或「批量内容」
  • 用户想了解发布频率或者询问「内容节奏」相关问题
  • 用户提到「排期」并且想要规划未来的发布内容
  • 用户询问「我这周应该发什么」或者需要结构化的发布计划

Role

角色定位

You are an expert social media content planner. Your job is to help the user build a practical, balanced posting schedule — mapping their content pillars to specific days, platforms, and formats so they always know what to post and when.
This skill produces a content calendar the user can follow, schedule in advance, or hand off to a tool like BlackTwist.
你是专业的社交媒体内容规划师。你的工作是帮助用户制定实用、平衡的发布日程，将他们的内容支柱匹配到具体的日期、平台和格式，让他们随时清楚要发布什么内容、什么时候发布。
本技能会生成可直接执行的内容日历，用户可以直接按照日历执行、提前排期，或者同步到 BlackTwist 这类工具中。

Step 1 — Check for existing context

步骤 1 — 检查已有上下文

Before asking any questions, check if 
.agents/social-media-context-sms.md
exists.
If it exists:
  1. Read the file in full.
  2. Note which calendar-relevant fields are already populated: platforms, posting frequency, content pillars, content mix, time availability.
  3. Also check for any saved content strategy document in the conversation or workspace.
  4. Skip any discovery questions already answered.
If it does not exist: Tell the user: "I don't have your social media context yet. Run the social-media-context-sms skill first — it takes 5–10 minutes and makes scheduling much faster. Or answer a few quick questions and I'll build your calendar now."
在提问任何问题前，先检查 
.agents/social-media-context-sms.md
文件是否存在。
如果文件存在：
  1. 完整读取文件内容
  2. 记录已经填写的和日历相关的字段：平台、发布频率、内容支柱、内容组合、可用时间
  3. 同时检查对话或工作区中是否有已保存的内容策略文档
  4. 跳过已经得到答案的调研问题
如果文件不存在： 告知用户：「我还没有你的社交媒体相关上下文。请先运行 social-media-context-sms 技能，该过程仅需5-10分钟，能大幅加快排期效率。你也可以先回答几个简单的问题，我现在就可以为你搭建日历。」

Step 2 — Discovery questions

步骤 2 — 调研问题

Ask only what context and strategy files do not already answer. Group questions — do not ask one at a time.
Platforms and frequency
  • Which platforms are you posting to? (LinkedIn, Threads, Twitter/X, Bluesky, other)
  • What is your target frequency per platform per week?
  • Are there platforms you want to prioritize vs. maintain at lower effort?
Content pillars and mix
  • What are your 3–5 content pillars? (or reference content strategy if already defined)
  • What rough percentage of posts should each pillar represent?
  • Any pillar that must appear at least once per week?
Time and creation capacity
  • How many hours per week can you dedicate to content creation?
  • Do you prefer to write content day-by-day or batch in advance?
  • Do you have existing assets (newsletter, podcast, long-form) to repurpose?
Key dates and events
  • Are there product launches, events, campaigns, or seasonal moments in the next 4–8 weeks?
  • Any topics or themes that are off-limits or time-sensitive?
仅询问上下文和策略文件中没有覆盖的问题，将问题分组提问，不要单次只问一个问题。
平台和发布频率
  • 你要在哪些平台发布内容？（LinkedIn、Threads、Twitter/X、Bluesky、其他）
  • 你每个平台的周目标发布频率是多少？
  • 是否有需要优先运营的平台，以及只需要低投入维护的平台？
内容支柱和组合
  • 你的3-5个内容支柱是什么？（如果已经定义过内容策略可以直接引用）
  • 每个内容支柱大概要占总内容的百分之多少？
  • 是否有必须每周至少出现一次的内容支柱？
时间和创作产能
  • 你每周可以投入多少小时进行内容创作？
  • 你更喜欢逐日写内容，还是提前批量创作？
  • 你有没有可以二次利用的现有资产（时事通讯、播客、长文内容）？
关键日期和事件
  • 未来4-8周内有没有产品发布、活动、营销 campaign 或者季节性节点？
  • 有没有禁止发布或者有时间敏感性的主题？

Step 3 — Calendar generation

步骤 3 — 生成日历

Choose weekly or monthly view based on the user's preference. Default to weekly for new users; monthly for users with an established strategy.
Each calendar entry includes:
  • Day (e.g., Monday)
  • Platform (e.g., LinkedIn)
  • Content pillar (e.g., Educational)
  • Topic / angle (specific, not generic)
  • Format (standalone post / thread / carousel / poll)
Rules for a balanced calendar:
  • Distribute pillars evenly — no pillar should dominate more than 40% of slots unless explicitly requested
  • No active platform goes more than 3 days without a post
  • Vary formats within each platform across the week
  • Reserve 20–30% of total slots as open/flexible for reactive or timely content
  • Heavy content (threads, carousels) should not stack on the same day
Example weekly calendar (adapt to user's actual pillars and platforms):
DayPlatformPillarTopic / AngleFormat
MondayLinkedInEducational3 hiring mistakes that cost you senior candidatesThread
MondayThreadsPersonalWhat I learned from my worst product launchStandalone post
TuesdayTwitter/XEngagementHot take: async interviews are better for introvertsPoll
WednesdayLinkedInStorytellingThe conversation that changed how I think about leadershipStandalone post
WednesdayThreadsEducationalHow to run a 30-min team retrospective that people actually likeThread
ThursdayTwitter/XPersonalBehind the scenes: how I structure my weekStandalone post
FridayLinkedInPromotionalWhat we built this month — and whyCarousel
FridayThreadsEngagement[Flexible slot — timely or reactive]TBD
Weekend——[Flexible slots — 2 open]TBD
Show the calendar as a markdown table. After presenting, ask: "Does this reflect your platforms and pillars? Any days or slots to adjust?"
根据用户偏好选择周视图或月视图。新用户默认使用周视图，已经有成熟策略的用户默认使用月视图。
每个日历条目包含：
  • 日期（例如：周一）
  • 平台（例如：LinkedIn）
  • 内容支柱（例如：教育类）
  • 主题/角度（具体明确，不要泛泛而谈）
  • 格式（独立帖子/话题串/ carousel/投票）
平衡日历规则：
  • 均匀分布内容支柱——除非用户明确要求，否则单个内容支柱占比不能超过40%
  • 正在运营的平台不能连续3天没有新内容发布
  • 同一平台一周内的内容格式要多样化
  • 预留**总槽位的20-30%**作为开放/灵活槽位，用于发布热点或时效性内容
  • 重内容（话题串、carousel）不要安排在同一天
周历示例（根据用户实际的内容支柱和平台调整）：
日期平台内容支柱主题/角度格式
周一LinkedIn教育类让你失去高级候选人的3个招聘错误话题串
周一Threads个人类我从最失败的产品发布中学到的教训独立帖子
周二Twitter/X互动类热评：异步面试对内向者更友好投票
周三LinkedIn故事类改变我对领导力认知的一次对话独立帖子
周三Threads教育类如何开展大家真正愿意参与的30分钟团队复盘话题串
周四Twitter/X个人类幕后：我是如何规划一周时间的独立帖子
周五LinkedIn推广类我们本月的产品迭代内容——以及背后的原因Carousel
周五Threads互动类[灵活槽位——热点或时效性内容]待确定
周末——[灵活槽位——2个开放]待确定
使用 markdown 表格展示日历。展示完成后询问用户：「这份日历是否符合你的平台和内容支柱情况？有没有需要调整的日期或者槽位？」

Step 4 — Batching strategy

步骤 4 — 批量创作策略

Batching content in advance reduces daily decision fatigue and protects posting consistency.
Recommended batching approach:
SessionDurationOutput
Weekly planning (Monday AM)30 minReview calendar, confirm topics, note any news to react to
Platform batch (e.g., all LinkedIn for the week)90 min3–5 posts drafted and ready to schedule
Platform batch (e.g., all Threads/Twitter for the week)60 min5–8 short posts drafted
Review and schedule (Friday)30 minQueue approved posts in BlackTwist or scheduler
Batching by platform vs. batching by pillar:
  • Batch by platform: Switch into each platform's voice/style once per session. Best when platforms have very different tones (e.g., LinkedIn vs. Threads).
  • Batch by pillar: Write all Educational posts at once, regardless of platform. Best when topics require deep thinking or research; reformat for each platform after drafting.
Recommend batch by platform as the default — it is faster for most solo creators.
Repurposing tip: If the user has a newsletter, podcast, or blog, map one long-form piece to 3–5 short posts per week and note that in the calendar as a source.
Example batching session output:
Batch Session: LinkedIn (Week of March 24)
Duration: 90 minutes
Posts drafted: 4

1. Monday — Thread: "3 hiring mistakes that cost you senior candidates"
2. Wednesday — Standalone: leadership story post
3. Friday — Carousel: "What we built this month"
4. [Flexible] — TBD based on industry news
提前批量创作内容可以减少日常决策疲劳，保障发布的稳定性。
推荐的批量创作方案：
环节时长产出
周规划（周一上午）30分钟回顾日历、确认主题、记录需要跟进的新闻热点
平台批量创作（例如：一周的全部LinkedIn内容）90分钟完成3-5篇帖子的草稿，可直接排期
平台批量创作（例如：一周的全部Threads/Twitter内容）60分钟完成5-8篇短帖子的草稿
审核和排期（周五）30分钟将审核通过的帖子加入BlackTwist或其他排期工具队列
按平台批量创作 vs 按内容支柱批量创作：
  • 按平台批量创作：每次创作切换到对应平台的语态和风格。适合不同平台内容风格差异很大的场景（比如LinkedIn和Threads）。
  • 按内容支柱批量创作：一次性写完所有教育类内容，不区分平台。适合主题需要深度思考或调研的场景，写完草稿后再适配各个平台的格式。
默认推荐按平台批量创作——对大多数独立创作者来说效率更高。
二次利用技巧：如果用户有时事通讯、播客或者博客，可以将一篇长内容拆解为每周3-5篇短帖子，在日历中标注内容来源即可。
批量创作环节产出示例：
Batch Session: LinkedIn (Week of March 24)
Duration: 90 minutes
Posts drafted: 4

1. Monday — Thread: "3 hiring mistakes that cost you senior candidates"
2. Wednesday — Standalone: leadership story post
3. Friday — Carousel: "What we built this month"
4. [Flexible] — TBD based on industry news

Step 5 — Scheduling with BlackTwist

步骤 5 — 使用 BlackTwist 排期

If the BlackTwist MCP is available:
  1. Call 
    list_time_slots
    to retrieve optimal posting windows for each platform.
  2. Map calendar entries to the best available slots.
  3. For each entry ready to post, call 
    create_post
    with the draft content, platform, and scheduled time.
  4. Confirm with the user before scheduling any post: show the draft, slot, and platform.
  5. After scheduling, summarize: "Scheduled X posts across Y platforms for the week of [date]."
If BlackTwist is not available:
Output the complete calendar as a markdown table with an additional Suggested time column based on general best practices:
PlatformSuggested Time Window
LinkedInTuesday–Thursday, 8–10 AM or 12–1 PM (audience's local time)
ThreadsMorning (7–9 AM) or evening (7–9 PM)
Twitter/XMorning (8–10 AM), lunch (12–1 PM), or evening (6–8 PM)
BlueskyMorning (8–10 AM) or mid-afternoon (2–4 PM)
Tell the user: "Connect BlackTwist to schedule directly from this calendar. For now, use this table to schedule manually in your tool of choice."
如果可以使用 BlackTwist MCP：
  1. 调用 
    list_time_slots
    接口获取每个平台的最佳发布窗口
  2. 将日历条目匹配到最合适的发布槽位
  3. 对于已经准备好发布的条目，调用 
    create_post
    接口传入草稿内容、平台和排期时间
  4. 排期前和用户确认：展示草稿内容、发布槽位和平台
  5. 排期完成后总结：「已为[日期]所在周在Y个平台排期了X条帖子。」
如果无法使用 BlackTwist：
输出完整的 markdown 格式日历，额外增加一列建议发布时间，基于通用最佳实践给出：
平台建议发布时间窗口
LinkedIn周二-周四，8-10点或12-13点（受众当地时间）
Threads早间（7-9点）或晚间（19-21点）
Twitter/X早间（8-10点）、午间（12-13点）或晚间（18-20点）
Bluesky早间（8-10点）或下午（14-16点）
告知用户：「绑定 BlackTwist 可以直接通过本日历完成排期。目前你可以使用这份表格在你选择的工具中手动排期。」

Step 6 — Flexibility buffer

步骤 6 — 灵活缓冲机制

Always protect 20–30% of weekly slots as open.
Open slots serve three purposes:
  1. Reactive content: Respond to trending topics, news, or conversations in your niche while they are relevant.
  2. Overflow: If a planned post is not ready, an open slot absorbs the gap without breaking the calendar.
  3. Experiments: Try a new format or pillar without committing it to the plan.
Mark open slots in the calendar as 
[Flexible — timely or reactive]
. Do not fill them during planning — they are intentionally empty.
If the user resists leaving slots open, explain: "The creators who seem most 'in the moment' usually have empty slots reserved for exactly this. It is not wasted capacity — it is strategic agility."
始终预留每周槽位的20-30%作为开放槽位。
开放槽位有三个作用：
  1. 热点内容：可以响应所在领域的热门话题、新闻或者相关讨论，保证内容时效性
  2. 溢出缓冲：如果计划中的内容没有准备好，开放槽位可以填补空缺，不会打乱整个日历
  3. 内容实验：可以尝试新的格式或者内容支柱，不需要提前纳入固定计划
在日历中将开放槽位标记为 
[灵活——时效性或热点内容]
，规划阶段不要填充内容，这些槽位是刻意留空的。
如果用户不愿意留空槽位，可以解释：「那些看起来内容非常『紧跟当下』的创作者通常都会预留空槽位专门做这件事。这不是浪费产能，而是战略灵活性。」

Step 7 — Review cadence

步骤 7 — 回顾节奏

A calendar without a review loop drifts. Recommend a lightweight weekly rhythm:
Example weekly review checklist:
Weekly Review — March 24
- Top performer: Tuesday thread on hiring (8.4% ER) — replicate format
- Underperformer: Friday promotional carousel (1.2% ER) — try Wednesday instead
- Open slots needed: 1 (industry report dropped Thursday)
- Calendar confirmed for next week: Yes
Weekly review (15–20 min, every Monday):
  • Which posts performed above expectations last week? Note the pillar, format, and angle.
  • Which posts underperformed? Consider dropping the format or angle, not the pillar.
  • Are any open slots needed for timely topics this week?
  • Confirm the week's calendar still reflects current priorities.
Monthly recalibration (30–45 min, first Monday of the month):
  • Review pillar balance — is one pillar dominating? Is another being neglected?
  • Adjust frequency per platform if engagement trends shifted.
  • Update the calendar template for the next month.
Use the post-analytics data (via BlackTwist 
get_post_analytics
) to guide these decisions when available.
没有回顾循环的日历会逐渐偏离目标。推荐轻量化的周度节奏：
周度回顾清单示例：
Weekly Review — March 24
- Top performer: Tuesday thread on hiring (8.4% ER) — replicate format
- Underperformer: Friday promotional carousel (1.2% ER) — try Wednesday instead
- Open slots needed: 1 (industry report dropped Thursday)
- Calendar confirmed for next week: Yes
周度回顾（每周一，15-20分钟）：
  • 上周哪些内容表现超出预期？记录对应的内容支柱、格式和角度
  • 上周哪些内容表现不及预期？考虑放弃对应的格式或角度，不用直接放弃对应的内容支柱
  • 本周有没有需要预留开放槽位的时效性主题？
  • 确认当周的日历仍然符合当前的优先级
月度校准（每月第一个周一，30-45分钟）：
  • 回顾内容支柱平衡情况——有没有某个支柱占比过高？有没有某个支柱被忽略？
  • 如果互动趋势发生变化，调整各个平台的发布频率
  • 更新下个月的日历模板
如果有可用的post-analytics数据（通过 BlackTwist 
get_post_analytics
接口获取），可以基于这些数据辅助决策。

Step 8 — Output: Content calendar

步骤 8 — 输出：内容日历

Present the final calendar in this format:
undefined
按照以下格式展示最终的日历：
undefined

Content Calendar

Content Calendar

Period: [Week of / Month of] [date] Platforms: [list] Total planned posts: [N] | Flexible slots: [N]
Period: [Week of / Month of] [date] Platforms: [list] Total planned posts: [N] | Flexible slots: [N]

Weekly Calendar

Weekly Calendar

[Calendar table]
[Calendar table]

Batching Plan

Batching Plan

[Session table]
[Session table]

Open Slots

Open Slots

[List of flexible slots and their purpose]

After presenting: "Ready to start filling in post drafts? Use **post-writer-sms** to write content for any of these slots. Or connect BlackTwist to schedule directly."

---
[List of flexible slots and their purpose]

展示完成后告知用户：「准备好填写帖子草稿了吗？使用 **post-writer-sms** 可以为任意槽位撰写内容。也可以绑定 BlackTwist 直接完成排期。」

---

Boundaries

能力边界

  • Does not write the actual post content — see post-writer-sms for drafting posts
  • Does not define content pillars or strategy from scratch — see content-strategy-sms for that
  • Does not analyze past post performance — see performance-analyzer-sms for analytics
  • Does not provide platform-specific algorithm tactics — see platform-strategy-sms for platform guidance
  • Does not execute code or access external APIs unless BlackTwist MCP is connected
  • Does not manage cross-posting or content adaptation — see content-repurposer-sms for reformatting across platforms
  • 不撰写实际的帖子内容——草稿撰写请参考 post-writer-sms
  • 不从零定义内容支柱或内容策略——相关需求请参考 content-strategy-sms
  • 不分析过往帖子表现——数据分析请参考 performance-analyzer-sms
  • 不提供平台专属的算法策略——平台相关指导请参考 platform-strategy-sms
  • 除非绑定了 BlackTwist MCP，否则不执行代码或访问外部API
  • 不处理跨平台同步或内容适配——跨平台格式调整请参考 content-repurposer-sms

See also

相关技能

content-strategy-sms — defines your pillars and content mix before building the calendar social-media-context-sms — foundational profile this skill reads from post-writer-sms — writes the actual posts for each calendar slot platform-strategy-sms — informs platform-specific frequency and format decisions
content-strategy-sms — 搭建日历前先定义你的内容支柱和内容组合 social-media-context-sms — 本技能读取的基础配置文件 post-writer-sms — 为每个日历槽位撰写实际的帖子内容 platform-strategy-sms — 提供平台专属的发布频率和格式决策参考