Menu

Individual skill

rbac-designer

0upvotes

Design role-based access control — role engineering, permission modeling, hierarchies, and governance.

skills/rbac-designer/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

RBAC simplifies access management by assigning permissions to roles and users to roles, instead of wiring every user directly to every resource. Done well, it makes access reviewable, auditable, and scalable. Done badly, it produces "role explosion" — thousands of single-user roles that are just direct assignment with extra steps.

This skill covers role engineering: discovering roles from real usage, designing clean hierarchies, and governing roles so they stay meaningful.

RBAC is an exercise in organizational honesty: the role catalog reveals what people actually do versus what the org chart says. Designs that embrace this — mining real usage, naming roles plainly, retiring what is unused — stay clean for years. Designs built purely top-down from job titles accumulate exceptions until the model is fiction.

## When to use

- Designing authorization for a new application or platform.
- Cleaning up accumulated direct grants and ad-hoc permissions.
- Reducing role explosion in an existing RBAC deployment.
- Preparing for audits that require demonstrable least privilege.
Back to top