About data-governance-access-review
A skill for converting data-governance questions into access-control plans covering classification, approvals, retention, auditing, and emergency access. It produces concrete governance artifacts and policies for exceptions and offboarding.
Key features
- 01Classifies data and access roles
- 02Defines approval and least-privilege rules
- 03Sets retention and review cadence
- 04Plans auditing and break-glass access
- 05Creates exception and offboarding policies
Use cases
- 01Reviewing access to sensitive data
- 02Designing data access approvals
- 03Setting break-glass procedures
- 04Auditing stale access and offboarding
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill data-governance-access-reviewAfter installing, type/data-governance-access-reviewin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/data-governance-access-patterns.md
Details
From the project READMEData Governance Access Review
Use this skill to convert a data governance, classification, access controls, least privilege, approvals, retention, audit logs, and break-glass policy question into a concrete artifact with owners, gates, metrics, and recovery paths.
Workflow
- Identify data domains, sensitive fields, actors, access purpose, retention requirements, owner teams, tooling, and audit expectations.
- Read
references/data-governance-access-patterns.md. - Classify data by sensitivity, residency, source, purpose, retention, customer visibility, and allowed access roles.
- Define access request workflow, approval policy, least privilege, expiration, review cadence, audit log, break-glass, and offboarding.
- Produce governance plan, state machine, decision table, event schema, access checklist, and exception review policy.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not grant permanent broad production data access for convenience.
- Do not let analytics, support, AI, or sales tooling copy sensitive data without purpose, minimization, retention, and owner approval.
- Do not run break-glass without incident/ticket reason, expiry, audit, and post-review.
- Do not treat data governance as complete if offboarding and stale access reviews are missing.
Output format
Data governance context:
Data class / actor / purpose / retention:
Data access governance plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |
Roles, approvals, and audits:
- <item> -> <policy, metric, edge case, support note>
Exception and break-glass policy:
- <trigger> -> <action, communication, owner>
Comments
Markdown supported