Authorization
Skill kimtth/agent-skill-100-lines-or-less/skills/authorization
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill authorizationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: design or review access control so users can only do what they are permitted to do.
SKILL.md
1.1 KB, as published. Nobody here has run it
Goal: enforce permissions consistently at every trust boundary.
Use for:
- deciding who can read or change what
- choosing a model: roles, attributes, or relationships
- fixing missing or inconsistent permission checks
Workflow:
- Define the resources, actions, and who may perform them.
- Choose a model: RBAC, ABAC, or relationship-based (ReBAC).
- Enforce checks server-side at every entry point.
- Default to deny; grant explicitly.
- Scope data queries to the caller's permissions.
- Test allowed and forbidden paths, including escalation attempts.
Patterns:
- centralized policy checks, not scattered ad hoc ifs
- ownership and tenant scoping on every query
- least privilege for roles and service accounts
- deny-by-default with explicit allow rules
Rules:
- never trust client-side authorization
- check on the server at the data boundary, every time
- default deny; make grants explicit and auditable
- prevent IDOR by scoping queries to the authorized subject