agentsclimarketplace
Sign in

Content repurposer

Skill celeryhq/simplified-ai/skills/content-repurposer

Transform one source asset into multiple channel-native social posts and a reusable content sequence. Use when the user asks to repurpose a blog post, video, transcript, webinar, newsletter, announcement, product page, testimonial, case study, podcast, or existing social post into content for LinkedIn, Instagram, Facebook, TikTok, YouTube, Threads, Bluesky, Pinterest, or Google Business.From its SKILL.md

Install
npx -y skills add celeryhq/simplified-ai --skill content-repurposer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 602 tokens by cl100k_base, as published. Nobody here has run it

Content Repurposer

Extract the strongest ideas from supplied source material and reshape them for the intended channels without inventing facts.

Guardrails

  • Treat the source as authoritative. Preserve names, numbers, claims, qualifications, links, and offer terms.
  • Clearly label any interpretation that is not directly supported by the source.
  • Return copy in conversation unless the user asks to save drafts.
  • Create remote content with action: "draft"; require explicit approval before scheduling or queueing.
  • Stop on MCP authorization failure or when required accounts are not connected.
  • Present returned URLs as links, never as embedded media.

Workflow

  1. Read the complete source material available to the user. If only a link is provided, retrieve it with an available browsing or connector tool before writing; do not guess its contents.
  2. Build a source ledger: central thesis, useful facts, proof points, quotes that may be paraphrased, stories, objections, CTA, and prohibited or unsupported claims.
  3. Identify reusable angles such as insight, checklist, contrarian point, customer proof, behind-the-scenes detail, FAQ, short tip, and offer.
  4. Select an output sequence that matches the source depth. Prefer fewer distinct posts over padded variations.
  5. Adapt each post to the channel's audience behavior, length, hook, CTA, and media format. Do not merely shorten the same caption.
  6. Call social_getSocialMediaAccounts once when the user wants connected-channel drafts.
  7. Show the proposed set with its source angle and intended channel. If asked to save it, call social_createSocialMediaPost with action: "draft" and the required settings from ../simplified-social/references/platform-settings.md.
  8. If new supporting visuals are explicitly requested, use $generate-image with storage: "asset" and pass each returned asset_id into social media. If the user supplies a local visual, follow $simplified-social through signed upload and api_registerAsset, then reuse the returned UUID.
  9. Wait for explicit approval before any scheduling or queueing operation.

Transformation Patterns

  • Long-form article: insight post, checklist, myth-versus-fact, quote card concept, and discussion prompt.
  • Webinar or transcript: key lesson, clip concept, speaker insight, FAQ, and follow-up CTA.
  • Case study or testimonial: challenge, turning point, outcome, lesson, and proof-led offer. Preserve exact attribution requirements.
  • Product announcement: problem, benefit, differentiator, demonstration, objection response, and launch CTA.
  • Event or promotion: announce, explain value, social proof, reminder, last call, and recap.

Output

State what was extracted from the source, then present each channel-ready post with its angle, copy, CTA, and media suggestion. Report whether the result is copy only, saved drafts, or awaiting publishing approval.

What ships with it: 3 files

15.2 KB alongside SKILL.md

agents/

assets/

Gives 0 of the 12 instructions most video audio skills give in 602 tokens

Counted across 619 of the 725 authors here whose files we hold, read 2026-09-06

  • Read product marketing context firstin 13 of 619, across 7 files
  • Define the core visual thesis in one sentencein 11 of 619, across 3 files
  • Break the concept into 3 to 6 scenesin 11 of 619, across 3 files
  • Render the smallest working version firstin 11 of 619, across 3 files
  • Start with a low-quality smoke test renderin 11 of 619, across 3 files
  • Add captions for accessibility and engagementin 11 of 619, across 5 files
  • Write the scene outline before writing codein 11 of 619, across 3 files
  • Specify subject, action, camera, style, and moodin 11 of 619, across 5 files
  • Decide what each scene provesin 10 of 619, across 2 files
  • Export one clean thumbnail framein 10 of 619, across 2 files
  • Pick the right tool for the jobin 10 of 619, across 4 files
  • Run the test suite before proposing a fixin 8 of 619, across 7 files

Said here and by no other author read

  • Treat the source as authoritative
  • Build a source ledger
  • Adapt each post to the channel

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.