# Antwork Repurpose > Use when the user wants to turn ONE piece of source content into platform-native posts through Antwork — a blog post, newsletter, long LinkedIn post, podcast/video transcript, or talk reshaped into versions for each platform. Trigger on phrases like "repurpose this", "turn this blog into posts", "make this into a LinkedIn + X + Threads version", "atomize this content", "spin this into social", or pasting long-form content and asking to distribute it. - Skill: `iker-gonzalez/antwork-repurpose` (Agent Skill) - Install (CLI): `npx skillmds@latest add iker-gonzalez/antwork-repurpose` - Raw SKILL.md: https://api.skillmd.com/api/skills/iker-gonzalez/antwork-repurpose/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: iker-gonzalez (https://skillmd.com/u/iker-gonzalez) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/iker-gonzalez/antwork-repurpose --- # Repurposing one piece into platform-native posts Antwork binds each post to a single account, and platform is derived from that account. Repurposing means writing a *distinct, native* version per platform — never one body copy-pasted everywhere — and grouping them under a shared `campaign_id`. This workflow codifies the mistakes assistants make when atomizing content. ## 1. Anchor the source Identify the one source piece and its core idea. If the user hasn't pasted it, ask for the text, URL, or transcript. Extract the spine before reshaping: - The single biggest claim or takeaway. - 3–5 supporting points or moments that can each stand alone. - Any quotable line, stat, or hook. This spine is what gets reshaped per platform — not the prose itself. ## 2. Pick targets and pull each voice Confirm which accounts to publish to (`list_social_accounts` if unsure — note `account_id`, platform, token health). For **each** target platform, before writing: - `get_post_context(platform, account_id)` — brand, that account's voice profile, recent posts, `voiceStale` flag. Each account has its own voice; LinkedIn-you and X-you are not the same writer. If `voiceStale`, say so and offer the `antwork-voice` refresh first. ## 3. Reshape — do not reuse Write a **native variant per platform**. Reusing one body across platforms is the core failure: X's 280-char cap mangles LinkedIn prose, and LinkedIn-length paragraphs look broken on Threads. Reshape for each: - **X (280)** — the sharpest single claim, or a thread broken into beats. No fluff. - **Threads (500)** — conversational, one idea, lighter than LinkedIn. - **LinkedIn (3000)** — room to tell the story; hook line, whitespace, a takeaway. Longer (300–600 words) is fine *only here*. - **Instagram (2200)** — caption that works under a visual; front-load the hook. - **Facebook / YouTube / Pinterest / TikTok** — match the platform's norm and limit. Honor every hard limit (X 280, Threads 500, Pinterest 800, IG 2200, LinkedIn 3000, TikTok 4000, YouTube 5000, FB 63206) — `schedule_post`/`publish_post` reject anything over. Match the voice profile's tone, emoji and hashtag policy, and CTA style per account. Avoid AI tells ("Here's the thing:", "Let me break it down", emoji-heavy openers). Capture the brief in `templates/campaign-brief.md` if the user wants a record of the repurpose set. ## 4. Create as one grouped set Generate a single `campaign_id` for this repurpose batch and create one draft per platform with it: - `create_post(text, account_id, hashtags?, goal?, campaign_id="")` for each variant. The shared `campaign_id` keeps the variants grouped so they can be tracked, compared, and cleaned up together. `create_post` only makes DRAFTS — nothing is live yet. ## 5. Present, pick, ship Show the drafts side by side (platform → variant) and let the user edit or drop any before anything goes out. Then per the user's intent: - **Schedule**: `schedule_post(post_id, scheduled_for)` (ISO 8601) — stagger across the day/week using `get_optimal_posting_times` rather than firing all variants at once. - **Publish now**: `publish_post(post_id)` — it returns live URLs per platform; report them back, one line per account. Never claim a variant is "posted" after only `create_post`. Complete the second step. ## 6. Media carries over, but per platform If the source has an image or video, attach the right asset to each variant — `attach_media(post_id, media_urls)`, or `upload_media(image_url)` first for a public/AI-generated image. Don't assume one aspect ratio fits every platform; flag when a visual needs reformatting for, e.g., Instagram vs. LinkedIn.