Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build secure access control with RBAC, ABAC, permissions, policies, and scope-based authorization.
Build secure access control with RBAC, ABAC, permissions, policies, and scope-based authorization.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User needs to control what actions users can perform. Agent handles permission design, role hierarchies, policy evaluation, and access control middleware.
TopicFileRBAC vs ABAC comparisonmodels.mdImplementation patternspatterns.mdFramework middlewaremiddleware.md
Authentication: Who you are (login, OAuth, tokens) Authorization: What you can do (permissions, roles, policies) Never mix concerns โ auth happens BEFORE authorization
Default deny โ explicit grants only Users get minimum permissions for their job Audit permissions periodically (revoke unused) Temporary elevation over permanent grants
ModelBest ForComplexityACLSimple resource ownershipLowRBACOrganizational hierarchiesMediumABACDynamic context-based rulesHighReBACSocial graphs, sharingHigh Start simple โ evolve when needed.
Roles represent jobs, not permissions Max 3 inheritance levels (admin โ manager โ user) Avoid role explosion โ combine with ABAC for edge cases Document role definitions (what can this role DO?)
resource:action:scope documents:write:own โ Can edit own documents documents:write:team โ Can edit team documents documents:delete:all โ Can delete any document Consistent naming prevents ambiguity.
Explicit deny โ always wins Explicit allow โ checked second No match โ default deny Log all denials for debugging
// โ Bad โ hardcoded role check if (user.role === 'admin') { ... } // โ Good โ permission check if (can(user, 'settings:update')) { ... } Roles change. Permissions are stable.
Checking roles instead of permissions โ brittle when roles change OR logic in permissions โ "can edit OR is admin" creates backdoors Caching permissions too long โ stale grants after role changes Frontend-only checks โ always verify server-side God roles โ split "admin" into specific permission sets Circular inheritance โ A inherits B inherits A crashes system
Data that stays local: All documentation and patterns are reference material No data collection or external requests This skill does NOT: Access your codebase automatically Make network requests Store any user data
If useful: clawhub star authorization Stay updated: clawhub sync
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.