agentleFS
XuHo-ITXuHo-IT/Content-Agent-Kit/skills/repurpose/SKILL.md

repurpose

Skill3 starsChanged 3 months agoMITView on GitHub

Turn one thing you already published into several more — social variants with different hooks, a short video script, a carousel outline, a newsletter blurb — for an agent built with content-agent-kit. Use when the user says "make more from this", "repurpose this post", "turn this article into a video", or points at something already live. Tracks which angles have been used so the same one is not published twice.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use email, strategy 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.
  • OpenAISkill

    email

    Email sending integration guidance — Resend (native Vercel Marketplace) with React Email templates. Covers API setup, transactional emails, domain verification, and template patterns. Use when sending emails from a Vercel-deployed application.

    Also in 4 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 5

    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:

    Not writing more. Getting more out of what is written.

    line 11
  2. Distinctive:

    Read the source properly: Not the title — the whole thing.

    line 19
  3. Distinctive:

    Vary the hook across variants: If all of them open with a number, they read as one post published five times.

    line 80
  4. Very specific:

    Multi-channel calendar: Use social-post-master to adapt tone, format, and spacing natively across Facebook, Instagram, Threads, and X.

    line 84
  5. Very specific:

    Hook & Copy refinement: Use marketing-core and fb-hook-extractor to test high-converting copy variants and distinct angle formulas.

    line 85
  6. Distinctive:

    No shortcuts because the words already existed:

    line 89
  7. Distinctive:

    Only record an angle after it publishes.

    line 111

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

The kit is good at making things. It has no answer for making more from what you already made — and for one person, that is the difference between three posts a week and twelve.

Not writing more. Getting more out of what is written.

The capability is already here: examples/ai-video-social/ holds the same Claude Fable 5 source as both an article and a video. Nothing connected "I made this once" to "make five more from it". This is that connection.

Before you start

Read the source properly. Not the title — the whole thing. A repurpose written from a headline produces five posts that all say the headline.

Then decide whether it deserves it. Repurposing a weak piece multiplies the weakness: five variants of something nobody engaged with is five times the work for the same silence. If the original is thin, say so and stop. The honest output here is sometimes "this one is not worth it — write something new instead".

Signals it is worth repurposing:

  • it has a number, a result, or a claim someone could disagree with — those travel
  • it took real work to research, so the value is already paid for
  • it performed, or it covers something you know people ask about

1. Find the angles, do not invent them

An angle is a different thing the source says, not the same thing said differently. Rewording one idea five ways is spam; five ideas from one piece of research is a week of content.

Pull them from the source itself:

anglewhat to look for
the counterintuitive bitwhere the result contradicted the expectation
the numberthe single figure that carries the claim
the costwhat it took, what broke, what you would not do again
the howthe steps someone could follow tomorrow
the disagreementthe part reasonable people would argue with
the asidethe small thing you noticed that was not the point

Four to six angles from a substantial piece. Fewer if the source is short — do not pad to hit a number.

2. Check what has already gone out

cat brain/repurposed.json   # { "<source-id>": { "angles": ["counterintuitive", "cost"], … } }

This file exists because history.json cannot answer the question. That is a flat list of published titles — it dedups by identity, so it knows the source went out but not which angle you used. Repurposing without this check is how the same point gets published three times in a month with different wording.

Skip angles already listed. If every angle is used, say so — that is a finished source, not a failure.

3. Produce, in the format that fits the angle

Match the container to the idea rather than making all five formats every time:

the angle is…make
one sharp claima short social post
a number worth seeinga frame-chart-bars scene, or an image
a sequencea frame-step-list scene, or a carousel outline
a story with a turna short video — see templates/VIDEO_GENRES.template.json
a judgementa frame-review-verdict scene
context worth keepinga newsletter paragraph

Vary the hook across variants. If all of them open with a number, they read as one post published five times.

Pairing with registry skills for multi-channel distribution:

  • Multi-channel calendar: Use social-post-master to adapt tone, format, and spacing natively across Facebook, Instagram, Threads, and X.
  • Hook & Copy refinement: Use marketing-core and fb-hook-extractor to test high-converting copy variants and distinct angle formulas.

4. Through the same gates as anything else

No shortcuts because the words already existed:

node scripts/social/validate-post.mjs brain/<slug>/repurposed/<angle>.json --strict

WRITING_CRAFT.md applies. review-gate applies. A repurposed post is a post.

5. Record what you used

Append to brain/repurposed.json:

{
  "rerank-rag-tieng-viet": {
    "sourceTitle": "Rerank trong RAG tiếng Việt",
    "angles": ["counterintuitive", "cost"],
    "lastRepurposedAt": "2026-08-03"
  }
}

Only record an angle after it publishes. Recording at draft time means a rejected draft burns the angle forever.

6. Report

Append to brain/<slug>/report.md: which angles were taken, which were left, and why any were rejected. The left-over list is what makes the next pass fast.

What not to do

  • Do not republish the same angle in different words. That is what the state file is for.
  • Do not repurpose across languages by translating. A translated post reads translated. Rewrite it for the new audience or skip it.
  • Do not strip the source. A repurposed post that removes the number, the caveat and the link is a claim with nothing behind it. Keep what makes it checkable.
  • Do not schedule them all for the same week. Spread them. The point is to fill weeks you would otherwise have nothing for.

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.