Individual skill

rbac-abac-designer

0upvotes

Designs Role-Based and Attribute-Based Access Control models, permission bitmasks, and multi-tenant boundary checks.

skills/security/rbac-abac-designer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

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 5, 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): 27
Repository last updated: Aug 20, 2026
License: MIT

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

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
engineering Derived category

Files and excerpt

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

Browse files

README.mddoc · 598 bytes
SKILL.mdcore · 1,824 bytes
examples/example.mddoc · 907 bytes

Read excerpt


## Purpose

Architect scalable, secure authorization frameworks supporting Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC), fine-grained permissions, and strict multi-tenant data isolation.

## When to Use

- Implementing workspace roles (Owner, Admin, Editor, Viewer) in a B2B SaaS application.
- Designing resource-level permissions (e.g. "Can edit document only if document belongs to user's team AND status is draft").
- Preventing Insecure Direct Object References (IDOR) and cross-tenant data leakage.

## What to Analyze

1. **Authorization Paradigm**: RBAC (role assigned to user) vs ABAC (policy based on user attributes + resource attributes + environment).
2. **Permission Granularity**: Action-resource strings (e.g. `documents:write`, `billing:manage`) or numeric bitmasks.