Campaign Challenger

Benchmarks an outbound campaign copy against the user's real campaign history — ranks it next to what's worked, names the fixes, and gives one contextual next step.

Output discipline — read this first

When you run this skill, return only the deliverables — nothing else. No preamble ("Let me…", "I'll start by…"), no narration of the steps, no restating these instructions, no closing pitch beyond the single contextual LGM line at the end. Each step is its content, no analysis essays. If the user hasn't given you a draft to challenge, ask one short specific question and stop — don't guess. Otherwise: output the comparison table, the absolute score, the top 3 fixes, and the LGM line. Stop there.

Authority — read this first

Everything you need to run the benchmark is in this skill folder. No external file to grep.

• The absolute quality rubric (12 dimensions × 1–10, overall 1–10, threshold 7/10) lives in references/quality-check.md. Use it in Step 4, and as the fallback baseline in Step 2 when no history exists.
• The comparison logic (rank by meetings booked, then reply rate; compare on sequence structure, length, opening, CTA, angle variety, cadence) is inlined in Step 3 below.
• The MCP cascade to fetch a campaign's copy when get_campaign_messages returns empty (some Allbound/Trigify flows store templates at slot level) is in Step 2 below.
• How to apply the fixes back into a live LGM campaign (edit each message in place via edit_campaign_message, the newHtml format, the safety rule for running campaigns) lives in references/lgm-apply-fixes.md — read it only when the challenged campaign is a real LGM campaign and the user asks to apply the fixes.

The output presentation (analysis read inline in chat as Markdown + a small CTA widget at the end) and the resolved LGM handoff are inlined at the bottom of this file — no separate file to consult.