campaign-reportlisted

Generate a per-campaign marketing performance report (pipeline + content + funnel) for the board: a two-funnel (New Business / Account Management) HubSpot analysis built from a manual lead sweep reconciled three ways, destination-dated conversions (monthly counts, quarterly and YTD rates), GA4 traffic on one unified campaign page set, edition-over-edition deltas, and a board key takeaway. Markdown source + self-contained HTML; optional gated publishing step. Use when the user says "/campaign-report", "campaign performance report for [campaign]", "build the [X] campaign report", or wants one campaign's marketing and pipeline performance packaged for leadership. NOT the monthly board snapshot (marketing-monthly) and NOT the company-wide RevOps diagnostic (pipeline-analysis). Company, CRM ids, page sets, templates, and publishing targets come from a client context pack chosen per run; nothing client-specific lives in this skill.
risukisu/marketing-skills · ★ 4 · Data & Documents · score 77

Install: claude install-skill risukisu/marketing-skills

# campaign-report — per-campaign performance report Produces, for **one campaign** over a period (default: YTD): a **markdown source**, a self-contained **HTML report** in the client's design system, and, when the pack defines a target and the owner says go, **ships it**. Funnel metric definitions are `pipeline-analysis/definitions.md`; do not redefine them here. **Paths.** `references/…` is relative to this skill's folder. Every output, template, and publishing path comes from the client pack, never from the current directory. ## Step 0 — Client context (every run, ask before reading) 1. List candidate packs: `references/*-context.local.md` here and in the sibling `pipeline-analysis/references/`, plus anything in the launch directory that looks like campaign context (a campaign README, a content plan, an earlier `*-performance-*.md`). Filenames only. 2. Ask one question: use this pack / point me elsewhere / paste the essentials / start with none. Wait. 3. Read only what was approved. "None" means Step 1 also collects portal id, funnels, GA4 property, and output path, and the run renders in the neutral default style. 4. No pack yet? Copy `pipeline-analysis/references/context-pack.TEMPLATE.md` to `references/<client>-context.local.md`, fill it with the user, verify ids live, continue. ## Critical rules 1. **No fabrication.** Every number traces to a CRM or analytics query. Empty result → say so. 2. **Attribution = the manual sweep is the source of truth.**