Rebuilding the same document every time a new program launches? This free Claude skill for Marketo builds campaign briefs.
Every time a new Marketo program gets created, there's a task waiting for you on the other side of it.
You need a briefing document. Not a rough outline — a real, formatted, stakeholder-ready doc that maps every program token to a fill-in field, broken out by asset, labeled in plain English, and styled to your brand standards. The kind of document your copywriters and campaign managers can actually use without pinging you with three follow-up questions.
So you open the program. You catalog the tokens. You rebuild the table structure you've built a hundred times before. You rename {{my.Hero-CTA-Copy}} to something a human can read. You match the fonts, check the colors, and double-check that you didn't miss anything.
An hour later — maybe two — you have a briefing doc. And somewhere in the background, another program just got created.
This is what marketing operations looks like before automation. It's not hard. It's just constant.
We built something to change that.
The Campaign Briefing Document Builder is a free Claude skill built by allGood — a Claude Marketo integration that turns program tokens into stakeholder-ready campaign briefs. You give it a campaign name. It talks directly to your Marketo instance, pulls every token from the program, figures out your campaign structure, and outputs a fully formatted, brand-compliant Marketo briefing document — ready for handoff.
What used to take an hour or two now takes minutes. It lets you automate Marketo campaign briefs end to end — no manual token cataloging, no reformatting tables, no translating Marketo-speak into something your copywriter understands.
It runs inside Claude, it's free, and it was built specifically for marketing operations teams running Marketo programs.
New to Claude skills? Check out our quick setup guide to get installed and ready in under two minutes.
You can customize the output and prompt Claude directly at any step. Need just Email 1 for now? Ask for it. Want a quick brief without the instructions section? You'll get that too.
Here's what happens when you ask for a Marketo briefing document:
Type the campaign name. Claude searches your Marketo instance directly and locates the right program. One match — it confirms and moves on. Multiple matches — it shows you the list and asks you to pick. Nothing comes back — it broadens the search automatically.
No logging into Marketo. No copying program IDs. Just type the name.
Once it has the program, Claude pulls every token — name, type, and current value — along with every email asset in the program. From there it determines the campaign structure on its own: single email, multi-touch series, or event plus landing page.
It also maps tokens to their deliverables automatically. Token names that include an em2- prefix belong to Email 2. em3- goes to Email 3. Everything else belongs to Email 1 or is shared. Claude reads the naming convention and figures out the structure without you having to explain it.
Before building anything, it surfaces a quick summary and asks you to confirm:
The skill reads a formatting reference file — briefing-format.md — that encodes your brand standards: fonts, colors, table widths, margin sizes, how tokens should be labeled. It builds your Marketo campaign brief template to your spec, not a generic layout.
The output is a structured Word document with three things that make it genuinely useful for stakeholders:
The 3-line label structure. Every token row shows three lines in the label column: a plain-English field name in bold at the top (so your copywriter knows what to write), the Marketo token name below it in gray (so your builder knows exactly where it maps), and a short helper note below that in smaller gray text (so neither of them has to ask you what it means). All generated automatically. All consistently formatted.
Pre-populated values. If a token already has a value set in Marketo, it comes through pre-filled in the doc. Your team sees what's already locked in and only needs to fill in what's missing.
Visual marker numbers. Each row in the content table gets a pink numbered marker — Subject Line is 1, Preheader is 2, Banner Image and Banner URL are both 3 (grouped because they go together), Headline is 4, and so on. Related fields share the same number and the same row background color. When you drop a screenshot of the email design into the doc, your stakeholders can match field 3 in the table to element 3 in the design without any guesswork.
The doc structure adapts to your campaign type as well. A single email gets one content section. A three-email nurture gets three, each organized by its token prefix. An event program with a landing page gets separate sections for shared event details, email content, and landing page content.
Before anything gets handed off, the skill runs through a 20-point validation checklist — confirming that every token from the program is present, pre-populated values match the source data, formatting is applied correctly, and nothing is mislabeled or missing. If anything fails, it fixes it and reruns the checklist.
Then you do a quick review, run a test build with Mary to confirm every token populates correctly, and hand it off. That's the whole process.
The skill works without it.
If you're not yet connected to Marketo through Claude, take a screenshot of the My Tokens tab in your Marketo program and drop it in. The skill reads the screenshot, extracts every token name and value it can see, infers the campaign structure from the naming convention, and builds the exact same briefing doc from there.
You lose the automatic pull, but you keep everything else. Same formatting, same label structure, same validation — just with a screenshot instead of a live connection.
We're also releasing a companion skill alongside this one — also free.
If you've ever received a Google Doc or Word file full of campaign copy that isn't formatted for your briefing template, you know what comes next. Manual translation. Field by field, line by line.
The Content-to-Brief Formatter takes that unstructured document and automatically maps the content into your existing briefing doc format — so Mary gets content in a format she can use, and you skip the reformatting entirely.
Two skills. Both free. Both built to give MOPs teams their time back.
Honest answer: Marketo briefing documents are one of those tasks that should have been automated years ago. The data is already in Marketo. The format doesn't change. The translation from token name to human label is purely mechanical.
But because it's tedious rather than hard, it just keeps getting done manually. Every new program. Every single time.
We think the best use of a marketing operations professional's brain is strategy, not reformatting tables. So we built the tool to handle the table reformatting — and made it free, because the whole program runs better when your team isn't buried in busywork.
Your token data is already in Marketo. Your brand standards are already documented. The only thing missing was a Claude Marketo integration to connect them automatically.
Download the Campaign Briefing Document Builder — free →
Any Marketo program with tokens. Email programs, engagement programs, default programs — if it has tokens, the skill can build the brief.
No. If you're not yet connected, upload a screenshot of your My Tokens tab and the skill builds from there. The live connection just makes it faster and fully automatic.
With the allGood integration enabled, Claude can query your Marketo instance directly — searching for programs by name, pulling all token data, and fetching email asset details — without you needing to export or copy anything manually. It's the same information you'd find in Marketo, just pulled automatically so you don't have to.
Yes. The skill reads a formatting reference file that encodes your specific brand standards — fonts, colors, table widths, token labeling conventions. It builds to your spec, not a generic template.
Single email, multi-touch email series, and event plus landing page campaigns. The skill detects the campaign structure from the program's assets and token naming, then structures the doc accordingly.
Typically a few minutes from start to finish — including pulling from Marketo, generating the doc, and running the validation pass.
No. You just need Claude Desktop and the allGood marketplace plugin installed. The skill is free and available to anyone.
Yes — by design. After the skill builds the doc, you do a quick review and run a test build with Mary to confirm all tokens populate correctly. The manual work goes from an hour to a few minutes. The human check stays in.
The Content-to-Brief Formatter takes unstructured copy — a Google Doc, a Word file, a content brief — and maps it into your briefing doc format automatically. It's for teams that receive raw copy from writers or stakeholders and need to get it into a format Mary can use, without doing it by hand.
Install the free Campaign Briefing Document Builder skill in Claude Desktop. Once connected to your Marketo instance, it pulls program tokens automatically, maps them to a formatted campaign brief template, and outputs a stakeholder-ready document in minutes. No manual token cataloging or table formatting required.
Yes. The skill connects Claude directly to your Marketo instance through the allGood plugin, allowing it to search programs, pull token data, and fetch email asset details — all without leaving Claude Desktop. It's a native Claude skill for Marketo, not a third-party workaround.
Book a 1:1 demo and meet your new favorite (AI) employee.
