Agent skill
content-calendar
Create a 4-week content calendar from a topic, pillar, or product. Each week includes 1 main piece (video or newsletter), 3 social posts, and 1 Substack note. Output as a clean table. Use when user wants a "content calendar", "posting schedule", "month of content", or "content plan".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/content-calendar-alexmcfarland-ai-co-writer-plugins
SKILL.md
Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Content Calendar Builder
Purpose: Create a structured 4-week content calendar from a topic, content pillar, or product focus. Produces a ready-to-execute publishing schedule with specific titles and hooks for every piece.
When to Activate
Use this skill when:
- User wants a content calendar or posting schedule
- User mentions "plan my month", "content schedule", or "what should I post"
- User has a topic or product they want to build content around
- User needs structure for their content production
Required Input
- Topic, pillar, or product to build the calendar around
- Platforms they publish on (or default to: newsletter + LinkedIn + Twitter + Substack Notes)
- Any upcoming events, launches, or themes to incorporate
Weekly Structure
Each week includes:
- 1 Main Piece — Newsletter or video (the hub content for the week)
- 3 Social Posts — Platform-native posts (LinkedIn, Twitter, or Instagram)
- 1 Substack Note — Short-form insight
Total monthly output: 4 main pieces + 12 social posts + 4 notes = 20 pieces
Process
Step 1: Define Weekly Themes
Each week gets a sub-topic or angle related to the main topic:
- Week 1: Foundation / Introduction / The Problem
- Week 2: The Framework / The System / The How
- Week 3: Advanced / Nuance / The Mistakes
- Week 4: Results / Case Study / What's Next
Adjust themes based on the user's specific topic and goals.
Step 2: Fill the Calendar
For each content piece, provide:
- Day (suggested posting day)
- Platform
- Format (newsletter, thread, post, note, etc.)
- Title/Hook (specific enough to write from)
- Status (Not Started — for tracking)
Output Format
# 4-Week Content Calendar
**Topic/Pillar:** [Main topic]
**Date range:** [Start — End]
**Total pieces:** 20
---
## Week 1: [Theme]
| Day | Platform | Format | Title/Hook | Status |
|-----|----------|--------|------------|--------|
| Mon | Newsletter | Thought Leadership | [Specific title] | Not Started |
| Tue | LinkedIn | Post | [Hook line] | Not Started |
| Wed | Twitter/X | Thread | [Hook tweet] | Not Started |
| Thu | Substack | Note | [Opening line] | Not Started |
| Fri | Twitter/X | Standalone | [Tweet idea] | Not Started |
---
## Week 2: [Theme]
| Day | Platform | Format | Title/Hook | Status |
|-----|----------|--------|------------|--------|
| Mon | Newsletter | How-To Guide | [Specific title] | Not Started |
| Tue | LinkedIn | Post | [Hook line] | Not Started |
| Wed | Instagram | Caption | [Hook + concept] | Not Started |
| Thu | Substack | Note | [Opening line] | Not Started |
| Fri | Twitter/X | Thread | [Hook tweet] | Not Started |
---
## Week 3: [Theme]
| Day | Platform | Format | Title/Hook | Status |
|-----|----------|--------|------------|--------|
[Same structure...]
---
## Week 4: [Theme]
| Day | Platform | Format | Title/Hook | Status |
|-----|----------|--------|------------|--------|
[Same structure...]
---
## Monthly Overview
| Week | Theme | Main Piece | Social Pieces | Notes |
|------|-------|-----------|---------------|-------|
| 1 | [Theme] | [Newsletter: Title] | 3 posts | 1 note |
| 2 | [Theme] | [Newsletter: Title] | 3 posts | 1 note |
| 3 | [Theme] | [Newsletter: Title] | 3 posts | 1 note |
| 4 | [Theme] | [Newsletter: Title] | 3 posts | 1 note |
---
## Content Production Notes
- **Best day for newsletters:** [Recommendation based on audience]
- **Social posting times:** [Platform-specific recommendations]
- **Batch production tip:** Write all 4 newsletters first, then derive social content from them
- **Repurposing:** Each main piece should generate at least 3 of the social posts for that week
Quality Checklist
- 4 full weeks with 5 pieces each (20 total)
- Each week has a clear theme that builds on the previous
- Main pieces are specific enough to write from (not "write about topic")
- Social posts have actual hooks (not placeholder text)
- Platform variety across the month
- Content format variety (not all the same type)
- Themes align with the user's business goals
- Calendar is realistic for one person to execute
- Status column included for tracking
- Production notes included for efficiency
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?