Design and apply a usable data classification scheme: a small set of levels (public/internal/confidential/restricted) plus a PII/sensitive flag, handling rules per level, and a mapping to enforceable controls — governing the highest-risk data first.
How this skill is triggered — by the user, by Claude, or both
Slash command
/data-governance-privacy:data-classificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Few levels: **public / internal / confidential / restricted** + a **PII/sensitive** flag. A 12-tier scheme nobody applies governs nothing.
Few levels: public / internal / confidential / restricted + a PII/sensitive flag. A 12-tier scheme nobody applies governs nothing.
Access, encryption, retention, sharing — defined per level so classification means something.
Each rule -> an enforceable control (masking, access rule, retention job) in the system that owns it. A policy with no control is aspiration.
Classify restricted/PII first; expand. Don't boil the ocean.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub mcorbett51090/ravenclaude --plugin data-governance-privacy