Authorization Design
Design authorization systems (access control, role-based permissions, principle of least privilege) to enforce fine-grained access policies.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill authorization-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/secure-development/skills/authorization-design ~/.claude/skills/authorization-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Authorization Design
Design fine-grained authorization systems using least privilege and role-based or capability-based access control.
## Context
You are a senior security architect designing authorization for $ARGUMENTS. Authorization enforces that authenticated users can only access resources they're entitled to.
## Domain Context
- **Principle of Least Privilege**: Grant minimum necessary permissions; default deny, explicit allow
- **Role-Based Access Control (RBAC)**: Users assigned roles (Admin, Editor, Viewer); roles have permissions
- **Attribute-Based Access Control (ABAC)**: Permissions based on attributes (user department, resource owner, time of day)
- **Capability-Based Access Control**: Users hold unforgeable tokens granting access; more fine-grained than RBAC
## Instructions
1. **Design Roles & Permissions**:
- Identify roles (Admin, Moderator, User, Guest)
- Define permissions for each resource/action (Read, Write, Delete, Admin)
- Assign roles to users; never grant permissions directly
- Example:
```
Admin: Read/Write/Delete all resources
Moderator: Read all; Write/Delete own posts and user-reported content
User: Read all; Write own content; Delete own content
Guest: Read public content only
```
2. **Implement Least Privilege**:
- Default deny; explicitly grant permissions
- Users get minimum necessary role; not Admin by defaultDetails
- Skill name
authorization-design- Repository
- sethdford/claude-skills
- Path
security/secure-development/skills/authorization-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Authorization Design skill do?
Design authorization systems (access control, role-based permissions, principle of least privilege) to enforce fine-grained access policies.
How do I install the Authorization Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Authorization Design popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Change Impact Analysis
48sethdford/claude-skills
Predict impacts of architectural changes on dependent systems. Trace dependencies, assess risk, plan rollout. Use when making major changes or analyzing blast radius.
Authentication Design
48sethdford/claude-skills
Design secure authentication systems with strong password policies, MFA, secure password reset, and session management.
Competitive Landscape
48sethdford/claude-skills
Map existing solutions, alternatives, and competitive positioning to understand the problem space.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.