agentleFS
Sign inStart free
Rushik-GhuntalaRushik-Ghuntala/claude-code-skills/skills/content-calendar/SKILL.md

content-calendar

Skill0 starsChanged 7 months agoMITView on GitHub

Generate weekly content plans with content pillars, cadence, and growth-stage-adapted strategies

27 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • DanderlionJerSkill

    campaign-brief

    Generate comprehensive campaign brief from strategy notes and goals

    Also in 3 projects that use this

  • stevenflanagan1Skill

    x-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

  • stevenflanagan1Skill

    linkedin-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

  • akhilkannurSkill

    content-repurposer

    Also in 4 projects that use this

  • AnthropicSkill

    seo-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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    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
  1. Distinctive:

    Use viral-hook-generator patterns for hook drafts

    line 34
  2. Distinctive:

    Use posting-schedule logic for optimal times

    line 35
  3. Distinctive:

    Every piece should serve the growth strategy, not just fill a slot

    line 78

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Calendar

Generate a complete 7-day content plan tailored to your developer niche, follower count, and growth goals.

Instructions

  1. Parse inputs from $ARGUMENTS:
    • Developer niche (e.g., "React developer", "DevOps engineer")
    • Follower count (for growth-stage adaptation)
    • Goals (e.g., "grow to 10K", "build thought leadership")
  2. Determine growth stage and adapt strategy:
    • 0-1K followers: Reply-heavy (70% replies, 30% original). Focus: build Real-graph scores. 1-2 tweets/day + 1 thread/week.
    • 1K-10K followers: Balanced. 1 thread/week + 1-2 daily tweets + selective replies.
    • 10K-50K followers: Authority building. Add thought leadership, signature frameworks, Spaces.
    • 50K+ followers: Platform building. Newsletter, premium content, selective partnerships.
  3. Apply content pillars from references/content-pillars.md:
    • Educational (40%) | Thought Leadership (20%) | Building in Public (20%) | Community (15%) | Personal (5%)
    • Adjust percentages by growth stage
  4. Follow weekly cadence from references/weekly-cadence.md:
    • Mon=Thread, Tue=Hot take, Wed=Code tip, Thu=BTS update, Fri=Community, Sat=Story, Sun=Rest
  5. Incorporate seasonal context from references/seasonal-dev-events.md if relevant
  6. Generate content for each day:
    • Use viral-hook-generator patterns for hook drafts
    • Use posting-schedule logic for optimal times
    • Match content type to pillar allocation
    • Include specific topic ideas based on niche + current trends
  7. Add daily reply targets and weekly growth goals

Output Format

📅 Content Calendar: [NICHE]
Growth Stage: [stage] ([follower count] followers)
Strategy: [1-sentence strategy summary]

| Day | Type | Topic | Hook Draft | Time (ET) | Pillar |
|-----|------|-------|------------|-----------|--------|
| Mon | Thread (8 tweets) | [topic] | "[hook]" | 8:30 AM | Educational |
| Tue | Hot take | [topic] | "[hook]" | 12:15 PM | Thought Leadership |
| Wed | Code tip | [topic] | "[hook]" | 8:00 AM | Educational |
| Thu | Build in public | [topic] | "[hook]" | 5:30 PM | Building in Public |
| Fri | Community | [topic] | [engagement activity] | 9:00 AM | Community |
| Sat | Story | [topic] | "[hook]" | 10:00 AM | Personal |
| Sun | Rest | — | — | — | — |

📊 Daily Targets:
- Reply to [N] tweets from [niche]-relevant accounts (esp. [follower range])
- Engage with [N] threads in your niche
- [Stage-specific daily goal]

🎯 Weekly Goals:
- [Impressions target]
- [New followers target]
- [Engagement rate target]
- [Content pieces to create]

💡 This Week's Opportunities:
- [Trending topic 1 in niche]
- [Seasonal event/relevance]
- [Suggested collaboration/engagement target]

Key Principles

  • Quality over quantity — better to skip a day than post filler
  • Replies are content too — especially at 0-1K stage
  • Every piece should serve the growth strategy, not just fill a slot
  • Adapt the calendar to what's actually trending, not just the template

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free