run-campaign
$
npx mdskill add anthropics/knowledge-work-plugins/run-campaignExecutes a full marketing campaign from analysis to asset creation and scheduling
- Solves the problem of launching targeted campaigns based on sales performance
- Uses QuickBooks, PayPal, Canva, and HubSpot for data and asset creation
- Analyzes revenue trends to prioritize content and offers in a 30-day brief
- Delivers approved content assets and staged sends with owner confirmation
SKILL.md
.github/skills/run-campaignView on GitHub ↗
--- name: run-campaign description: Runs an end-to-end marketing campaign — sales analysis, content brief, Canva assets, HubSpot send. Accepts optional lookback and channel arguments. allowed-tools: Read, WebFetch, Bash --- Run the full campaign pipeline by chaining three skills in order. The owner approves at each handoff — never roll past a gate without explicit confirmation. Parse arguments: - `--lookback` (default `90d`) — how far back to look for the revenue dip - `--channel` (default `both`) — `email`, `social`, or `both` ## Step 1 — Sales analysis + content brief (content-strategy) Trigger the `content-strategy` skill workflow: 1. Pull sales data from QuickBooks and PayPal for the lookback window. 2. Identify the revenue dip — which product/service, which time period, magnitude. 3. Produce a 30-day prioritized content brief: what to push, what offer to run, what to hold. 4. Present the brief to the owner. Wait for explicit "approved, build the assets" before continuing. If the owner edits the brief, incorporate edits and re-present. ## Step 2 — Asset generation + send staging (canva-creator) After Step 1 approval, trigger the `canva-creator` skill workflow: 1. Take the approved brief from Step 1 as input. 2. Build the posting calendar matched to the brief's priorities. 3. Generate on-brand Canva assets for each post (apply each on screen for owner approval before moving on). 4. Draft caption copy for each post. 5. Stage the scheduled send in HubSpot (do NOT send — staging only). 6. Present the staged campaign to the owner. Wait for explicit "approved, send to segment X" before Step 3. ## Step 3 — Audience segmentation (lead-triage) After Step 2 approval, trigger the `lead-triage` skill workflow: 1. Pull HubSpot contacts that match the campaign's target segment (from the approved brief). 2. Score by engagement, company fit, urgency markers. 3. Produce two deliverables: - **Bulk send list** — the segment receiving the staged campaign from Step 2 - **High-priority call list** — top 5 leads the owner should call personally with talking points 4. Block calendar time for the call list. 5. Present both lists. Wait for explicit "send" before pushing the HubSpot campaign live. ## Approval gates (must hold) - Never auto-progress between steps. Each handoff requires explicit owner approval. - Never send the HubSpot campaign without the owner's "send" command in Step 3. - If any connector is unreachable (QuickBooks, PayPal, Canva, HubSpot), stop, report which connector failed, and ask whether to retry or abort. ## Output End the run with a one-paragraph recap: revenue dip identified, posts generated, segment size, calls booked. Link to the HubSpot campaign URL once sent.
More from anthropics/knowledge-work-plugins
- accessibility-reviewRun a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
- account-research"Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question."
- analyzeAnswer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
- architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
- audit-supportSupport SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
- brand-reviewReview content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
- brand-voice-enforcement>
- briefGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
- build-dashboardBuild an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
- build-zoom-botBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining Meeting SDK, RTMS, and backend services.