Skip to content
TrustedSkillsbeta
Back to all skills

Permission System

Checked
m19803261706·vlatest·security

This skill establishes granular user permissions, ensuring secure access and controlled resource utilization within your application.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add m19803261706/springboot-vben-admin --skill permission-system -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

m19803261706

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 m19803261706/springboot-vben-admin at 06cecca9b4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
06cecca9b4
Manifest
.claude/skills/permission-system/SKILL.md
Scanned
1 file, 333 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides a permission system for managing access control within applications. It allows defining roles and associating permissions with those roles, then assigning users to specific roles. This enables granular control over what actions different users can perform within the application environment.

When to use it

  • Controlling User Access: Restrict access to sensitive data or functionalities based on user roles (e.g., only administrators can delete records).
  • Implementing Role-Based Security: Define distinct roles like "editor," "reviewer," and "publisher" with varying permissions for content management workflows.
  • Managing API Access: Control which users or applications have access to specific APIs based on assigned permissions.
  • Enforcing Data Governance Policies: Ensure compliance by limiting user actions according to predefined data governance rules.

Key capabilities

  • Role Definition: Create and manage roles within the system.
  • Permission Assignment: Assign specific permissions to each role.
  • User Role Association: Assign users to one or more roles.
  • Access Control Enforcement: Automatically enforce permission restrictions based on user roles.

Example prompts

  • "Create a new role called 'Moderator' with permissions for 'edit_posts' and 'delete_comments'."
  • "Assign the user 'john.doe' to the 'Editor' role."
  • "List all users who have the 'Admin' role."

Tips & gotchas

This skill likely requires a pre-existing application framework that supports roles and permissions. Ensure your AI agent has access to the underlying data structures for managing users, roles, and permissions within that framework.