agentleFS
Sign inStart free
belzoralolbtwbelzoralolbtw/x-agent-skill/skills/x-repurpose/SKILL.md

x-repurpose

Skill0 starsChanged 34 days agoMITView on GitHub

Turn content the account owner already made elsewhere into X (Twitter) posts. Use when the user has a video, blog post, newsletter, podcast, talk, note, or thread and wants posts out of it, asks to repurpose, "turn this into tweets", or wants more posts without more ideas. Produces a set of standalone posts, each carrying one idea, humanized and copy-ready.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Jakeschincariol/x-agent-skill★ 4same name
    2. swayamdhawan/x-agent★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

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

    Read the voice profile (templates/voice.md), or infer the voice from the user's posts.

    line 19
  2. Distinctive:

    Ask where the source was published, so the posts do not just point back to it.

    line 24
  3. Distinctive:

    3. Space them: Do not post all of them one after another.

    line 44
  4. Distinctive:

    Every post ends with "full piece in the link".

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

x-repurpose

Most people do not need more ideas, they need more posts per idea. One good piece of writing usually holds five to ten X posts. This skill mines them out without turning the timeline into an ad for the original.

Before you write

  1. Read the voice profile (templates/voice.md), or infer the voice from the user's posts.
  2. Get the source pasted or linked in full. A video: ask for the transcript. A blog or newsletter: the text. Do not work from a summary; the specifics are the whole value.
  3. Ask where the source was published, so the posts do not just point back to it. On X, repurposed posts work as standalone ideas, not as teasers.

The rule that makes repurposing work

A repurposed post has to stand on its own with no link back. If the post only makes sense as a trailer for the source, it underperforms and it looks like promotion. The reader should get the whole idea from the post, and want more of the writer as a result, not more of the link.

The loop

1. Mine the source for the units that survive alone: a number, a counterintuitive claim, a mistake with a lesson, a short story, a specific how. List them. Aim for 5-10 for a substantial source.

2. Turn each into a post using x-post (opener pattern, shape, humanize). Different units take different patterns: a result takes "The Tally", an opinion takes "Against the Grain", a story takes "Cold Scene".

3. Space them. Do not post all of them one after another. Spread them across days and mix them with original posts. Ten posts from one source in an afternoon reads as a content dump.

4. Do not link the source unless the post genuinely cannot stand alone and a link adds something. When in doubt, leave it out. If the user wants traffic to the source, that belongs in a reply, or in the occasional dedicated post.

What mines well, and what does not

Mines well     specific numbers, steps, mistakes, quotes, short scenes,
               answers to a question the source poses.
Does not        the thesis (too big for one post), transitions, definitions,
               anything that needs the previous paragraph.

Failure modes

  • Posts that all say the same thesis in different words. One idea, one post.
  • Every post ends with "full piece in the link". That is an ad, not content.
  • Lifting sentences verbatim, so the posts read as pulled, not written.
  • Repurposing once and stopping. The best sources can be mined again in a month with new angles.
  • Ignoring the source's best specific because it does not fit a neat format. The specific detail is usually the strongest 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.

Check your setup, free