social-media-calendar
Skill5 starsChanged 19 days agoMITView on GitHub
Builds a complete monthly cross-platform social media content calendar (Instagram, TikTok, YouTube, LinkedIn, X, Facebook, Pinterest, Threads) with themes, pillars, post ideas, drafts, formats, posting times, and campaign or holiday hooks, exported as Markdown and CSV for Notion, Google Sheets, Buffer, or Later. Use when the user asks for a content calendar, posting schedule, or monthly social media plan.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- tkcostello/pastor-ai-skillstheir own version, first seen Nov 13, 2026
- kevinaimonster/skill-hubtheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- tkcostello/pastor-ai-skills★ 56same name
- kevinaimonster/skill-hub★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- docs/llms.txtllms.txt
- a11y-fixerSkill
- ad-copy-generatorSkill
- agent-guardrailsSkill
- agent-memory-keeperSkill
- ai-slop-detectorSkill
- api-to-sdkSkill
- app-store-optimizerSkill
- architecture-doctorSkill
- brand-voice-guideSkill
- bug-detectiveSkill
- changelog-from-gitSkill
- codebase-explainerSkill
- codebase-time-machineSkill
- commit-craftSkill
- competitor-spySkill
- content-repurposerSkill
- cost-cutterSkill
- demo-recorderSkill
- dependency-doctorSkill
- dockerize-anythingSkill
- durable-agent-workflowsSkill
- e2e-flow-testerSkill
- email-campaign-writerSkill
- env-secrets-guardSkill
- gh-actions-auditorSkill
- hook-generatorSkill
- incident-commanderSkill
- influencer-outreachSkill
- instagram-growth-managerSkill
- landing-page-roasterSkill
- launch-post-writerSkill
- meeting-notes-to-ticketsSkill
- merge-conflict-resolverSkill
- migration-wizardSkill
- plan-grillerSkill
- prompt-injection-scannerSkill
- pr-reviewer-proSkill
- readme-glow-upSkill
- roast-my-githubSkill
- screenshot-to-componentSkill
- seo-blog-writerSkill
- skill-creator-proSkill
- skill-finderSkill
- skills-doctorSkill
- social-analytics-reporterSkill
- social-media-managerSkill
- sql-optimizerSkill
- startup-idea-validatorSkill
- tdd-loopSkill
- terse-modeSkill
- test-gap-hunterSkill
- tiktok-viral-creatorSkill
- ui-tasteSkill
- youtube-script-writerSkill
- youtube-seo-optimizerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Create one hero piece per week (a long video, blog post or live session) and repurpose it into smaller posts (see content-repurposer).
- Distinctive: line 30
Default posting times are only a starting point, so tell the user to replace them with the best times from their own analytics.
- Distinctive: line 42
Never plan more content than the stated capacity.
- Distinctive: line 43
Every post needs a purpose (a pillar) and a CTA.
- Distinctive: line 44
Import into Notion, Sheets, Buffer, Later or Metricool only through tools the user has connected, and after confirming with them.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Social Media Calendar
A month of content planned in one go, realistic for the team that has to produce it.
1. Intake
Brand, audience, goals and KPIs for the month, active platforms, team capacity (posts per week you can really produce), upcoming launches, events, promotions and the region (for holidays).
2. Plan the month
- A monthly theme plus a weekly sub-theme.
- Pillars and their ratio, for example 40% educate, 25% entertain, 20% community or proof, 15% promote.
- Key dates: launches, relevant holidays, awareness days and cultural moments for the user's region. Mark them
[VERIFY]if the date might be wrong. - Create one hero piece per week (a long video, blog post or live session) and repurpose it into smaller posts (see
content-repurposer).
3. Calendar output
A Markdown table and a CSV file (content-calendar-<yyyy-mm>.csv):
date,time,platform,format,pillar,topic,hook,caption_draft,cta,hashtags,asset_needed,owner,status
2026-11-03,18:00,instagram,reel,educate,"...","...","...","Save this","#a #b","15s talking head",Sara,ideaDefault posting times are only a starting point, so tell the user to replace them with the best times from their own analytics.
4. Production checklist
A list of assets to create grouped into a batch-production day (film all the Reels together, design all the carousels together), with deadlines set 2–3 days before publish dates.
5. Weekly check-in template
What was published, the top performer and why, what to change next week.
Rules
- Never plan more content than the stated capacity. Consistency matters more than volume.
- Every post needs a purpose (a pillar) and a CTA.
- Import into Notion, Sheets, Buffer, Later or Metricool only through tools the user has connected, and after confirming with them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

