// execute

AI Marketing Governance

Use when a marketing team has adopted AI faster than anyone wrote rules for it — deciding which tools are approved, what must never go into a prompt, who reviews before publish, and how AI-drafted claims get fact-checked. Also use when the user mentions AI policy, AI governance, AI usage rules, AI disclosure, hallucinated citations, fake statistics, made-up sources, prompt data leakage, "is it safe to put this into ChatGPT", or reviewing AI-written marketing copy. Produces an adoption-readiness verdict, a completed policy with a named owner, and a per-claim citation check applied before anything publishes.

ExecuteengineIntermediate
bash
$npx skills add sarojkjha/aaj-marketing-skills --skill ai-marketing-governance
Or run it in Claude or ChatGPT through the AAJ engines connector

How to install and run this

Install it in your project:

npx skills add sarojkjha/aaj-marketing-skills --skill ai-marketing-governance

No install? Add https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp as a custom connector in Claude, ChatGPT or any MCP client.

https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp

Then ask: Use the AAJ ai-marketing-governance skill on my numbers.

Step-by-step for every agent, Windows, Mac and Linux →

Claude Code

/plugin marketplace add sarojkjha/aaj-marketing-skills
/plugin install aaj-marketing-skills@aaj

OpenAI Codex

codex plugin marketplace add sarojkjha/aaj-marketing-skills
codex plugin add aaj-marketing-skills@aaj

Claude or ChatGPT — no install

Add this as a custom connector:

https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp
Recipes: vendor data in, a verdict out

// when to use it

Use when a marketing team has adopted AI faster than anyone wrote rules for it — deciding which tools are approved, what must never go into a prompt, who reviews before publish, and how AI-drafted claims get fact-checked. Also use when the user mentions AI policy, AI governance, AI usage rules, AI disclosure, hallucinated citations, fake statistics, made-up sources, prompt data leakage, "is it safe to put this into ChatGPT", or reviewing AI-written marketing copy. Produces an adoption-readiness verdict, a completed policy with a named owner, and a per-claim citation check applied before anything publishes.

// what you give

Which AI tools the team uses and for what, whether the plan trains on inputs, who reviews before publish, and the claims and citations in a draft

// what you get

A readiness score with the gaps named, a filled-in policy with owners and a review date, a per-citation verdict, and the five rules as a card the team can pin up

Engine spec

// decision it supports

Is our team ready to publish AI-drafted marketing work, and does each citation in a draft meet the rules before it ships?

// inputs

Which AI tools the team uses and for what, whether the plan trains on inputs, who reviews before publish, and the claims and citations in a draft

// output

A readiness score with the gaps named, a filled-in policy with owners and a review date, a per-citation verdict, and the five rules as a card the team can pin up

// acts or analyzes

Analyzes only

Makes no network calls, writes no files and changes nothing in your tools.

// where your information goes

How you run itWhere your inputs go
Skill installed in your agent, or the local MCP serverThe engine runs on your machine and AAJ receives nothing. Your AI agent still sends what you give it to its model provider (Anthropic, OpenAI and so on), under your own account's terms.
Hosted MCP serverYour agent's model provider, as above, plus AAJ's server on Cloudflare, which receives the engine inputs over HTTPS, runs them in memory and keeps no copy. Cloudflare keeps error logs (no inputs) for up to 7 days.

No engine needs customer names, emails or other personal data; leave them out.

// limitations

  • It is a rule check, not a fact checker. A citeable verdict means the citation has the right parts; it cannot tell whether the study exists. It does not replace legal or compliance review.
  • The draft sweep only spots figures written with %, "percent", "x" or $. Plain counts such as "110 startups" go unflagged, so read the draft for every number.
  • Readiness credits tools only against the engine's six task labels, matched exactly, and scores what you say was verified. It cannot see your plan's real training setting.
  • Give {check, input}; with no input you get a labelled demo. An unknown check or top-level field stops the run, but fields inside input that it doesn't know are ignored, so use the names in the header.

// review before acting

The named reviewer opens every cited document before publish, and the policy owner checks the training-on-inputs setting on the plan itself. Legal or compliance reviews disclosure, data and claims rules for your markets.

// setup

install
$npx skills add sarojkjha/aaj-marketing-skills --skill ai-marketing-governance
hosted mcp
$https://aaj-engines-mcp.sarojkjha10.workers.dev/mcp

Agents listed: Claude Code, Cursor, OpenAI Codex, Windsurf, Cline. Tested and recorded: Claude Code, OpenAI Codex (Windows, ab-test-significance only).

Full spec on GitHub

AI Marketing Governance

AI can get a marketing team to a draft far faster than it could get there alone. What it cannot do is take responsibility for what goes out. This skill is the set of checks that sit between the draft and the publish button.

One principle carries everything: AI drafts. People decide and sign.

When to use

The team has started using AI on company work with no written rules, a founder wants a policy they can adopt this week, someone is about to publish AI-drafted content, or a figure in a draft needs checking before it ships.

Do not use this to write an aspirational AI ethics statement. A policy nobody owns is a document, not a policy — every section here ends in a name.

Before you start

  1. Read the brand/product context first (.agents/product-marketing.md / .agents/aaj-brand.md).
  2. Get the actual tool list, by task and by person. "AI" is not a tool, and a policy that does not name them cannot be followed.
  3. Get the plan tier for each tool, because whether it trains on inputs depends on it. Business and enterprise tiers usually do not; consumer tiers often do, and the default is rarely the safe one. If the user does not know, that is the first finding, not a blocker to note later.
  4. Get the reviewer's name. Not "the team" — a person.

Method

Two failures are being prevented, and they are not the same.

Leakage is what goes in. Treat every prompt as though it may be read by someone outside the company, because it may be.

Fabrication is what comes out, and it is the one most policies leave out. AI models generate plausible citations, not retrieved ones. Asked for a statistic, a model produces something with the right magnitude, attributed to a firm that genuinely publishes research in that area, with a sample size that sounds like a real study. It reads as evidence because it was built from the shape of evidence:

  • "In CB Insights' 2021 analysis of 110+ startup post-mortems, 35% of failed startups cited no market need."
  • "CB Insights found Series A companies with strong positioning raise their next round 30% faster."

The first is real, and even it is easy to get wrong: an older CB Insights edition put the figure at 42%, and the page that used to host it now serves a newer edition with different numbers. The edition and the year travel with the figure, or the figure is wrong. The second does not exist. To a reader — and to the model that wrote them — they are indistinguishable. That is not carelessness; it is what generation does when no document is in the loop.

The working rule: ask AI for the argument, not the statistics. Add figures afterwards, one at a time, each from a document the user has opened themselves.

Workflow

  1. Score adoption readiness. Run the engine. Report the verdict and every failed check verbatim. Lead with the blockers.

  2. Fill the approved-tools table — task, tool, who may use it, notes. Anything not on the list needs the owner's approval before use on company work. Review it quarterly; tools change faster than policies do.

  3. Verify the training setting rather than assuming it, and write the answer down with the date and who checked: Our plan trains on inputs: Yes / No · Verified on [date] by [name].

  4. Write the never-in-a-prompt list and keep it concrete: customer names and lists; unannounced pricing, roadmap or financials; anything under NDA; employee records and compensation; credentials, API keys and tokens; and anything the user would not be comfortable seeing in a screenshot on social media.

  5. Name the reviewer and the gate. Nothing AI-drafted publishes without a named human reviewer who answers four questions and is accountable for the answers:

    • Is every factual claim in this true, and can I show where it came from?
    • Does it sound like us, or does it sound like everyone?
    • Does it promise anything we cannot deliver?
    • Would I be comfortable if a customer knew AI drafted it?

    If any answer is no, it does not ship. The reviewer's name goes in the doc, the ticket or the CMS field — somewhere it survives the week.

  6. Check every citation with checkCitation. A published figure carries the organisation that ran the study (not the one that repeated it), the document's title and date — and edition, if it is an annual — the sample (how many, of what, measured when), and a link on that organisation's own domain.

  7. Set the disclosure line. Disclose where the reader's judgement depends on who wrote it: a founder's personal note, a customer story, a case study, anything under a named byline that the named person did not write. Routine drafting help on marketing copy needs no more disclosure than a spellchecker.

  8. Assign ownership and a review date. Who owns the policy, who approves a new tool, how a new tool is requested, and when it is next reviewed. Quarterly is the default.

  9. Hand over the five rules as a card to pin up, not as a document to file.

Run the tool

node resources/ai-governance.js --demo

scoreReadiness(state) returns a score, a verdict, every check with its reason, and what is missing before the team should be publishing AI-drafted work at all. checkCitation(citation) applies the section-5 rules to one source, and checkDraft(draft) sweeps a draft for unsourced figures, never-cite patterns and missing disclosure.

Use the engine's output rather than your own read of a source — the same rules every time is the point.

Present the result

  1. The principle, stated once: AI drafts, people decide and sign.
  2. The readiness verdict and score, blockers first, each failed check with its reason.
  3. The approved-tools table, with owners filled in and any blank cell named as a blank.
  4. The training-on-inputs answer, with its verification date, or flagged as unverified.
  5. The reviewer's name and where it will be recorded.
  6. Every citation checked, with the failures quoted.
  7. The five rules card.

Show where it came from. Open your answer with "AAJ ai-marketing-governance engine result:" and print the engine's output block exactly as it returned it, then add the line Method: https://skills.aajconsult.com/skills/ai-marketing-governance. Say the numbers come from the AAJ engine, not from the model. Put your interpretation under that block. Do not retype the figures from memory. If you could not run the engine, say so and label any numbers as your own estimate, not an AAJ result.

The five rules

  1. AI drafts. People decide and sign. No exceptions, no "it was only a social post".
  2. Use the tools on the list. Anything else needs approval first.
  3. Nothing confidential goes into a prompt. Customers, pricing, NDAs, credentials — none of it.
  4. Ask for the argument, not the statistics. Add every figure yourself, from a document you opened.
  5. A named person reviews before publish. Their name goes somewhere that survives the week.

Guardrails & common mistakes

  • Never invent a quote, a review or a testimonial. There is no version of that which is a shortcut rather than a fabrication.
  • Never publish AI-generated words under a named person's byline without that person reading and approving them.
  • If a claim needs a number that cannot be found, the claim is wrong — not under-researched. This is the line that saves the most trouble.
  • Never cite an AI-generated aggregator or "research" page that republishes other people's work; a publisher's index, tag or category page (a citation resolves to one document); a preprint described as a conference or journal paper — label it a preprint with its identifier; anything reached "via" a third party, because via in a source list is a confession; or a firm that no longer exists, for a figure that cannot be opened today.
  • Do not accept the plan's privacy default. Check whether the tier trains on inputs, write the answer down, and re-check it when the plan changes.
  • Do not let "the team" be the reviewer. Accountability that is not a name is not accountability.
  • Do not over-disclose. Disclosing routine drafting help trains readers to ignore disclosure where it matters.
  • A policy with no owner and no review date is a document. Refuse to hand one over in that state.
  • brand-voice-governance — the "does it sound like us" half of the review gate, at scale
  • seo-content-brief — where citation targets get chosen before drafting starts
  • aaj-copywriting — the drafting this policy governs

// faq

// install

$npx skills add sarojkjha/aaj-marketing-skills --skill ai-marketing-governance

// worked example

Get the worked example for AI Marketing Governance

One email. The filled-in config, the output, and how to read it.

No spam. Unsubscribe anytime.

// human in the loop

Need a human in the loop?

AAJ builds the strategies, tools, and playbooks these skills are made of — with engagements for growth-stage and enterprise teams.