Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/useai-pro/openclaw-skills-security --skill permission-auditor- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads permission-auditor automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
network
What it allows: Making HTTP requests to external servers. Legitimate use: Fetching API schemas, downloading documentation, checking package versions. Risk: This is the primary exfiltration vector. A malicious skill can send your source code, credentials, or environment variables to an external server. Mitigation: Network access should be rare. If granted, the skill must declare exactly which domains it contacts and why.
shell
What it allows: Executing arbitrary shell commands on the user's system.
Legitimate use: Running git log, npm test, build commands.
Risk: Full system compromise. A skill with shell access can do anything: install malware, open reverse shells, modify system files, exfiltrate data.
Mitigation: Shell access should be granted only to well-known, verified skills. Always review which commands the skill executes.
Audit Protocol
When the user provides a skill's permissions, follow this process:
1. List Requested Permissions
PERMISSION AUDIT
================
Skill: <name>
fileRead: [YES/NO]
fileWrite: [YES/NO]
network: [YES/NO]
shell: [YES/NO]
2. Evaluate Necessity
For each granted permission, answer:
- Why does this skill need it? (based on its description)
- Is this the minimum required? (could it work with fewer permissions?)
- What is the worst case? (if the skill is malicious, what could it do?)
3. Identify Dangerous Combinations
| Combination | Risk | Reason |
|---|---|---|
| network + fileRead | CRITICAL | Can read and exfiltrate any file |
| network + shell | CRITICAL | Can execute commands and send output externally |
| shell + fileWrite | HIGH | Can modify system files and persist |
| fileRead + fileWrite | MEDIUM | Can read secrets and write backdoors |
| fileRead only | LOW | Read-only, minimal risk |
4. Suggest Minimum Permissions
Based on the skill's description, recommend the minimal permission set:
RECOMMENDATION
==============
Current: fileRead + fileWrite + network + shell
Minimal: fileRead + fileWrite
Reason: This skill generates tests from source code.
It needs to read source and write test files.
Network and shell access are not justified.
Rules
- Always explain permissions in plain language — assume the user is not a security expert
- Use concrete examples of what could go wrong, not abstract warnings
- If a skill requests
networkorshell, always recommend extra scrutiny - Never approve a skill with all four permissions unless it has a strong justification
- Suggest alternatives if a skill seems over-privileged
FAQ
What does the permission-auditor skill do?
Analyze OpenClaw skill permissions and explain exactly what each permission allows. Identifies over-privileged skills and suggests minimal permission sets.
How do I install permission-auditor?
Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill permission-auditor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/permission-auditor/ (personal) or .claude/skills/permission-auditor/ (project).
Which AI agents can use permission-auditor?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is permission-auditor safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains permission-auditor?
It is published by useai-pro in useai-pro/openclaw-skills-security. It has 477 recorded installs.
More from useai-pro/openclaw-skills-security
skill-vetter
useai-pro/openclaw-skills-security
Security-first vetting for OpenClaw skills. Use before installing any skill from ClawHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
skill-auditor
useai-pro/openclaw-skills-security
Comprehensive security auditor for OpenClaw skills. Checks for typosquatting, dangerous permissions, prompt injection, supply chain risks, and data exfiltration patterns — before you install anything.
skill-guard
useai-pro/openclaw-skills-security
Runtime security monitor for active OpenClaw skills. Watches file access, network calls, and shell commands. Flags anomalous behavior and enforces permission boundaries.
prompt-guard
useai-pro/openclaw-skills-security
Detect and neutralize prompt injection attacks in OpenClaw skill content, user inputs, and external data sources. Prevents instruction hijacking and context manipulation.
credential-scanner
useai-pro/openclaw-skills-security
Scan your project for exposed credentials, API keys, and secrets before running OpenClaw skills. Prevents accidental exfiltration.
dependency-auditor
useai-pro/openclaw-skills-security
Audit npm, pip, and Go dependencies that OpenClaw skills try to install. Checks for known vulnerabilities, typosquatting, and malicious packages.
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.