Skill 详情
content-calendar-sms
Plans social posting schedules and content calendars.
使用前先检查
自动化审核只检查相关性,不代表安全审查或推荐。使用前请阅读来源中的说明。
SKILL.md
这段内容是审核时保存的快照。外部来源才是完整且最新的版本。
--- name: content-calendar-sms description: "When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post. Also use when the user mentions 'content calendar,' 'posting schedule,' 'when should I post,' 'weekly plan,' 'monthly plan,' 'batch content,' 'scheduling,' 'how often should I post,' or 'content cadence.' For deciding what topics to cover, see content-strategy-sms. For writing the actual posts, see post-writer-sms." metadata: version: 1.0.0 --- ## 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. --- ## Step 1 — Check for existing context 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." --- ## Step 2 — Discovery questions 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? --- ## Step 3 — Calendar generation 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): | Day | Platform |在 GitHub 阅读完整来源 (打开外部页面)