agentleFS
saypage-aisaypage-ai/saypage-plugin/skills/content-calendar/SKILL.md

content-calendar

Skill0 starsChanged 12 days agoMITView on GitHub

Plan the user's Instagram week: how many posts they can really make, the format and subject of each, the call to action and the Saypage page or automation behind it, daily stories and time for comments. Built from their recent posts and insights when Saypage is connected. Use for requests like "what do I post this week", "make me a posting schedule", "I'm out of ideas", "organise my Instagram for November", "ideas for today's stories".

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

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

  • 3

    Very specific

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

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

    If sales-plan or performance-review ran in this conversation, their findings outrank every default below.

    line 22
  2. Very specific:

    The ask: when a post promises something to send, give it a keyword and say which page it sends (an existing one from list_pages, or one to …

    line 50
  3. Very specific:

    The bio: if the plan pushes people to the bio link, make sure it leads to a page that matches the offer (profile-review).

    line 57
  4. Distinctive:

    Use the audience's time zone, from the demographics when available.

    line 62

“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

A plan the user can keep beats an ambitious one they drop on Wednesday. This skill decides what to make; the other skills write it.

1. Start from what is true

With Saypage connected (call get_account first):

  • list_instagram_posts: the last four weeks of posts, their formats and topics, so the plan does not repeat a theme from last week.
  • get_instagram_insights over 28 days, with demographics: true when the account has 100 followers or more: the countries tell you which time zone to plan in.
  • list_automations and get_page_stats: which keywords already run, and which pages people visit.
  • If sales-plan or performance-review ran in this conversation, their findings outrank every default below.

Then ask, in one message:

  1. What is happening this week: a launch, a new dish, an event, a result, a lesson, a customer story. A week's news gives better posts than any idea list.
  2. What they want from Instagram right now: new followers, visits, bookings, sales, DMs.
  3. How many posts they can realistically make: be honest, two good ones beat five rushed.

2. The mix

Give each post one job, and vary them across the week:

JobUsual formatWhat it does
DiscoverReelbrings in viewers new to the account
Usefulcarousel or Reelgets saved and sent: recipes, steps, tips
TrustReel, photo or storiesthe person, the place, the process, behind the scenes
Offercarousel, Reel or storieswhat they sell, said plainly, with the keyword or link

A week of three posts might be Discover, Useful, Offer, with stories every day.

Give each post a precise subject the user could film tomorrow: "the €4 dinner I make when the shop closes late" rather than "pasta".

3. Wire each post to Saypage

  • The ask: when a post promises something to send, give it a keyword and say which page it sends (an existing one from list_pages, or one to build with reel-funnel). An Offer post needs something to sell: if the user has nothing yet, start with offer-finder.
  • The automation: note which ones to create and on which post. Check the plan's limits in get_account before promising one on every post. On the Free plan none runs yet: plan the asks and build the pages all the same, and say once that they go live with a plan that includes them ("Plans" in the saypage skill).
  • The bio: if the plan pushes people to the bio link, make sure it leads to a page that matches the offer (profile-review).

4. When to post

Use the audience's time zone, from the demographics when available. Pick moments when they browse (commutes, lunch, evenings for most people), check the guess against the user's own best posts, and then keep a steady rhythm. If the user spends more time on the hour than on the opening of their Reels, steer them back: a weak opening loses more than an odd hour.

Saypage has no scheduler: it publishes when the user asks. The plan says when to come back ("Tuesday 6 pm: publish the gnocchi Reel"), or the user posts from the app.

5. Around the posts

Comments: 15 minutes after each post to answer the first comments (comment-replies).

Stories: three to six frames a day. They rarely reach new people: they reach followers, for a day, so use them to give those followers an easy reason to reply, visit or buy.

  • A day's shape: what is happening now, filmed; a detail, a price or how it is made; one sticker around the middle, while most people still watch; the answer, or a reason to come back tomorrow.
  • One sticker per job: a poll for easy taps, a question box to hear what people want (keep the answers: they are tomorrow's hooks), a link to a Saypage page, a countdown for a launch.
  • Open on something real (a face, hands, a place), with few words, away from the top and bottom 250 px of the 1080×1920 frame.
  • Selling works here: the context, then the offer, then someone who liked it.
  • What Saypage cannot do: Instagram's API publishes stories without stickers, so frames with a poll or a link go out from the app. Plain frames can go through Saypage when the user asks (prepare_instagram_post with kind: "story", or publish_instagram_video). Replies land in the inbox, which Saypage cannot read, and trigger no automation: to send something automatically, point the story to a post with a keyword, or add a link sticker. Visits from link stickers appear in get_page_stats under instagram_bio.

Output

WEEK OF 2 NOVEMBER  ·  3 posts  ·  audience mostly in France (Europe/Paris)

TUE 18:30  REEL      Discover  "I salted pasta water wrong for ten years"   ask: follow
THU 12:00  CAROUSEL  Useful    5 weeknight sauces, 10 minutes each           ask: Comment SAUCES -> sauces page (to build)
SAT 10:00  REEL      Offer     Sunday cooking class, 6 seats left            ask: Comment CLASS -> booking page (live)

STORIES   every day; poll on Wednesday, class countdown from Thursday
COMMENTS  15 min after each post

To do with Saypage: build the sauces page, then an automation on Thursday's post.

Then offer to write the first post ("write Tuesday"), one at a time with reel-script, carousel-post or instagram-caption.

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.