agentleFS
njpattennjpatten/claude-skills/content-repurposer/SKILL.md

content-repurposer

Skill0 starsChanged 2 months agoMITView on GitHub

Transforms raw input (call notes, voice memos, rough ideas, brain dumps) into polished social media posts matching the user's authentic voice. Triggers on 'turn this into a post', 'make this into content', 'repurpose this', 'write a LinkedIn post about', or when rough notes are shared for content creation.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use research-synthesizer, landing-page-copywriter and 4 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.
  • o2alexanderfedinSkill

    research-synthesizer

    Creates comprehensive synthesis documents distilling research findings into actionable insights. Activates when: creating synthesis.md files, aggregating research findings, integrating multi-source data, extracting strategic insights, or resolving conflicting information. Operates across technical, market, architecture, certification, and roadmap domains. Ensures evidence-based synthesis with full traceability to source research files.

    Also in 3 projects that use this

  • julianromliSkill

    landing-page-copywriter

    Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand. Creates headlines, value propositions, CTAs, and full page sections optimized for conversion. Use when users need landing page copy, sales page content, or marketing website text.

    Also in 3 projects that use this

  • Marine-softdrink524Skill

    seo-blog-writer

    SEO-optimized blog post writer with expertise in keyword research, content structure, meta tags, and search engine ranking strategies. Use when creating blog posts, articles, or any content that needs to rank well on Google.

    Also in 3 projects that use this

  • raroqueSkill

    youtube-script-writer

    Write a tight, retention-focused YouTube script from a topic, outline, or research brief. Use when the user asks for a video script, wants to turn notes or research into a YouTube video, needs a hook/intro rewritten, or wants to plan a video end-to-end with pacing, visual beats, and CTAs.

    Also in 3 projects that use this

  • vivy-yiSkill

    content-calendar

    Use when scheduling Xiaohongshu posts, maintaining consistent posting frequency, planning content around events or seasons, or organizing content production workflow

    Also in 4 projects that use this

  • ncklrsSkill

    proposal-writer

    Expert sales proposal and pricing presentation strategist. Use when writing proposals, executive summaries, ROI business cases, pricing presentations, SOWs (Statement of Work), RFP responses, or competitive positioning documents. Covers proposal structure, terms positioning, design formatting, follow-up strategy, and win-rate optimization.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 11

    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:

    Use this skill when:

    line 12
  2. Distinctive:

    Ask what platform: if not specified. Default to LinkedIn.

    line 22
  3. Distinctive:

    One idea per post: If the raw input has multiple ideas, pick the strongest one OR ask the user which to lead with.

    line 28
  4. Distinctive:

    No hashtags in the body: If hashtags are needed (LinkedIn), suggest 3-5 after the post in a separate "Hashtags" section.

    line 34
  5. Distinctive:

    No emojis unless the user uses them: Check the user's style. If they use emojis naturally, include them sparingly.

    line 36
  6. Distinctive:

    Offer a variation: After the first draft, suggest one alternative hook or angle.

    line 38
  7. Distinctive:

    If you're juggling multiple AI subscriptions, ask yourself: am I paying for capabilities, or am I paying for the lack of a system?

    line 76
  8. Distinctive:

    CTA patterns: Add your standard CTAs to the rules: "My default CTA is a question.

    line 94
  9. Distinctive:

    Audience context: Add a rule: "My audience is [who].

    line 96
  10. Distinctive:

    Platform preferences: If you only post on LinkedIn, remove the platform question from Rule 2 and hardcode it.

    line 98
  11. Distinctive:

    Content pillars: Add a rule: "My content pillars are: [pillar 1], [pillar 2], [pillar 3].

    line 100

“Common” is measured: kept by at least 6 in 10 of the 26 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

Content Repurposer

Transforms raw input — call notes, voice memo transcripts, rough ideas, articles you've read, shower thoughts — into a polished piece of content in your voice. Not a generic LinkedIn post generator. This skill holds YOUR tone, YOUR CTA patterns, and YOUR audience context.

Triggers

Use this skill when:

  • User says "turn this into a post," "make this into content," or "repurpose this"
  • User shares rough notes, a transcript, or a brain dump and wants content from it
  • User says "write a LinkedIn post about [topic]" or "I want to post about [idea]"
  • User says "I just had a thought about [topic] — help me turn it into something"

Rules

  1. Ask for the raw input if not provided. Minimum needed: a topic, a rough idea, or raw notes. Even a single sentence works — "I want to post about how most AI prompts are overcomplicated."
  2. Ask what platform if not specified. Default to LinkedIn. Options: LinkedIn post, email newsletter, Twitter/X thread, short-form social (Instagram/TikTok caption).
  3. Lead with the hook. The first 1-2 lines must stop the scroll. No throat-clearing. No "I've been thinking about..." openings. Hit them with the insight, the contrarian take, or the story moment.
  4. Write in the user's voice, not Claude's. Match the user's natural tone from their instructions and past conversations. If they're casual, be casual. If they're technical, be technical. Never default to corporate LinkedIn-speak.
  5. One idea per post. If the raw input has multiple ideas, pick the strongest one OR ask the user which to lead with. Don't cram three points into one post.
  6. Structure for scannability. Short paragraphs (1-3 sentences max). Line breaks between thoughts. Use white space aggressively — walls of text don't get read on social.
  7. End with engagement, not a sales pitch. The CTA should invite conversation: a question, a take people can disagree with, a "what's your experience?" prompt. Don't end every post with "DM me" or "link in comments" — save hard CTAs for 1 in 5 posts max.
  8. No hashtags in the body. If hashtags are needed (LinkedIn), suggest 3-5 after the post in a separate "Hashtags" section. Never embed them in the text.
  9. No emojis unless the user uses them. Check the user's style. If they use emojis naturally, include them sparingly. If they don't, keep the post clean.
  10. Offer a variation. After the first draft, suggest one alternative hook or angle. "Want me to try a version that leads with the story instead of the takeaway?"

Output Format

[Platform] Post

[Full post text, ready to copy and paste]


Hook alternative: [A different opening line they could swap in]

Hashtags (if LinkedIn): #tag1 #tag2 #tag3

Best time to post: [Day/time suggestion based on platform norms]

First comment suggestion: [Optional — a comment to drop under the post for engagement or a soft CTA]

Example

Raw input from user: "Had a discovery call today. Guy was using 4 different AI tools — ChatGPT for writing, Jasper for marketing, Otter for transcription, and Notion AI for notes. Paying like $120/month total. I showed him Claude doing all four in one project. He literally said 'wait, what?' Closed him on a strategy session on the spot."

LinkedIn Post

Most people are paying for 4 AI tools when they need one.

Had a call yesterday with a founder running ChatGPT for writing, Jasper for marketing, Otter for transcription, and Notion AI for notes. $120/month across four subscriptions.

I pulled up one Claude project and did all of it. In front of him. Live.

His response: "Wait... what?"

Here's what most people get wrong about AI tools: they solve for features instead of workflows. They end up with a Frankenstein stack where nothing talks to each other and they're still copy-pasting between tabs.

One well-configured AI project with good instructions, the right files, and trained memory will outperform a stack of five tools that don't know you exist.

He signed up for a strategy session before the call ended.

If you're juggling multiple AI subscriptions, ask yourself: am I paying for capabilities, or am I paying for the lack of a system?


Hook alternative: "$120/month on AI tools. One Claude project replaced all of them."

Hashtags: #AI #ClaudeAI #AIStrategy #Solopreneur #AITools

Best time to post: Tuesday or Wednesday, 7-9am your audience's timezone

First comment suggestion: "If you're curious what a well-configured Claude project looks like, I break down the full setup in my course. Link in my profile."

Customization Notes

To make this skill work for YOUR content:

  1. Voice calibration. Upload 3-5 of your best-performing posts as a project file called "content-examples.md." Claude will match that energy instead of guessing. This single step makes the biggest difference.
  2. CTA patterns. Add your standard CTAs to the rules: "My default CTA is a question. My hard CTA (use sparingly) is: [your link or offer]."
  3. Audience context. Add a rule: "My audience is [who]. They care about [what]. They're skeptical of [what]." This prevents generic content.
  4. Platform preferences. If you only post on LinkedIn, remove the platform question from Rule 2 and hardcode it. If you post across multiple platforms, keep it.
  5. Content pillars. Add a rule: "My content pillars are: [pillar 1], [pillar 2], [pillar 3]. Every post should connect to one of these." This keeps your feed focused instead of random.

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.