mcpField
G
governance

governance

github.com/gtmagentsMarketing & growth43068 installsUpdated 30w ago
Repository

About governance

A governance skill for teams managing personalization rules, models, and content variants across deployments, compliance reviews, and audits. It organizes policy alignment, approvals, change records, risk monitoring, and audit trails, with templates for common processes.

Key features

  1. 01Policy and channel constraint records
  2. 02Change approvals and evidence requirements
  3. 03Version history and rollback details
  4. 04Fairness and compliance risk monitoring
  5. 05Decision and incident audit trails
  6. 06Change, checklist, and incident templates

Use cases

  1. 01Deploying personalization rule or model updates
  2. 02Running quarterly consent and fairness audits
  3. 03Investigating personalization errors or policy breaches

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill governance

After installing, type/governancein Claude Code to confirm it loaded.

Details

From the project README

Personalization Governance Skill

When to Use

  • Deploying or updating personalization rules, models, or high-impact content variants.
  • Running quarterly audits on consent, data usage, or fairness metrics.
  • Investigating incidents related to personalization errors or policy breaches.

Framework

  1. Policy Alignment – document legal, privacy, accessibility, and ethical constraints per channel.
  2. Approval Workflow – define RACI (architect, legal, security, marketing) and required evidence per change.
  3. Change Logging – capture version metadata (who, what, when, why), including rollback steps.
  4. Risk Monitoring – set KPIs + alerts for fairness, bias, consent violations, or performance regressions.
  5. Audit Trail – maintain dashboards + storage for decision logs, approvals, and incident reports.

Templates

  • Change request form (summary, impact, risk score, approvers, attachments).
  • Governance checklist (consent, accessibility, localization, security, QA evidence).
  • Incident review template (root cause, remediation, follow-up actions, owner).

Tips

  • Pair governance checkpoints with CI/CD or deployment scripts to prevent bypass.
  • Use unique change IDs to connect decision tree updates with content variants and experiments.
  • Schedule quarterly tabletop exercises to keep stakeholders fluent in escalation paths.

Comments

Markdown supported