content-calendar
Skill0 starsChanged 7 months agoMITView on GitHub
Use to plan a 4-week content calendar across LinkedIn, blog, newsletter, and X. Produces a weekly theme, the assets per channel, owners, and a single quarterly narrative thread. Asks for the brand's pillar topics if not provided.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- clements23/marketing-agency-skillstheir own version, first seen Nov 8, 2026
- saypage-ai/saypage-plugintheir own version, first seen Nov 1, 2026
- epicx-labs/keytomic-claude-plugintheir own version, first seen Oct 25, 2026
- try-era/geo-skillstheir own version, first seen Oct 17, 2026
- postoncehq/postonce-skillstheir own version, first seen Oct 16, 2026
Used with
Projects with it also use campaign-brief, x-writer and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DanderlionJerSkillcampaign-brief
Generate comprehensive campaign brief from strategy notes and goals
Also in 3 projects that use this
stevenflanagan1Skillx-writer
X/Twitter Content Specialist. Writes X-native posts — hooks, threads, and standalone tweets optimised for the platform. Strictly enforces the 280 character limit with a count on every post. Supports standalone tweets and X threads (1/ format). Reads brand-style.md and content-calendar.md. Optional X trend research via Tasty Content MCP. Output to outputs/x/.
Also in 3 projects that use this
stevenflanagan1Skilllinkedin-writer
LinkedIn Content Specialist. Writes LinkedIn-native posts for SMB clients — first-person, professional-but-human, built for LinkedIn's format and algorithm. Not adapted captions: posts written from first principles for the platform. Reads brand-style.md and content-calendar.md. Flags posts that would benefit from a Blotato infographic. Output to outputs/linkedin/.
Also in 3 projects that use this
akhilkannurSkillcontent-repurposer
Also in 4 projects that use this
AnthropicSkillseo-audit
Run a comprehensive SEO audit — keyword research, on-page analysis, content gaps, technical checks, and competitor comparison. Use when assessing a site's SEO health, when finding keyword opportunities and content gaps competitors own, or when you need a prioritized action plan split into quick wins and strategic investments.
Also in 4 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- indranilbanerjee/digital-marketing-pro★ 934same name
- OpenClaudia/openclaudia-skills★ 731same name
- vivy-yi/xiaohongshu-skills★ 455same name
- Ootto-AI/claude-content-skills★ 417same name
- stevenflanagan1/social-ai-team★ 216same name
- marcosmodly/marketing-skill★ 141same name
- gokulsvision/Crewm8-Social-Media-Manager-Skill-Graph★ 17same name
- oswarld/notion-skills★ 11same name
- calven-ai/marketing-as-code★ 10same name
- styfinity/claude-marketing-department★ 6same name
17 more not listed
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 repository8 other files it gives its agents.
- code-reviewSkill
- cold-email-sequenceSkill
- funnel-analysisSkill
- market-researchSkill
- qualify-leadSkill
- release-notesSkill
- seo-outlineSkill
- write-linkedin-postSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Never schedule a post without a hook idea.
- Distinctive: line 60
Always leave one weekly slot unscheduled for reactive content.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
content-calendar
A content calendar is not a list of post ideas. It's a quarterly narrative split into weekly themes, where each week's assets reinforce each other across channels.
Inputs to gather
- Pillar topics — 3-5 topics the brand wants to be known for. If missing, ask.
- Channels in scope — LinkedIn, blog, newsletter, X, YouTube, podcast?
- Cadence — posts per channel per week.
- Quarterly narrative — the one story you want the audience to walk away with at the end of the quarter.
Output format
## Quarterly narrative
<one sentence: the story we want this quarter to tell>
## Pillar topics
1. <topic> — <one-line angle>
2. <topic> — <one-line angle>
3. <topic> — <one-line angle>
## 4-week calendar
### Week 1 — Theme: <theme>
| Channel | Asset | Hook | Owner | Repurpose from |
|---|---|---|---|---|
| Blog | <title> | <hook> | content-agent | — |
| Newsletter | <subject> | <opener> | content-agent | blog post |
| LinkedIn (Mon) | personal post | <hook> | linkedin-agent | blog excerpt |
| LinkedIn (Wed) | company post | <hook> | linkedin-agent | data point |
| LinkedIn (Fri) | personal post | <hook> | linkedin-agent | newsletter line |
| X (3x) | thread + 2 replies | <hook> | linkedin-agent | LinkedIn post |
### Week 2 — Theme: <theme>
[same shape]
### Week 3 — Theme: <theme>
[same shape]
### Week 4 — Theme: <theme>
[same shape]
## Production rules
- The blog drives every week. Everything else is a repurpose.
- Each week ends with a tie-back to the quarterly narrative.
- Reserve one slot per week for *reactive* content (industry news, customer story).Hard rules
- One theme per week. Don't try to cover three topics in five days.
- Repurposing is mandatory, not optional. The blog post becomes the newsletter, the LinkedIn post, and the X thread.
- Never schedule a post without a hook idea. "TBD" is a planning failure.
- Always leave one weekly slot unscheduled for reactive content.
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.

