Build a Weekly Marketing Metrics Review That Writes Itself in Claude Cowork

Start by creating a folder for the weekly review. Keep the structure simple:

`marketing-metrics-review/`, `inputs/`, `working/`, `outputs/`, and `skills/`.

`inputs/` is where Claude will collect the raw material: sales data, revenue numbers, Slack summaries, and meeting note summaries. `working/` is where Claude can create drafts, source checks, and intermediate notes. `outputs/` is where the final report, leadership brief, Slack update, action items, PDFs, and slides should land.

The point is not to create a fancy file system. The point is to give Claude a predictable place to look every time the workflow runs.

Pro tip: keep this in a repo if you can. It makes it much easier to see what changed week to week, recover older reports, and avoid overwriting something important.

The first skill should prepare the inputs. Do not make it write the report yet. Its job is to gather and summarize the raw material.

Use a prompt like this:

Create a skill that prepares our weekly marketing review inputs. It should summarize last week's Slack messages, look at my Gmail for sales updates, check our revenue numbers in Google Analytics, pull in meeting notes from Google Drive, and save the summaries in inputs/.

Your inputs will probably look different. You might use HubSpot instead of Gmail, a spreadsheet instead of Google Analytics, or a Notion doc instead of Google Drive.

Before you finalize the skill, ask Claude:

Look at the connectors I have available and suggest the best weekly marketing review inputs you can gather automatically.

That one extra question is worth doing. Claude may have access to useful context you forgot about, and it can help you avoid building the workflow around the wrong sources.

The second skill should turn the inputs into a first draft.

Keep this prompt simple:

Create a skill that looks at the inputs and creates a first draft of the main marketing report, the leadership brief, the Slack update, and the action items.

Once Claude writes the skill, add one important rule: it should separate facts from interpretation. If a number comes from Google Analytics, Slack, Gmail, or a meeting note, Claude should say where it came from. If two sources do not line up, it should flag the mismatch instead of smoothing it over.

For example, your sales team might want the report organized by customer segment, while your export still uses old campaign groups. That is exactly the kind of mismatch you want Claude to catch before it writes a polished report.

Run the input skill first. That should create or update the source summaries in `inputs/`.

Then run the reporting skill. Ask Claude to create the first draft, but do not let it treat the first draft as final. Review the story before it expands the report.

Use a direction like this:

Use the inputs to draft the weekly marketing review. Focus the story on pipeline quality and Q2 readiness. Keep source-backed facts separate from interpretation, and flag anything that needs human approval before the final report.

After you approve the story, Claude can create the final report, leadership brief, Slack update, and action items.

Pro tip: do not skip the approval step. Claude can find patterns, but you still own the management judgment. The best workflow is not fully automatic writing. It is automatic prep, human-approved story, then automatic packaging.

The Markdown files are useful, but they are usually not the final format people want.

Create one more skill for publishing:

Create a publishing skill that turns final Markdown reports into PDFs and the leadership brief into a Google Slide. Save files in outputs/final/. Archive last week's outputs.

This keeps the writing workflow separate from the delivery workflow. The reporting skill creates the substance. The publishing skill turns it into the format people will actually read.

You can also automate the publishing step after the report is approved. For example, Claude can generate the PDFs, create the slide, archive last week's files, and prepare a Slack-ready summary.