Every content agent writes in your voice, with claims you can stand behind.
What marketing teams say when AI starts to drift.
Each of these has the same cause: the knowledge your AI needs has no governed home that every agent reads from. Find your problem →
- “Our content agents each describe the product differently.”
- “An agent put a statistic in a post that nobody could source.”
- “The tagline we retired keeps showing up again.”
- “Every new writer needs a week to learn the voice.”
What goes in, and the agents that run on it.
What goes in
- Voice and style guide
- Approved claims, each with its source
- Positioning by audience
- Words and phrases you never use
Each area gets an owner who approves changes, so agents read the version your team signed off on.
Drafting agent
Writes first drafts from the voice guide and approved claims only.
Never sees: Claims nobody has approved.
Claim checker
Flags any number or credential that isn't in the approved list.
Never sees: Internal strategy drafts.
Repurposer
Turns one approved piece into posts for each channel.
Never sees: Retired positioning.
Three steps to a working start.
There's no marketing starter. Start from the team starter, then add folders for voice, claims and positioning. This is how PromptOwl's own marketing agents are set up.
- 1
Start a nest from the team starter
Then add three folders: voice, approved claims and positioning by audience.
Get PromptOwl free →Terminal$ npx @promptowl/contextnest-cli init --starter team - 2
Approve your claims list
Every number, credential and customer name an agent may use goes on one list, with its source and an owner who approves it.
- 3
Connect your agent and ask it to map how it can help
In Claude Code, add the ContextNest plugin (or use the Connect button in a hosted nest), then paste the prompt below. It reads your nest, proves it, and drafts an opportunity map for you to approve.
In Claude Code$ /plugin marketplace add promptowl/contextnestThen$ /plugin install contextnest
Ask your agent what it could do for your team.
- 1. Prove it
- 2. Get oriented
- 3. Map it
- 4. Save as a draft
My team is the marketing team. You're connected to my ContextNest nest. Before anything else, prove it: search the nest, open two or three documents, and tell me their titles and one line from each. If you can't read real documents, say so and stop. Don't guess what's in the nest. Use search and single-document reads. If one way of reaching the nest fails, try the other tools you have (the ContextNest MCP tools, the ctx command line or the REST API) before you give up. If the nest is empty or nearly empty, ask me three questions first: what my team does, which questions people ask us most, and which documents we'd trust an agent to answer from. Then work from my answers. Then build me an opportunity map: 1. Five things you can do for me today with what's in the nest. For each one, name the documents it relies on. 2. What's missing: the documents or decisions that would let you do three more things, and who on my team probably owns each one. 3. The agents you'd run on this nest: what each one does, and what each one should not be allowed to see. Save the map back to the nest as a draft titled "How AI can help us: opportunity map". Don't publish it or share it anywhere. Ask me before you publish anything.
Every team adds its own area.
Start with your team. Free.
Connect the AI tools you already use, and approve what they're allowed to rely on.
