Personalization orchestration covering profiles, decision rules, and governance
Installation
npx claude-plugins install @gtmagents/gtm-agents/personalization-engine
Contents
Folders: agents, commands, skills
Included Skills
This plugin includes 3 skill definitions:
content-variants
Use when planning, approving, and versioning personalized creative assets.
View skill definition
Content Variant System Skill
When to Use
- Mapping creative requirements for each decision tree branch.
- Coordinating design, copy, and legal reviews across multiple channels.
- Auditing variant performance or sunsetting outdated experiences.
Framework
- Variant Inventory – catalog base asset, variant name, audience, channel, owner, expiration.
- Approval Flow – document reviewers, compliance steps, localization, accessibility requirements.
- Asset Delivery – link storage locations (DAM, CMS, MAP) plus version IDs and CDN paths.
- Testing Hooks – note experiment IDs, KPIs, guardrails for each variant.
- Lifecycle Management – set refresh cadences, archival rules, and dependency tracking.
Templates
- Variant matrix (channel × persona × lifecycle stage).
- Approval checklist (copy, design, legal, localization, accessibility).
- Performance tracker (variant → impressions → engagement → conversion → decision).
Tips
- Assign unique IDs to every variant for analytics + rollback references.
- Bundle variants into kits aligned with key journeys for easier governance.
- Pair with
decision-treesoutputs to ensure every branch has an approved asset.
decision-trees
Use when designing branching logic, eligibility rules, and fallback paths.
View skill definition
Personalization Decision Trees Skill
When to Use
- Planning logic for dynamic experiences across web, in-app, email, or sales plays.
- Auditing existing decision flows for complexity, coverage, or compliance gaps.
- Simulating new branches before deploying rule or model updates.
Framework
- Objective Mapping – tie each node to business KPIs and user intents.
- Signal Hierarchy – prioritize deterministic signals (consent, account tier, lifecycle) before behavioral or predictive ones.
- Fallback Design – ensure every branch has a safe default when data is missing or risk flags appear.
- Experiment Hooks – embed test slots at key decision points with guardrail metrics.
- Monitoring – log path selections, success rates, and anomaly alerts for continuous tuning.
Templates
- Decision tree canvas (node, condition, action, fallback, owner).
- Signal priority matrix (signal → freshness → reliability → privacy risk).
- Simulation checklist (scenarios, expected path, validation steps).
Tips
- Keep trees shallow where possible; offload complexity to scoring models or external services.
- Version control decision logic alongside content assets for traceability.
- Pair with
governanceskill to log approvals for high-impact branches.
governance
Use to enforce approvals, compliance, and auditability for personalization
View skill definition
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
- Policy Alignment – document legal, privacy, accessibility, and ethical constraints per channel.
- Approval Workflow – define RACI (architect, legal, security, marketing) and required evidence per change.
- Change Logging – capture version metadata (who, what, when, why), including rollback steps.
- Risk Monitoring – set KPIs + alerts for fairness, bias, consent violations, or performance regressions.
- 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.