Skip to content
TrustedSkillsbeta
Back to all skills

Permission Test Skill

Checked
matteocervelli·vlatest·security·MIT

Checks if a user has sufficient permissions to perform a specified action within a system.

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 matteocervelli/llms --skill permission-test-skill --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/permission-test-skill/SKILL.md
Scanned
1 file, 55 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 allows an AI agent to test if a user has specific permissions. It determines whether a given user possesses a particular permission based on predefined rules or configurations. The skill can be used for access control and authorization within applications or systems.

When to use it

  • Access Control: Verify if a user is allowed to perform an action, like deleting a file or accessing sensitive data.
  • Feature Gating: Enable or disable features based on the user's permission level.
  • Authorization Checks: Confirm that a user has the necessary rights before proceeding with a request.
  • API Security: Ensure users have appropriate permissions to access specific API endpoints.

Key capabilities

  • Permission checking
  • User authorization
  • Access control verification

Example prompts

  • "Does user 'john.doe' have permission to 'delete_files'?"
  • "Check if the current user has the 'admin' role."
  • "Verify that user 'jane.smith' is authorized for 'data_export'."

Tips & gotchas

The skill relies on a pre-existing system or configuration defining user permissions; it doesn’t create those definitions itself. Ensure your permission rules are accurately defined and accessible to the agent for accurate results.