Localized reading guide
marketing-mondayPurpose, usage and source
Delivers the weekly growth briefing as one merged read — whether the growth engine is working, what customers are saying in public and private, what competitors actually changed, and the three growth actions worth taking this week. The growth twin of the Monday brief, chaining growth-pulse and review-reputation and adding a web-native competitor scan, merged into a single page rather than three reports. Offers to run on a weekly cadence once, and sets it up on a yes. Use this whenever the owner wants a recurring or one-off growth check, including phrasings like "how's marketing doing," "growth check for the week," "give me my Monday growth brief," "what should I be doing about growth this week," "are we winning or losing out there," or "set up a weekly marketing update." Reach for it when the owner asks how the business is growing rather than how it is paying its bills.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/marketing-monday/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Delivers the weekly growth briefing as one merged read — whether the growth engine is working, what customers are saying in public and private, what competitors actually changed, and the three growth actions worth taking this week. The growth twin of the Monday brief, chaining growth-pulse and review-reputation and adding a web-native competitor scan, merged into a single page rather than three reports. Offers to run on a weekly cadence once, and sets it up on a yes. Use this whenever the owner wants a recurring or one-off growth check, including phrasings like "how's marketing doing," "growth check for the week," "give me my Monday growth brief," "what should I be doing about growth this week," "are we winning or losing out there," or "set up a weekly marketing update." Reach for it when the owner asks how the business is growing rather than how it is paying its bills.
How the upstream workflow works
Overview
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).
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. In: public reviews, PayPal disputes, HubSpot tickets, complaint-language email threads, and pasted or exported reviews when nothing reads them directly. Out: three to five themes with verbatim quotes, reviews needing a reply, and customers who have gone quiet. Handoff: carry forward the themes and the rating direction. Carry the drafted replies as a separate approval queue, not as brief content. Gate: nothing posts publicly without the owner reading it first, one review at a time. This gate survives the chain intact — a merged brief does not become blanket approval to reply on the owner's behalf.
Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Overview
- Step 1 — Is the engine working (growth-pulse)
- Step 2 — What customers are saying (review-reputation)
- Step 3 — What competitors did (web research)
- Step 4 — Merge into one brief
- Step 5 — Offer the cadence, once
- Approval gates (must hold)
- What not to do
- Output
- Closing offer
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
706f7f307c5ea0941598ad482466c398b0857ec8fcc7739227c0e4ccff502979