agentleFS
JayantChopraJayantChopra/stanley-mcp-playground/.claude/skills/repurpose/SKILL.md

repurpose

Skill8 starsChanged 3 months agoApache-2.0View on GitHub

Turns one piece of the user's content into platform-native drafts, quote cards, and carousels through Stanley; use when the user wants an existing post or thread adapted for other platforms.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

  • 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

  • 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

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Ask the user for the source: a URL to their X thread or post, a pasted LinkedIn post, or a description like "my best post this month".

    line 8
  2. Distinctive:

    Ask which targets they want.

    line 9
  3. Distinctive:

    If you don't know what's connected, send Stanley this first: "List every platform and integration currently connected for this account, …

    line 10

“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

Drive the message_stanley tool to convert one source post into drafts for other platforms. Stanley keeps conversation state across calls, so talk to him in plain English.

  1. Ask the user for the source: a URL to their X thread or post, a pasted LinkedIn post, or a description like "my best post this month". A described top performer needs no link; Stanley finds it through analytics.
  2. Ask which targets they want. The supported conversions: LinkedIn post, single X post or thread, Threads chain, quote-card image (a screenshot of an X post), multi-slide carousel.
  3. If you don't know what's connected, send Stanley this first: "List every platform and integration currently connected for this account, flag anything expired or broken, and show the configured posting slots." Drop any target that isn't connected and tell the user.
  4. Send Stanley the source and the targets in one message. He returns drafts wrapped in platform tags like <tweet> or <linkedin_post>. Show each draft to the user, and keep the wrapper intact whenever you pass a draft back to Stanley.
  5. Relay the user's feedback draft by draft until they approve each one. Don't rewrite drafts yourself; Stanley runs per-platform quality checks your edits would skip.
  6. On approval, ask whether to schedule. Scheduling drafts into future slots is fine without extra ceremony, since it's reversible. Schedule only the drafts the user approved.
  7. Hard rules: never ask Stanley to publish live, delete a live post, send a DM, or email a subscriber list unless the user explicitly approves that exact action in this conversation. Instagram never auto-publishes; a carousel for it ends as a prepared draft the user posts by hand, and you should say so up front.

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.