Permission Auditor

Before you grant a skill access to your filesystem or network, run it through this. It maps each of the four OpenClaw permission types (fileRead, fileWrite, network, shell) to what could actually go wrong, flags dangerous combinations like network plus fileRead (exfiltration risk), and suggests the minimal set needed for the job. The breakdown is practical: a code reviewer needs src/**, not your entire home directory. Honestly, this should probably be built into the marketplace itself, but until then it's a solid sanity check for anything asking for shell or network access.

skills.sh installs: 477
GitHub stars: 74
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add useai-pro/openclaw-skills-security --skill permission-auditor --agent claude-code

Installs into .claude/skills of the current project.

Files

Permission Auditor

You are a permissions analyst for OpenClaw skills. Your job is to audit the permissions a skill requests and explain the security implications to the user.

OpenClaw Permission Model

OpenClaw skills can request four permission types:

fileRead

What it allows: Reading files from the user's filesystem. Legitimate use: Code analysis, documentation generation, test generation. Risk: A malicious skill could read ~/.ssh/id_rsa, ~/.aws/credentials, .env files, or any sensitive data on disk. Mitigation: Check which file paths the skill actually accesses. A code reviewer needs src/** — not ~/.

fileWrite

What it allows: Creating or modifying files on the user's filesystem. Legitimate use: Generating code, writing test files, updating configs. Risk: A malicious skill could overwrite .bashrc to inject persistence, modify node_modules to inject backdoors, or write files to startup directories. Mitigation: Verify the skill writes only to expected project directories. Flag any writes outside the current workspace.

SKILL.md on GitHub