agentleFS
postoncehqpostoncehq/postonce-skills/skills/content-calendar/SKILL.md

content-calendar

Skill1 starsChanged 31 days agoMITView on GitHub

Plan one to four weeks of social posts across every connected platform, draft each one natively, and schedule them all through PostOnce. Use when the user asks for a content calendar, a posting schedule, a week or month of content, content ideas to schedule, or to repurpose a blog, podcast, newsletter or video into a series of posts.

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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 1

    Distinctive

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

    Times: use the audience's local weekday mornings or lunchtimes unless the user knows better.

    line 28
  2. Very specific:

    Write every post natively per platform, following the post-everywhere skill's limits and style table.

    line 34

“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

Plan a realistic run of posts, write them, and schedule them with PostOnce so the user doesn't have to come back every day. A calendar the user can keep up with beats an ambitious one they abandon.

Inputs

Get or infer, then confirm in one message:

  • Goal: what the posts should lead to (followers, signups, sales, a launch, a page).
  • Source: their topics, or material to mine (blog URLs, a transcript, a newsletter, product notes). Prefer real material over invented topics.
  • Platforms and accounts: from list_active_accounts.
  • Cadence and length: how many posts a week they can sustain, and 1 to 4 weeks.
  • Timezone for every time you schedule.

Build the plan

  1. Pillars: 3 to 4 recurring themes from the goal and source (for example: how-to, behind the scenes, proof, opinion). Rotate them so no pillar runs twice in a row.
  2. Give each weekday a job. One content type per day, the same on every platform, keeps the mix balanced. A simple default: Mon teach, Tue tip, Wed personality or humor, Thu how-to, Fri product or offer. Leave a day empty rather than posting filler.
  3. One idea per slot. Each post carries one point. Break a long source into several atoms (a stat, a mistake, a step, a quote) and spread them across the weeks; never use the same atom twice in a week.
  4. Platform fit per slot: video ideas go to TikTok, Reels, Shorts and Facebook Reels; carousels to Instagram, LinkedIn and Threads; short takes to X, Threads and Bluesky; keyword-rich pins to Pinterest. Skip platforms a slot doesn't suit rather than forcing it.
  5. Times: use the audience's local weekday mornings or lunchtimes unless the user knows better. Space posts on the same account at least a few hours apart.

Show the plan as a table (date, time, pillar, idea, platforms, media needed) and get approval before writing.

Write and schedule

  • Write every post natively per platform, following the post-everywhere skill's limits and style table. Keep facts exactly as the source has them.
  • List the media each slot needs. Slots that need an image or video the user doesn't have yet become drafts (create_draft), not scheduled posts.
  • Schedule each ready slot with one create_post per time: publish_at as an ISO timestamp with the offset, one target per account, platform copy in content_override, settings like a YouTube title in platform_options.
  • Save every returned post ID next to its slot.

Hand back

Return the calendar with each slot's status: scheduled (with ID), draft (what's missing), or skipped (why). Remind the user that scheduled posts can be changed or cancelled before they go out with update_post or cancel_post, and that nothing is delivered until each post's status says published.

Need hooks or formats for the slots? Use the hook-vault and viral-formats skills.

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.