Pace
← All cookbooks Marketing cookbook

Marketing

Weekly campaign brief. Content drafting that knows your brand voice. Performance reports you don't have to assemble.

Marquee recipe

Weekly campaign performance digest, Fridays at 4pm

The marketing team walks into Monday already aligned on what shipped last week.

Trigger
Routine, schedule, weekly Friday 16:00
Skills
performance-report, write-query
Features
Routines (cloud schedule), Amplitude + HubSpot connectors, cross-plugin chain

The team walks into Monday already aligned on what shipped last week and how it performed. The digest is in #marketing-weekly by Friday afternoon, pulled from Amplitude funnels and HubSpot lead sources without anyone touching a spreadsheet.

How to set it up

  1. 1
    Install marketing + data plugins

    Marketing has the report skill; data has the SQL skill it leans on.

    Install in Cowork ↗ npx pace-tools install marketing data
  2. 2
    Authorize Amplitude, HubSpot, and Slack

    The first time you run any marketing or data skill, OAuth windows open one by one. Sign into each once. Amplitude is the analytics source; HubSpot is the CRM; Slack is where the digest lands.

  3. 3
    Create the scheduled routine

    In Cowork, open Routines → New routine. Pick Schedule, set to Weekly · Friday · 16:00.

  4. 4
    Paste this as the routine prompt

    Edit the channel name and the metrics list to match your team's KPIs.

    Routine prompt 
    Run performance-report covering the past 7 days.
Pull funnel metrics from Amplitude (signups, activations,
free-to-paid conversion) and lead-source attribution from
HubSpot. Use write-query if you need to grab anything
the report skill doesn't have directly. Format as a Slack
digest: headline numbers at the top, week-over-week deltas,
top 3 campaigns by impact, anything anomalous worth a closer
look. Post to #marketing-weekly.
  5. 5
    Click Run now to verify

    First run takes a few minutes (it has to authenticate Amplitude on the cloud side too). The digest lands in #marketing-weekly. Future Fridays at 16:00 are automatic.

Brand-voice gate on every external draft

Trigger
Routine, GitHub trigger on pull_request.opened in the marketing repo
Skills
brand-voice-enforcement, draft-content
Features
Routines (GitHub trigger), brand-voice plugin, inline PR comments

Any PR that touches landing pages, blog posts, or email templates auto-runs brand-voice-enforcement and posts inline comments with concrete fixes. Catches drift before it ships; pair with draft-content when a section needs a rewrite from scratch.

Auto-build the launch comms kit when a Linear cycle ships

Trigger
Routine, GitHub event when a release branch merges to main
Skills
draft-content, brand-voice-enforcement
Features
Routines (GitHub event), Linear + Notion connectors, plan mode for review

When a release branch merges, the routine reads the cycle's shipped issues, drafts the announcement post, the changelog entry, and the customer-facing one-pager in one go. Brand-voice enforcement runs over each artifact. Everything lands in Notion under a single page for your review before anything goes out.

How to set it up

  1. 1
    Create the GitHub-triggered routine

    In Cowork, open Routines → New routine → GitHub event. Pick the repo and event described in the trigger above. The Claude GitHub App is offered as part of setup; install it on the relevant repo.

  2. 2
    Paste this as the routine prompt
    Launch comms prompt 
    When a release branch merges to main, read the shipped issues from Linear in that cycle. Draft the launch comms kit in Notion under a single page:

1. A blog announcement post (in our brand voice).
2. The changelog entry for the public release notes.
3. A customer-facing one-pager.

Run brand-voice-enforcement over each artifact. Park everything in plan mode for the marketing lead's review before anything goes out.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.

Weekly content calendar generated from the strategy doc

Pull the quarterly themes from your strategy doc, the upcoming product launches from Linear, and any event tie-ins from the calendar. The routine drafts a week of planned posts across blog, social, and email (with platform-specific drafts for each), parks them in plan mode for review, and posts the calendar to #content for visibility.

Trigger
Routine, schedule, weekly Wednesday 13:00
Skills
campaign-plan, draft-content
Features
Routines (cloud schedule), Notion + Linear connectors, plan mode for review

How to set it up

  1. 1
    Create the scheduled routine in Cowork

    In Cowork, open Routines → New routine → Schedule. Match the cadence described in the trigger above.

  2. 2
    Paste this as the routine prompt
    Content-calendar prompt 
    Every Wednesday at 1pm, pull the quarterly themes from the strategy doc in Notion, upcoming product launches from Linear, and any event tie-ins from the calendar. Draft a week of planned posts: one blog topic, three social posts (LinkedIn + X + threads versions), one email to the newsletter list.

Park the calendar in Notion plan mode for the marketing lead to review, then post the approved version to #content for the week.
  3. 3
    Click Run now to verify

    Eyeball the first run for accuracy. Once it looks right, the routine fires on its trigger from then on. Assumes the plugin from the marquee above is already installed and connectors authorized.