agentleFS
postoncehqpostoncehq/pinterest-mcp/skills/pinterest-content-calendar/SKILL.md

pinterest-content-calendar

Skill2 starsChanged 47 days agoMITView on GitHub

Plan 1–4 weeks of Pinterest pins from the user's goals, content pillars or a source to repurpose (blog URL, video, transcript), draft every pin, and schedule them with the PostOnce Pinterest MCP. Use when the user asks for a Pinterest content calendar, a Pinterest posting schedule, Pinterest pin ideas for the month, or a plan to keep pinning consistently.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't repeat the same pin on the same board in the same week.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Pinterest content calendar

Plan a steady run of pins, draft each one fully, and schedule the set once the user approves it. Pinterest rewards consistency and fresh pins over bursts, so a calendar is a good fit.

Inputs to get first

  • Goal: traffic to a blog, sales from a shop, email sign-ups, or awareness.
  • Pillars (2–5 topics) or a source to repurpose: blog URLs, a video, a transcript, a product list.
  • How many weeks (1–4) and pins per week. A small account can start with 3–7 pins a week; more only if the user has the images.
  • Pinterest account, board IDs if they want specific boards, timezone and preferred times.
  • What images exist. Every pin needs an image or a video.

Pin types to mix

TypeMediaGood for
Image pin1 image, 1000×1500 (2:3)Most pins: recipes, tutorials, products, list posts
Carousel2–5 images, same sizeSteps, before/after, a product in several colors
Video pin1 video, 4 seconds to 5 minutesHow-to clips, process, quick demos

Rules:

  • Each pin has its own image and title, even when several link to the same page. Use pinterest-blog-to-pins for one article and pinterest-pin-maker for images.
  • Plan seasonal topics ahead; people search for holidays and seasons weeks before they arrive.
  • Titles up to 100 characters, descriptions up to 500, keyword first, no hashtags (see pinterest-pin-description-generator).
  • Set link to the page the pin promotes. Links are optional but most Pinterest goals need one.
  • Don't repeat the same pin on the same board in the same week.

Build the calendar

  1. Spread pillars evenly across the weeks.
  2. Give each slot: date and time, pillar, pin type, title, description, link, board, image note.
  3. Flag slots that still need an image from the user.

Output

Return the calendar as a table, then the full text of every pin. Ask for approval and edits. On approval, for each pin: upload images with create_upload_url, then call create_post with publish_at, media, and title, link and optional boardId in platform_options. Pins without images yet go in as create_draft. Confirm the account, boards and timezone before the first create_post (see the postonce skill), then report each post ID and time.

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.