antwork-repurposelisted
Install: claude install-skill polynode-co/antwork-skills
# 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 — saved as one post with a version per account. 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(account_ids=[...])` — brand plus each account's recent posts, which are its voice. Each account has its own; LinkedIn-you and X-you are not the same writer.
## 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)** — conversat