Social content planner
Build goal-led weekly or monthly social content calendars for marketers, social media managers, and small businesses. Use when the user asks for a content plan, posting calendar, campaign calendar, content pillars, posting cadence, ideas to fill calendar gaps, or a set of social drafts organized across dates and channels.From its SKILL.md
npx -y skills add celeryhq/simplified-ai --skill social-content-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, 604 tokens by cl100k_base, as published. Nobody here has run it
Social Content Planner
Turn business goals into a practical, channel-aware content calendar. Use the Simplified hosted MCP connector for account discovery, analytics, drafts, tags, and scheduling.
Guardrails
- Treat planning, drafting, and publishing as separate levels of authorization.
- Return a plan in conversation when the user asks only for a plan. Do not create remote drafts unless requested.
- Use
action: "draft"when the user asks to create or save the planned content. - Before any
scheduleoradd_to_queuecall, show the final posts, accounts, dates, media, and platform settings and obtain explicit confirmation. - Stop on
401or an empty account list and explain how to connect Simplified. - Present returned URLs as links, never as embedded images.
Workflow
- Establish the planning frame: business goal, audience, offer or topic, date range, channels, cadence, key dates, and desired call to action. Ask only for information that materially changes the plan; otherwise state reasonable assumptions.
- Call
social_getSocialMediaAccountsonce without a network filter when connected channels matter. Use only returned account IDs. - If the user wants a performance-informed plan, retrieve the relevant account analytics before ideating. Use
$social-performance-analystfor a full analysis. - Create three to five useful content pillars. Balance education, proof, promotion, engagement, and brand or community content rather than repeating one message.
- Assign each post a date, channel, pillar, objective, format, hook, core message, CTA, and asset requirement. Adapt the idea to each channel instead of copying identical text everywhere.
- Present the calendar in chronological order and flag missing source material or media.
- If remote drafts were requested, create each with
social_createSocialMediaPostandaction: "draft". Include required platform-specificadditionalfields from../simplified-social/references/platform-settings.md. - If scheduling was requested, create or show drafts first, then wait for explicit approval before scheduling.
Planning Heuristics
- Tie every post to one primary objective: awareness, engagement, consideration, conversion, retention, or trust.
- Use realistic cadence for the available channels and source material; do not fill a calendar with low-value repetition.
- Build sequences around launches and events: setup, reveal, proof, reminder, last call, and follow-up.
- For small businesses, prioritize offers, local relevance, customer proof, FAQs, behind-the-scenes content, events, and Google Business updates where appropriate.
- Reuse a campaign idea across channels, but rewrite the hook, length, CTA, hashtags, and format for each audience context.
Output
Summarize the strategy first, then show the calendar. End with counts by channel and pillar, unresolved inputs, and the exact next authorized action: plan only, drafts created, or awaiting scheduling approval.
What ships with it: 3 files
15.1 KB alongside SKILL.md
agents/
- openai.yaml596 B
assets/
- simplified-icon-256.png8.0 KB
- simplified-logo.png6.6 KB
Gives 0 of the 12 instructions most plan spec skills give in 604 tokens
Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06
- Ask one question at a timein 73 of 1360
- Write the spec using the templatein 22 of 1360
- Ask clarifying questions if neededin 19 of 1360, across 18 files
- Wait for user confirmation before proceedingin 19 of 1360
- Save plans to the plans directoryin 17 of 1360, across 13 files
- Check for product marketing context firstin 16 of 1360, across 5 files
- Read the plan file completelyin 16 of 1360
- Order tasks by dependencyin 16 of 1360
- Gather context from the conversationin 15 of 1360, across 9 files
- Explore the codebase instead of askingin 15 of 1360, across 13 files
- Wait for explicit user approvalin 14 of 1360, across 13 files
- Quiz the user on the breakdownin 13 of 1360, across 7 files
Said here and by no other author read
- Treat planning, drafting, and publishing as separate levels
- Return a plan in conversation when only asked for a plan
- Present returned URLs as links
- Establish the planning frame
- Create three to five useful content pillars
- Present the calendar in chronological order
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.