antwork-campaignlisted
Install: claude install-skill polynode-co/antwork-skills
# Running a campaign with Antwork
A campaign is a sequence of posts (beats) scheduled across days toward a single goal. Each beat is its own post, with a version per account that carries it; the beats are tied together by the plan and a per-post `goal`, not by a shared id. The work is to design the arc first, get approval, then create and schedule the sequence. This workflow codifies the mistakes assistants make when coordinating multi-post pushes.
## 1. Define the campaign before drafting
Pin down the brief before any copy. Capture it in `templates/campaign-brief.md`:
- **Goal** — what the campaign should achieve (signups, attendance, sales, awareness) and the single success metric.
- **Window & cadence** — start/end dates and how many posts on which days.
- **Audience & key message** — the through-line every post reinforces.
- **Platforms/accounts** — which `account_id`s (check `list_social_accounts`; skip unhealthy tokens).
For launch-shaped campaigns, use `templates/launch-week.md` for the classic arc: pre-launch teasers → launch-day push → follow-up / social proof.
## 2. Pull context and design the arc
- `list_posts(date_from, date_to, group_by_day=true)` — so the campaign weaves around existing posts, not on top of them.
- `get_post_context(account_ids=[...])` — brand, default posting times and timezone, plus each account's recent posts, which are its voice. One call for every account in the campaign.
Design the sequence so each post has a distinct job (tease →