Security / Runtime Hardening

Marketing Agent Risk Review

Assess marketing and adtech agents for risky actions, sensitive data exposure, unsafe tool access, and missing human approval boundaries.

DocumentationAgent instructionsRequirements & limits

Use when reviewing marketing or adtech agents that touch spend, audiences, product data, analytics, customer data, or publishing workflows.

Inputs

Collect:

  • Agent role and business objective.
  • Channels involved: search, social, programmatic, CRM, commerce, SEO, analytics, CMS.
  • Tool list and permissions.
  • Data categories: aggregate metrics, audience lists, customer records, creative assets, product catalog, commercial terms.
  • Actions the agent may perform.
  • Human review points and approval owners.
  • Logging and retention requirements.

Outputs

  • Marketing-agent risk matrix
  • Required approval gates
  • Data-governance recommendations

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Analysis-only; must not approve campaigns, change spend, publish content, export data, or modify permissions.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Marketing Agent Risk Review

When to use

Use this skill when a proposed agent touches marketing operations, commerce, analytics, paid media, lifecycle CRM, SEO, product feeds, or content publishing.

Typical triggers:

  • "Can this paid media agent safely change budgets?"
  • "What should be approval-gated in this marketing workflow?"
  • "Is this analytics agent allowed to export customer data?"
  • "What security risks exist in this campaign copilot?"
  • "How should we separate suggestion, approval, and execution?"

Inputs required

Collect:

  • Agent role and business objective.
  • Channels involved: search, social, programmatic, CRM, commerce, SEO, analytics, CMS.
  • Tool list and permissions.
  • Data categories: aggregate metrics, audience lists, customer records, creative assets, product catalog, commercial terms.
  • Actions the agent may perform.
  • Human review points and approval owners.
  • Logging and retention requirements.

Workflow

  1. Classify the action surface.

    • Low risk: read aggregate metrics, summarize reports, draft recommendations.
    • Medium risk: generate campaign drafts, create audience suggestions, prepare product-feed changes.
    • High risk: change budgets, publish content, modify bidding, export user-level data, update customer journeys, alter tracking, or change permissions.
  2. Classify the data surface.

    • Aggregate campaign metrics are lower risk.
    • Customer-level data, audience membership, CRM events, cookies, identifiers, conversion values, and commercial terms require stricter controls.
  3. Check tool permissions.

    • Identify whether each tool is read-only, governed write, or unrestricted write.
    • Flag broad API scopes and human-token inheritance.
  4. Check approval boundaries.

    • Require human approval for all high-risk actions.
    • Require a second reviewer for data export, production publishing, bidding changes, or policy overrides.
  5. Check compliance and brand risk.

    • Identify claims, regulated categories, targeting constraints, attribution claims, and platform policy exposure.
    • Recommend deterministic checks where rules are clear.
  6. Check audit and rollback.

    • Confirm every decision can be traced to prompt, model, tool call, policy result, approver, and artifact version.
    • Recommend rollback plans for published or budget-impacting actions.

Output format

# Marketing Agent Risk Review

## Overall risk
Low / Medium / High / Blocked

## Risk matrix
| Area | Risk | Evidence | Required control |
| --- | --- | --- | --- |
| Spend | ... | ... | ... |
| Publishing | ... | ... | ... |
| Customer data | ... | ... | ... |
| Tool permissions | ... | ... | ... |
| Compliance | ... | ... | ... |
| Audit and rollback | ... | ... | ... |

## Approval gates
1. ...

## Required changes
1. ...

## Safe starting mode
Advisory / Plan-only / Approval-gated execution / Not recommended

Guardrails

  • Do not approve or execute campaign, bidding, publishing, audience, or data-export actions.
  • Treat spend changes, customer-level data, and production publishing as high risk by default.
  • Do not rely on the same model instance to both generate and approve regulated or brand-sensitive content.
  • If tool permissions are unclear, classify the tool as unrestricted until proven otherwise.
  • Recommend plan-only mode when identity, policy, logging, or approval boundaries are missing.

Failure modes

  • If platform policies are unknown, require policy review before launch.
  • If data classification is missing, block customer-level export and recommend aggregate-only operation.
  • If rollback is impossible, require stricter approval and staging before execution.
View file metadata
---
name: marketing-agent-risk-review
description: Review marketing and adtech agents for spend, publishing, customer-data, audience, attribution, and compliance risks before deployment.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/input.json, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install security/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install security/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install security/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: analysis-only

Approval boundary: Analysis-only; must not approve campaigns, change spend, publish content, export data, or modify permissions.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: security/marketing-agent-risk-review

Tags: marketing, adtech, security, approvals, data-governance

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Marketing-agent risk matrix
  • Required approval gates
  • Data-governance recommendations