marketing-monday

Run the weekly growth briefing by chaining two skills — growth-pulse for whether the engine is working and review-reputation for what customers are saying — then adding a web-native competitor scan. The three parts feed one merged brief; this is not three reports stapled together.

Connectors: any one of PayPal, Shopify, or HubSpot is enough to run. Apollo, Clay, Mailchimp, Square, Stripe, and TikTok Ads each add a layer. TikTok Ads contributes the paid layer to Step 1 through growth-pulse: last week's spend, results, and cost per result beside the sales trend, reported as the platform's own claim next to the CRM's lead count, never blended (../growth-pulse/reference/data_sources.md). Mailchimp contributes the email channel to Step 1 (its get_capabilities call needs user_request and a category; ../../shared/connector-call-shapes.md) — campaign analytics with revenue attribution and audience-growth numbers. It is read-only in this brief: nothing is drafted or sent from here, and its attributed revenue is reported as the email channel's own claim beside the platform and CRM numbers, never blended into one figure. With none of them, CSV exports and pasted reviews go in, and the competitor scan runs web-native with no connector at all.

Default window: the last 7 days for the pulse, the last 90 days for reviews, and since the last run for the competitor watchlist.

Step 1 — Is the engine working (growth-pulse)

Trigger the growth-pulse skill workflow. Pull every connector in one parallel batch; a serial run is a wait nobody sits through twice.

In: whatever is connected, or exports. Out: channel trend, funnel conversion, campaign return, product performance, and sentiment — each with a status, and anything missing marked "n/a" rather than silently dropped.

Handoff: carry forward the single sentence that explains the period, plus the biggest drop-off in the funnel and any product carrying the whole trend. Do not carry the full five-view dashboard into the merged brief.

No gate here. The command was invoked; run it. Reading data is not an approval-worthy action.

Step 2 — What customers are saying (review-reputation)

Trigger the review-reputation skill workflow.