agentleFS
Sign inStart free
UXMagicaiUXMagicai/seosorted-skills/skills/content-calendar/SKILL.md

content-calendar

Skill0 starsChanged 39 days agoMITView on GitHub

Plan and manage the publishing schedule for SEOsorted articles — see what is scheduled and published on the calendar, which destinations are connected and whether deliveries failed, fill gaps with content ideas, and schedule ready articles on a steady cadence. Use when the user asks about their content calendar, publishing schedule, why posts stopped going out, what's publishing next, what to write next, or wants to schedule articles.

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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If posts "stopped", get_publishing_calendar operation: "deliveries" — recent publish attempts with their errors.

    line 14
  2. Distinctive:

    All three are free.

    line 16
  3. Very specific:

    Not enough ready? get_content_ideas operation: "ideas" for saved ideas, or with generate: true and count to write new ones from the …

    line 21

“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

Scheduled articles auto-publish to the default destination. If nothing is scheduled, publishing stops — the most common reason "the blogs stopped".

1. Read the calendar

  1. get_publishing_calendar operation: "calendar" (default today + 30 days; from / to as YYYY-MM-DD, at most 120 days) — scheduled and published articles with dates and live URLs.
  2. get_publishing_calendar operation: "destinations" — connected destinations, which are ready, and the default. No ready destination means scheduled posts cannot go out: send the user to Settings → Integrations.
  3. If posts "stopped", get_publishing_calendar operation: "deliveries" — recent publish attempts with their errors. Report the exact error.

All three are free.

2. Find what can fill it

  1. manage_articles operation: "list" with status: "READY" — written, waiting for a date.
  2. Not enough ready? get_content_ideas operation: "ideas" for saved ideas, or with generate: true and count to write new ones from the business profile; operation: "topic_opportunities" for the keyword opportunities found at onboarding. Free. Ideas become articles through write-article or bulk-content-run.

3. Schedule

  1. Propose a cadence. Defaults: 1–2 posts per day for an established site, 3–4 per week for a new one. Spread clusters out rather than publishing one topic in a burst. Quick wins and seasonal topics first.
  2. Show the schedule as a table (date, time, title, keyword) and get approval.
  3. publish_articles operation: "schedule" per article with article_id and scheduled_for (ISO date-time, future). Run it with dryRun: true first, then with confirm: true once the user has said yes.

Notes

  • Scheduling is a paid feature. If the tool returns an upgrade link, pass it on as is.
  • To pull an article off the calendar: operation: "unschedule" (also needs confirm: true).

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