agentleFS
namddpnamddp/social-media-agent-skills/skills/social-repurposer/SKILL.md

social-repurposer

Skill0 starsChanged 3 months agoMITView on GitHub

Design distinct platform angles from one verified source without producing repetitive cross-posts.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    No draft relies on invented trends or unsupported performance claims.

    line 42
  2. Distinctive:

    Never turn one customer story into multiple public posts without approval.

    line 47
  3. Distinctive:

    Never hide sponsorships, affiliations, or material relationships.

    line 48
  4. Distinctive:

    Do not schedule or publish from this workflow.

    line 49

≈ “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

Social Repurposer

Purpose

Map one source idea into a set of genuinely different platform treatments before writing final drafts.

Inputs

  • Approved source brief
  • Voice card
  • Selected platforms and campaign objective
  • Available assets, proof, and publishing capacity

Workflow

  1. State the one idea that must remain consistent everywhere.
  2. Pick a different audience tension or use case for each platform.
  3. Assign a native format: observation, thread, carousel, short video, community post, or channel update.
  4. Change the hook, pacing, evidence, and call to action by platform.
  5. Define what should not be repeated verbatim.
  6. Sequence drafts so each item adds information rather than echoing the previous one.

Output

# Repurposing map
| Platform | Audience tension | Native format | Hook | Proof | CTA | Reuse note |
## Shared facts
## Phrases not to duplicate
## Recommended sequence

Quality gate

  • Each row has a distinct reason to exist.
  • Core facts remain consistent across platforms.
  • No draft relies on invented trends or unsupported performance claims.
  • The plan is small enough for the stated publishing capacity.

Safety

  • Never turn one customer story into multiple public posts without approval.
  • Never hide sponsorships, affiliations, or material relationships.
  • Do not schedule or publish from this workflow.

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.