Claude-skill-registry governance
Use to enforce approvals, compliance, and auditability for personalization
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/governance" ~/.claude/skills/majiayu000-claude-skill-registry-governance-d854a9 && rm -rf "$T"
manifest:
skills/data/governance/SKILL.mdsource content
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.