access-control-planner

Define actors, resources, and protected actions for access-control models.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill access-control-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: access-control-planner
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/access-control-planner
Command: npx skills add https://github.com/saranskumar/anti-slop --skill access-control-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define and model who can access which resources and actions within a system.

Core Features & Use Cases

  • Identify actors, resources, and protected actions to model access.
  • Map permissions with ownership, roles, memberships, and policies across systems.
  • Use in multi-tenant or domain-specific environments to prevent over- or under-privilege.

Quick Start

Identify actors, resources, and actions for your system and draft an initial access-control model.

Frequently Asked Questions about access-control-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I model access control policies for a multi-tenant system?

To model access control for multi-tenant systems, identify your required actors, resources, and protected actions, then map permissions across ownership, roles, memberships, and policies to prevent over-privilege.

What is the difference between RBAC and ABAC for policy design?

RBAC and ABAC are access control models scoped within this planner to define permissions. RBAC maps permissions via roles and memberships, while ABAC evaluates attributes and policies to determine resource access.

How do I define protected operations and policy enforcement layers?

You define protected operations and policy enforcement layers by specifying the required actors, targeted resources, and protected actions, establishing the boundaries for secure access control within your system.

When should I use a dedicated access control model instead of ad-hoc permissions?

Use a dedicated access control model when you need to prevent over-privilege in domain-specific or multi-tenant environments, requiring precise mapping of ownership, roles, memberships, and policies.

Does this approach support mapping ownership and memberships across systems?

Yes, the access control planning process supports mapping permissions with ownership, roles, memberships, and policies across various systems to ensure precise and secure resource access.