Skip to content
TrustedSkillsbeta
Back to all skills

Permission Auditor

Listed
useai-pro·vlatest·security·MIT

The Permission Auditor analyzes user permissions to identify potential over-access and security risks, ensuring data protection & compliance.

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 useai-pro/openclaw-skills-security --skill permission-auditor -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

useai-pro

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No credential access: failed

    Touches credential material in 2 places.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

    What it found

    • skills/permission-auditor/SKILL.md:38instructs the agent to access ssh private keys or config(in the instructions, not code)
      **Risk:** A malicious skill could read `~/.ssh/id_rsa`, `~/.aws/credentials`, `.env` files, or any sensitive data on disk.
    • skills/permission-auditor/SKILL.md:38instructs the agent to access aws credentials file(in the instructions, not code)
      **Risk:** A malicious skill could read `~/.ssh/id_rsa`, `~/.aws/credentials`, `.env` files, or any sensitive data on disk.

  • 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 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 useai-pro/openclaw-skills-security at 4645f2d047.

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

Commit
4645f2d047
Manifest
skills/permission-auditor/SKILL.md
Scanned
1 file, 110 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

The permission-auditor skill analyzes a given set of permissions and determines if they are overly broad or potentially risky. It identifies specific resources that the agent can access, flags any wildcard usage (like *), and suggests more restrictive alternatives where possible. This helps ensure AI agents operate with appropriate levels of access and reduces potential security vulnerabilities.

When to use it

  • Reviewing new agent configurations: Before deploying an agent, audit its permissions to proactively identify and mitigate risks.
  • Responding to security alerts: If a security incident occurs, quickly assess the permissions granted to affected agents.
  • Periodic access reviews: Regularly review agent permissions as part of your overall security posture.
  • Troubleshooting unexpected behavior: When an AI agent exhibits unusual or unintended actions, examine its permissions for potential misconfigurations.

Key capabilities

  • Identifies accessible resources.
  • Flags wildcard permission usage.
  • Suggests more restrictive permission alternatives.

Example prompts

  • "Analyze these permissions: read:*/data, write:s3://my-bucket/* and tell me if they are overly broad."
  • "Can you review the following agent permissions and suggest improvements? `execute:lambda:*"
  • "What's risky about granting an AI agent admin access?"

Tips & gotchas

The effectiveness of this skill depends on providing accurate and complete permission lists. Wildcard usage can be difficult to fully assess without context, so always review the suggested alternatives carefully.