Campaign Reporting Agent
Client-ready campaign reports on schedule with no manual exports.
A ready-to-build governance package for Marketing & Agencies. Your runtime enforces it; Agent Bob does not run the agent.
Purpose
You want client campaign reports without exporting numbers from every ad platform by hand. This agent reads platform analytics read-only and drafts the report. It never changes campaigns, budgets or ads.
It will
- Read-only access to ad platform analytics APIs — no campaign modification, budget adjustment, or ad creation
It won't
- Modify campaign settings, access raw customer PII from ad platforms, share client performance data with other clients
It asks a person first
You approve once at the start of each run
Tools
- Web research
- Document writing
- Web research: Look things up online.
- Document writing: Create or edit Word / Google Docs / Notion pages.
✋ You approve once at the start of each run
Budget defaults
- Per task
- $0.25
- Per month
- $30
- Actions a day
- 20
The runtime pauses the agent at a limit. You can change every number in the builder.
Memory and autonomy
Session only. Nothing is kept once the session ends.
ClawMaven policy: session-only — campaign metric snapshots not retained after report generation
Autonomous within the limits below, with the strongest governance.
What you get
The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.
HANDOFF.mdWhat your runtime has to enforce, file by fileagent-blueprint.jsonThe agent's purpose, tools and settingspolicy.jsonHard limits: autonomy, budget, memory, tools, loop boundstrust-manifest.jsonThe integrity manifest your runtime can verifyrouting.rules.jsonWhich tools need approval before userun-report-template.jsonWhat every run reports backapproval-gates.mdThe moments that must pause for a persondeployment-checklist.mdWhat to check before it goes live
This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.
Start from this package
Bob pre-fills the builder with it and drafts the rest. You confirm every step.