agentleFS
postoncehqpostoncehq/pinterest-mcp/skills/pinterest-blog-to-pins/SKILL.md

pinterest-blog-to-pins

Skill2 starsChanged 49 days agoMITView on GitHub

Turn one blog post URL into 5–10 fresh Pinterest pins, each with its own image, title and description, linked to the post and scheduled over several weeks with the PostOnce Pinterest MCP. Use when the user asks to promote a blog post on Pinterest, turn an article into pins, repurpose a blog for Pinterest, or drive blog traffic from Pinterest.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Read the post and pull 5–10 distinct angles.

    line 23
  2. Distinctive:

    Put the strongest angle first.

    line 46
  3. Distinctive:

    Use the user's times; if they have none, suggest evenings and weekends, when many people browse Pinterest, and say it's a starting point.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 blog to pins

One good article can carry many pins. Each pin is a different way into the same post: a different angle, image and title, all with the same destination link. Spread them out over weeks instead of posting them all at once.

Inputs to get first

  • The blog post URL. Read the page if your environment can fetch it; otherwise ask the user to paste the text.
  • Photos from the post or the user's library. Pins need an image or video; text-only pins aren't possible.
  • The Pinterest account and, optionally, the board ID for these pins.
  • How many pins (default 6) and over how long (default 3–4 weeks).
  • The user's timezone and preferred posting times.

Find the angles

Read the post and pull 5–10 distinct angles. Each must be true to the post:

AngleExample for "How to start a sourdough starter"
The main promiseEasy Sourdough Starter for Beginners
A specific audienceSourdough Starter Without a Kitchen Scale
A list inside the post5 Signs Your Sourdough Starter Is Ready
A problem it solvesWhy Your Sourdough Starter Isn't Rising
A step or timelineDay-by-Day Sourdough Starter Schedule
A checklist or printableSourdough Starter Supplies Checklist

Skip angles the post doesn't actually cover. Never invent results, stats or quotes.

Build each pin

  • Image: a different photo or layout for every pin. Use the pinterest-pin-maker skill for 1000×1500 images with a text overlay. Don't reuse one image with a new title; Pinterest treats new images as fresh pins.
  • Title (up to 100 characters): the angle's search phrase first. Use the pinterest-pin-description-generator rules.
  • Description (up to 500 characters): the phrase in the first sentence, related phrases after, a reason to click at the end. No hashtags.
  • Link: the blog post URL, set as link in platform_options. Every pin in the set uses the same link.

Schedule

  • Space pins out: one or two per week per post works well, and alternating angles keeps the set from looking repetitive.
  • Put the strongest angle first.
  • Use the user's times; if they have none, suggest evenings and weekends, when many people browse Pinterest, and say it's a starting point.

Output

Return a table: date and time, title, description, image note, link, board. Then the rendered images or design notes. On approval, upload each image with create_upload_url and call create_post once per pin with publish_at, the image as media, and title, link and optional boardId in platform_options (see the postonce skill). Confirm the account, board and schedule before the first create_post. Report each post ID and scheduled time, and check one with get_post.

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.