Access Control Rbac
CheckedThis RBAC skill manages user access permissions to resources, ensuring secure and granular control for enhanced system protection.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add aj-geddes/useful-ai-prompts --skill access-control-rbac -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
aj-geddes
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned aj-geddes/useful-ai-prompts at 3f5182cfd7.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3f5182cfd7
- Scanned
- 5 files, 624 lines
About this skill
access-control-rbac
What it does
This skill enables AI agents to manage Role-Based Access Control (RBAC) policies within cloud environments. It allows for the dynamic assignment of roles and permissions to users or service identities based on specific organizational requirements.
When to use it
- Enforce least-privilege principles by granting minimal necessary permissions to new team members.
- Rotate access credentials automatically when an employee leaves the organization.
- Audit current permission sets to identify overly broad or unused roles.
- Implement temporary elevated access for contractors with auto-expiry settings.
Key capabilities
- Define custom roles with granular permission scopes.
- Assign roles to individual users, groups, or service accounts.
- Enforce policy constraints across cloud infrastructure resources.
- Generate compliance reports on active permissions and role usage.
Example prompts
- "Create a 'Data Analyst' role that can read all datasets in the finance bucket but cannot delete any files."
- "Remove write access from the 'Interns' group for the production database cluster immediately."
- "Audit the current RBAC configuration and list all users with admin-level permissions."
Tips & gotchas
Ensure you have root or owner-level access to the cloud provider console before attempting to modify role definitions. Always test permission changes in a non-production environment first to prevent accidental lockouts of critical services.