Use this AI campaign brief generator to prepare a structured, evidence-linked draft from the facts you approve. With separately verified account access and write permission, its setup can create the working Sheet in your chosen Drive folder. Without access, review the same fields in chat; no saved-file claim is made.
What a complete brief includes
The actual pack uses these fields: Campaign ID, Goal, Audience, Offer, Proof, Channels, CTA, Owner, Due and Status. Working tabs are Requests, Briefs, Review Queue and Activity. Evidence and reviewer questions travel with the draft.
Fictional request and expected answer
Input: Juniper Studio wants demo requests from operations teams. LinkedIn is proposed, but price, proof, owner and due time are absent. Expected: goal and audience filled from that request; Offer, Proof, Owner and Due marked unknown. Suggested reviewer question: "Which offer and evidence are approved, who reviews, and what is the due date and timezone?" No unsupported performance claim or publishing step.
Run it without guessing
- Download and read the three public files.
- Confirm scope, account, folder, reviewer and manual or supported scheduled mode.
- Test the fictional request. Check that unknowns remain unknown.
- Supply approved real inputs and review the exact draft before any external action.
The pack describes a weekday check as a setup option, not a timer installed by downloading. Ordinary chat runs manually unless a supported scheduler is separately configured and approved.
Marketing workflow setup on Copilot · Instinct workflow setup and limits · Prepare the approved campaign calendar
Normalize requests into complete, evidence-linked campaign briefs and review questions. The agent keeps the steps, checks and output consistent, while you keep every decision.
Picture tomorrow's handoff.
"Hello, turn this launch request into a campaign brief"
| Campaign ID | Goal / audience | Offer / proof | Review status |
|---|---|---|---|
| FICTION-001 | Launch demo / operations teams | unknown / unknown | Blocked: approved offer and proof needed |
Sample data. Your agent fills the file from the sources you approve and flags anything it cannot verify.
Included files. One complete workflow.
skill.mdThe full job, evidence rules, output checks and stop points.
setup-prompt.txtChecks the chosen account and folder, defines the working Sheet and tests a fictional row. Creation needs supported tools and permission.
usage-prompt.txtThe short request you reuse whenever the job comes up.
Working in three steps
It checks access and permission before any folder or output file is created.
Use Google by default, or the Microsoft or Zoho alternative.
Unknowns and next decisions are shown instead of guessed.
Where the agent stops
- It does not invent missing facts or hide weak source evidence.
- It does not send, publish, spend, schedule or make a human decision without approval.
- It flags blocked work and tells you exactly what is needed next.
Put this job on a repeatable workflow.
direct download · Keep the files forever · free download
Add the next agent when this job is working
Use the Campaign Brief Agent with your assistant
The same Included files run on any assistant that reads plain text. Pick yours for the step-by-step setup - where the files go, what a run looks like, and the honest limits:
- Microsoft Copilot - With Microsoft 365 Copilot, create a Notebook, add skill.md as a reference and the setup prompt as the custom instructions, then run the setup and approve the sample-data test. With consumer Copilot, upload skill.md at the start of each session instead.
- Hermes - Give Hermes the Included files in its workspace: skill.md becomes the standing skill, then run the setup prompt and approve the fictional-data test. Because Hermes is open-source and local-first, your prompts and outputs stay under your control.
- Instinct - Give Instinct the public skill.md, setup-prompt.txt and usage-prompt.txt. Confirm scope, source access, destination and reviewer, then run a fictional-data test. Files alone do not activate a recurring workflow; any supported schedule needs separate scope and time approval.
- OpenClaw - Drop the Included files into your OpenClaw workspace and point it at skill.md, then run the setup prompt over your usual chat channel. OpenClaw keeps its workspace persistent, so the agent's rules survive between asks, and its approval style matches the agents' stop-at-human-gates design.
- Muse - Give Muse the Included files and ask it to keep skill.md as the standing rules for the job, then run the setup prompt and approve the fictional-data test before pointing it at real work. As with any action-taking agent, keep its approvals on.
- Perplexity - Create a Space for the job, upload the Included files, and paste the setup prompt into the Space instructions. Run the setup, approve the sample-data test, and start each run in that Space. Save the agent's output where your work lives (Sheets, Docs).
- ChatGPT - Create a Project for the job, upload skill.md as a Project file and paste the setup prompt into the Project instructions. Run the setup once, approve the sample-data test, then start each run inside that Project so the rules stay loaded.
- ChatGPT Dots - Create your dot on an eligible desktop account. Give it the included files as readable reference instructions, run the setup prompt and review the fictional-data output. Check plugin permissions separately; local skills require a connected computer. Approve the exact action before sending, spending or changing records.
- Claude - Create a Project for the job and add skill.md as Project knowledge with the setup prompt as instructions. Run the setup conversation, check the sample-data output, then start each run in that Project so the rules stay loaded. Artifacts Claude produces can be saved out to your Drive.
- DeepSeek - Upload skill.md at the start of a chat, paste the setup prompt, and approve the sample-data test. Keep the Included files in a folder you can reach: each new chat starts fresh, so you re-attach skill.md and re-paste the usage prompt per run.
- Town - Share the Included files with Town and ask it to keep skill.md as the standing rules for the job, then run the setup prompt and approve the fictional-data test. Town's email and calendar focus pairs well with agents whose output is a draft, a schedule or a follow-up queue.
- Grok - Attach the Included files to a chat or build a Grok Skill/Bot with skill.md as the standing expertise, then run the setup prompt and approve the fictional-data test. Skills keep the rules persistent between asks.
- Gemini - Create a Gem whose instructions are the skill.md contents plus the setup prompt, then run the setup. Gems keep their instructions between sessions, so the agent's rules persist. For Sheets work, Gemini's Workspace integration makes it the natural home for these agents.
Questions people ask
What does the Campaign Brief Agent actually do?
It normalizes the request into a complete campaign brief in a draft brief, evidence-linked, with the open questions called out for a human to answer. It prepares review-ready work and stops for your approval before anything is sent, spent, published or scheduled.
Which AI assistants work with the Campaign Brief Agent?
Workflow compatibility depends on readable files and the permitted tools. Setup guides: Microsoft Copilot, Hermes, Instinct, OpenClaw, Muse, Perplexity, ChatGPT, ChatGPT Dots, Claude, DeepSeek, Town, Grok, Gemini. Verify the sample output and current account access before real work.
Is the Campaign Brief Agent free to use?
Yes. The agent pack is free to download and keep. There is no site account or renewal.
How long does setup take?
About 10 minutes: attach the files, run the setup prompt, approve the fictional-data test. It never touches real work until you approve the sample run.
Last updated 13 September 2026 · Reviewed by the AI Agent Skills team.