Skip to content

AgriciDaniel/claude-repurpose / skills/repurpose-calendar

repurpose-calendar

Verified

Generates a 7-day publishing calendar with staggered posts, optimal timing per platform, file references, engagement reminders, and theme-day grouping. Prevents audience fatigue by limiting to 2-3 posts per day. Sub-skill of the Content Repurposing Engine. Use when user says "publishing calendar", "content calendar", "posting schedule", "7-day calendar", or "repurpose calendar".

Publishing Calendar Generator

Produce a 7-day staggered publishing calendar starting from the current date. Maps all repurposed content to specific days, times, and platforms.

Inputs

Received from the parent orchestrator:

InputDescription
generated_outputsList of all content files produced by other sub-skills
platforms_requestedWhich platforms were included (all if unspecified)
primary_topicCategory or niche of the source content
target_audienceWho benefits from this content
current_dateToday's date (start of the 7-day window)

References

Load these before generating the calendar:

  • references/platform-specs.md -- posting limits and format rules
  • references/engagement-benchmarks.md -- optimal timing data and engagement windows

Output: calendar.md

File: calendar.md

Calendar Table Format

The calendar is a markdown table with these columns:

| Day | Date | Time | Platform | Content Type | File Reference | Image Needed | Notes |
|-----|------|------|----------|-------------|----------------|--------------|-------|

Column definitions:

ColumnDescription
DayDay name (Monday, Tuesday, etc.)
DateActual date (YYYY-MM-DD) calculated from current_date
TimeRecommended posting time in local time
PlatformTarget platform name
Content TypeWhat is being posted (tweet, thread, carousel, poll, etc.)
File ReferenceRelative path to the output file (e.g., twitter/thread.md)
Image NeededYes/No -- whether this post requires an image or graphic
NotesEngagement reminders, dependencies, or special instructions

Optimal Posting Times

Use these windows as defaults. Adjust if the user specifies a timezone or audience location.

PlatformBest DaysBest Times (Local)Peak Window
Twitter/XMon-Fri9-11 AM or 1-3 PMTue-Thu 10 AM
LinkedInTue-Thu8-10 AMWed 9 AM
InstagramMon, Wed, Fri11 AM - 1 PMWed 12 PM
FacebookTue-Fri9 AM - 12 PMThu 10 AM
YouTube CommunityTue, Thu10 AM - 12 PMTue 11 AM
SkoolMon, Wed, Fri9 AM - 11 AMMon 10 AM
TikTokTue, Thu, Sat7-9 PMThu 8 PM
RedditMon-Fri8-10 AM ESTTue 9 AM EST
QuoraMon-Fri9 AM - 12 PMWed 10 AM
ThreadsTue, Thu10 AM - 1 PMThu 11 AM
PinterestSat, Sun8-11 PMSat 9 PM
SnapchatMon-Fri10 PM - 1 AMWed 11 PM
DiscordWeekdays3-8 PM ESTWed 5 PM EST
MediumTue-Thu8-10 AMWed 9 AM
WhatsAppDaily8-9 AM, 6-8 PMTue 8 AM
TelegramDaily9-11 AM, 7-9 PMWed 10 AM
NewsletterTue or Thu8-10 AMTue 9 AM

Scheduling Rules

Rule 1: Stagger Across Days

Never post to all platforms on the same day. Spread content across the full 7-day window to maintain consistent presence without flooding.

Rule 2: Maximum 2-3 Posts Per Day

No more than 3 posts on any single day. Audience fatigue is real. If a day has 3 posts, they must be on 3 different platforms.

Rule 3: Lead with Long-Form, Follow with Snippets

Publish comprehensive content first (LinkedIn article, newsletter, Reddit post), then extract and post shorter pieces (tweets, quote cards, polls) in subsequent days. This creates a natural content cascade.

Rule 4: Space Repeated Platforms

If a platform appears twice in the week (e.g., Twitter standalone tweet + Twitter thread), space them at least 2 days apart.

Theme Days

Organize the 7-day calendar by content theme. Adapt based on which platforms were actually generated.

Day 1 (Start Date): Long-Form Launch

PriorityPlatformContent TypeNotes
1LinkedInText post + carouselLead with the authoritative version
2MediumArticle (1500-3000 words)In-depth launch; Google SEO play
3NewsletterEmail excerpt (Day 0 of drip)Send to existing subscribers

Engagement reminder: "Reply to every LinkedIn comment within 60 minutes."

Day 2: Threads and Discussions

PriorityPlatformContent TypeNotes
1Twitter/XThread (8-12 tweets)Expand on Day 1's core insight
2ThreadsThread (5-10 posts)Parallel to Twitter; links allowed
3RedditDiscussion postPeer-to-peer version of the same insight
4QuoraAnswer postAuthority version; targets high-traffic question

Engagement reminder: "Engage with every thread reply for 2 hours after posting."

Day 3: Visual Content

PriorityPlatformContent TypeNotes
1InstagramCarousel (7-10 slides) + captionVisual breakdown of the topic
2TikTokVideo script (15-60s)Post after Instagram carousel; reference same atoms
3Pinterest3-5 pins + idea pinSEO-rich; longest-lasting content format

Engagement reminder: "Reply to Instagram comments within first hour for algorithm boost."

Day 4: Engagement and Polls

PriorityPlatformContent TypeNotes
1LinkedInPollAsk audience to weigh in on a key question
2Twitter/XPollSame question, adapted for Twitter's format
3FacebookQuestion post or pollConversational version
4DiscordPoll or reaction voteCommunity engagement in server
5TelegramPoll (quiz mode optional)Channel engagement

Engagement reminder: "Vote in your own polls (sets the tone). Comment on early responses."

Day 5: Community Building

PriorityPlatformContent TypeNotes
1SkoolChallenge or action postGive the community something to do
2YouTube CommunityText post or pollEngage existing subscribers
3DiscordDiscussion thread + announcementCommunity conversation

Engagement reminder: "Pin a follow-up comment with additional context."

Day 6: Drip and Reinforcement

PriorityPlatformContent TypeNotes
1NewsletterEmail 2 (Day 2 of drip)Deeper dive for subscribers
2WhatsAppChannel updateBest insight as personal message
3TelegramChannel postFormatted broadcast with key takeaway

Engagement reminder: "Monitor email replies; respond to any subscriber questions."

Day 7: Lightweight and Residual

PriorityPlatformContent TypeNotes
1InstagramStory or reel scriptLightweight, behind-the-scenes feel
2SnapchatStory script (3-5 frames)Ephemeral, raw feel
3SkoolDiscussion postOpen-ended community question

Engagement reminder: "Respond to any leftover comments from the week across all platforms."

Drip Sequence Integration

Map the 3-email drip to calendar days: Email 1 on Day 1 (with long-form launch), Email 2 on Day 3 or 6, Email 3 on Day 5 or 7. Shift to next weekday if start date falls on a weekend.

Platform Filtering

If not all platforms were generated, remove missing rows, redistribute content (max 2-3/day still applies), compress to 3-4 days for 1-2 platforms.

Calendar Footer

Include after the table: total pieces count, platforms covered, image assets needed (reference images/prompts.md), email drip status, and these engagement rules: respond to comments within 60 minutes, engage with 3-5 niche posts before and after yours, never post and ghost, track top performers for future repurposing.

Error Handling

ConditionAction
No outputs generated yetCannot build calendar; report error to orchestrator
Only 1 platformGenerate 3-day schedule; 1 post per day
Start date is weekendShift Day 1 to next Monday; compress weekend into light days
brief_mode was usedCondense to 3-day calendar; top 3 platforms only
Missing image assetsMark "Image Needed: Yes" and reference images/prompts.md
Email drip not generatedRemove drip rows; note in footer
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall