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

repurpose-content

Skill0 starsChanged 11 days agoMITView on GitHub

Turn one long piece (a YouTube video, podcast, blog post, newsletter, workshop, recipe collection or menu) into a week of Instagram Reels, carousels and stories that each stand alone, plus one Saypage page holding the full version that every post sends by keyword DM. Use for requests like "get Instagram posts out of my podcast", "reuse my YouTube video", "turn my article into content", or when the user pastes something long.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agency-clients, cross-post-video and 10 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.
  • posteverywhereSkill

    agency-clients

    Work safely across several clients or brands in PostEverywhere. Use when the user manages social media for more than one client, brand or business, mentions a client by name, asks to switch clients, or when the connected accounts belong to different companies.

    Also in 3 projects that use this

  • posteverywhereSkill

    cross-post-video

    Post one video to several platforms with PostEverywhere, with the right title and caption for each. Use when the user wants to share a video, Reel, Short or TikTok across TikTok, Instagram Reels, YouTube Shorts, LinkedIn and Facebook Reels, or asks to "post this video everywhere".

    Also in 3 projects that use this

  • CodeWithSulemanSkill

    approval-workflow

    Manage human-in-the-loop approval workflows for sensitive actions like payments, emails to new contacts, social media posts, and other actions requiring human oversight.

    Also in 3 projects that use this

  • flintfromthebasementSkill

    write-blog-post

    Write or edit a long-form blog post in a specific author's voice, then run it through six editorial passes (substance, structure, human voice, de-AI scrub, house style + O'Reilly word list, fresh-context critic) before delivering. Handles drafting from a brief, filling an outline, editing a draft, refreshing an old post, and applying revision notes. Use when the user wants a blog post that sounds like a real person wrote it, not a one-shot generation.

    Also in 3 projects that use this

  • +8 more from posteverywhere

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

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

    Do not shrink the source into a summary: look for pieces that make sense to someone who never saw it.

    line 21
  2. Distinctive:

    When the inventory is short (two or three finds), tell the user honestly: one strong post from it is better than four weak ones.

    line 34
  3. Very specific:

    Put the complete version on one Saypage page: the whole recipe, the full guide, the checklist, the episode notes with their links.

    line 39
  4. Very specific:

    Look at the plan's limits in get_account before offering an automation on every post.

    line 45
  5. Distinctive:

    Write each post for a stranger: no reference to the source ("in my podcast…"), and everything it needs to make sense inside the post itself.

    line 52

“Common” is measured: kept by at least 6 in 10 of the 6 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

Repurpose content

A long video, episode or article usually hides several Instagram posts, and the full version deserves a home too. This skill finds the posts inside it, and puts the whole thing on a Saypage page that every one of those posts can send by DM.

1. Take in the whole source

Work from the full text: a transcript, the article, the newsletter, the recipes, the workshop notes. A link you cannot open: ask the user to paste it. Go through all of it before choosing anything. If the user filmed the source themselves, ask for the file as well, since clips of the real footage feel more alive than a re-shoot.

2. Inventory what can stand alone

Do not shrink the source into a summary: look for pieces that make sense to someone who never saw it. Count them by kind, and show the counts before drafting:

FindWhat it isBest as
Momentsa scene with a person and a turn: what went wrong, what changedReel
How-tossteps someone can follow todaycarousel or Reel
Numbersa cost, a time, a quantity, a resultReel hook or carousel cover
Opinionsa claim someone could argue withReel
Fixesa mistake and how to avoid itReel
Linesa sentence quotable as it isstory frame
Questionswhat it answers that people askcarousel or a reply Reel

When the inventory is short (two or three finds), tell the user honestly: one strong post from it is better than four weak ones.

3. The page behind the posts

Put the complete version on one Saypage page: the whole recipe, the full guide, the checklist, the episode notes with their links. Offer to build it with the saypage skill (get_page_guide first, then a private preview; publish only with the user's agreement). Each post then closes on a keyword ("Comment GUIDE and I'll send you the full guide"), and an automation sends the page.

Look at the plan's limits in get_account before offering an automation on every post. A good start is one automation on the strongest post, and the same page in the bio link. On the Free plan the page and the automation are built and previewed, and go live with a plan that includes them: say so once ("Plans" in the saypage skill).

4. Lay out the week

  • Write each post for a stranger: no reference to the source ("in my podcast…"), and everything it needs to make sense inside the post itself.
  • Change the hook type from one post to the next (types in reel-script), so the week does not feel produced on a template.
  • Open the week with the post most likely to travel, and keep the most useful one (the how-to that sends the page) for when the first posts have brought new followers in.
  • Clips from the user's footage: start and stop at the edges of a sentence, and keep their natural reactions.

Output

SOURCE  "Why I stopped buying bread" (podcast, 38 min)
FOUND   3 moments, 4 how-tos, 6 numbers, 2 opinions, 3 fixes, 5 lines

PAGE    "Sourdough starter guide": the full method + the timings sheet  (to build)

TUE  REEL      Opinion   "Supermarket sourdough isn't sourdough."        clip at 12:40
THU  REEL      Moment    The starter I killed twice, and what saved the third
SAT  CAROUSEL  How-to    Your starter in 7 days                          ask: Comment STARTER -> page
DAILY STORIES  the 5 lines, one a day, link sticker to the page

Then draft the posts one by one when the user asks, with reel-script, carousel-post or instagram-caption, so each gets its own angle and voice.

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.