content-repurposer
- Repo stars 1
- Author updated Live
- Author repo claude-skills
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @00PrabalK00 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: content-repurposer
description: Transform one source asset into channel-specific content such as LinkedIn posts, X threads, capt…
category: writing
runtime: no special runtime
---
# content-repurposer output preview
## PART A: Task fit
- Use case: Transform one source asset into channel-specific content such as LinkedIn posts, X threads, captions, reel scripts, carousel copy, blog outlines, or newsletters while preserving the core message and voice. Use when adapting content across platforms..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / Core Workflow / Deliver” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Transform one source asset into channel-specific content such as LinkedIn posts, X threads, captions, reel scripts, carousel copy, blog outlines, or newsletters while preserving the core message and voice. Use when adapting content across platforms.”.
- **02** When the source has headings, the agent prioritizes “Overview / Core Workflow / Deliver” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Overview / Core Workflow / Deliver”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: content-repurposer
description: Transform one source asset into channel-specific content such as LinkedIn posts, X threads, capt…
category: writing
source: 00PrabalK00/claude-skills
---
# content-repurposer
## When to use
- Transform one source asset into channel-specific content such as LinkedIn posts, X threads, captions, reel scripts, ca…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / Core Workflow / Deliver” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "content-repurposer" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / Core Workflow / Deliver
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Content Repurposer
Overview
Adapt the message to the channel instead of reposting the same copy everywhere.
Core Workflow
- Extract the core message, audience, voice, proof points, and call to action from the source.
- Decide which formats are needed and what each channel rewards: hook, cadence, depth, or brevity.
- Rewrite for each channel's mechanics rather than merely shortening the original.
- Vary hooks, openings, and structure so the outputs feel native to the platform.
- Keep the central message aligned across all variants.
Deliver
- Produce channel-ready drafts with clear labels.
- Preserve the original voice unless a new one is requested.
- Note any source gaps that weaken credibility or conversion.
Guardrails
- Do not fabricate testimonials, metrics, or outcomes.
- Avoid obvious copy-paste repetition across channels.
- Keep CTAs realistic and matched to the audience stage.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review