agentleFS
Sign inStart free
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/repurpose-content/SKILL.md

repurpose-content

Skill2 starsChanged 2 months agoMITView on GitHub

Turn an interview, newsletter, talk or other long source into distinct content pieces or visual briefs while preserving its facts and voice.

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

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    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. Very specific:

    Read AGENTS.md, relevant identity, audience, strategy and voice pages, and the full supplied source.

    line 11
  2. Very specific:

    Use linkedin-copywriter for LinkedIn drafts and graphics-designer or flowchart when the relationship is clearer visually.

    line 17
  3. Distinctive:

    Keep the CTA aligned with the current offer.

    line 19

“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

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Repurpose content

Read AGENTS.md, relevant identity, audience, strategy and voice pages, and the full supplied source. Use capture-context if the source has not been preserved. Record source sections or timestamps for each candidate.

Extract independent ideas, examples, disagreements, processes and evidence. Rank them by usefulness to the intended reader and fit with the author's strategy, not by how many posts can be produced.

For each selected piece, identify one point, its source section, pillar, funnel job and suitable format. Different wording alone does not make a second distinct piece. Preserve the source's uncertainty, time period and scope. Do not transfer a guest's experience into the author's first-person story.

Use linkedin-copywriter for LinkedIn drafts and graphics-designer or flowchart when the relationship is clearer visually. A request for a video brief can produce a sourced storyboard and shot list; do not claim a rendered video without actually rendering and inspecting it.

Keep the CTA aligned with the current offer. Mention the original source when it helps the reader, rather than opening every piece with an announcement about repurposing.

Deliver the requested quantity supported by the source; explain any shortfall. Include a compact source-to-piece map outside the copy. Save to Notion only within the requested scope using the configured destination and existing-card check.

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