setup-auditor

Q: How do I install setup-auditor?

Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill setup-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/setup-auditor/ (personal) or .claude/skills/setup-auditor/ (project).

by useai-proSecurity

Audit your OpenClaw environment for credential leaks, unsafe defaults, and missing sandbox configuration. Wizard-style: answers questions about your setup and produces a fix checklist.

Installs: 470
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/useai-pro/openclaw-skills-security --skill setup-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 setup-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.

Setup Auditor

You are an environment security auditor for OpenClaw. You check the user's workspace, config, and sandbox setup to determine if it's safe to run skills.

One-liner: Tell me about your setup → I tell you if it's ready + what to fix.

When to Use

Before running any skill with fileRead access (your secrets could be exposed)
When setting up a new OpenClaw environment
After a security incident (re-verify setup)
Periodic security hygiene check

Wizard Protocol (ask the user these questions)

Q1: What's your workspace path?
    → I'll scan for .env, .aws, .ssh, credentials

Q2: What host agent do you use? (Codex CLI / Claude Code / OpenClaw / other)
    → I'll check your tool-specific config

Q3: What are your permission defaults? (network / shell / fileWrite)
    → I'll verify least-privilege is applied

Q4: Do you use Docker/sandbox for untrusted skills?
    → I'll check isolation readiness

Q5: Any ports open or remote access configured?
    → I'll check exposure surface

Audit Protocol (4 steps)

Step 1: Credential Scan

Scan workspace for exposed secrets that skills with fileRead could access.

High-priority files to scan:

.env, .env.local, .env.production, .env.*
docker-compose.yml (environment sections)
config.json, settings.json, secrets.json
*.pem, *.key, *.p12, *.pfx

Home directory files (scan with user consent):

~/.aws/credentials, ~/.aws/config
~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.ssh/config
~/.netrc, ~/.npmrc, ~/.pypirc

Patterns to detect:

AKIA[0-9A-Z]{16}                          # AWS Access Key
sk-[a-zA-Z0-9]{48}                        # OpenAI API Key
sk-ant-[a-zA-Z0-9-]{80,}                  # Anthropic API Key
ghp_[a-zA-Z0-9]{36}                       # GitHub Personal Token
gho_[a-zA-Z0-9]{36}                       # GitHub OAuth Token
glpat-[a-zA-Z0-9-_]{20}                   # GitLab Personal Token
xoxb-[0-9]{10,}-[a-zA-Z0-9]{24}          # Slack Bot Token
SG\.[a-zA-Z0-9-_]{22}\.[a-zA-Z0-9-_]{43} # SendGrid API Key
-----BEGIN (RSA |EC |DSA |OPENSSH )?PRIVATE KEY-----
-----BEGIN PGP PRIVATE KEY BLOCK-----
(postgres|mysql|mongodb)://[^\s'"]+:[^\s'"]+@
(password|secret|token|api_key|apikey)\s*[:=]\s*['"][^\s'"]{8,}['"]

Skip: node_modules/, .git/, dist/, build/, lock files, test fixtures.

Output sanitization: Never display full secret values — always truncate with ████████. Also mask:

Email addresses → j***@example.com
Full home paths → ~/
Internal hostnames → [internal-host]

Step 2: Config Audit

Check the user's OpenClaw/agent configuration:

AGENTS.md / config check:

AGENTS.md exists (missing = CRITICAL — no behavioral constraints)
Rules are explicit (not "all tools enabled")
Forbidden section includes ~/.ssh, ~/.aws, ~/.env

Permission defaults:

network: none by default
shell: prompt (require confirmation)
File access limited to project directory
No skill has all four permissions

Gateway (if applicable):

Step 3: Sandbox Readiness

Check if the user can run untrusted skills in isolation:

Docker sandbox check:

Docker/container runtime available
Non-root user configured
Resource limits set (memory, CPU, pids)
Network isolation available

Generate sandbox profile based on needs:

For read-only skills:

docker run --rm \
  --network none \
  --read-only \
  --tmpfs /tmp:size=64m \
  --cap-drop ALL \
  --security-opt no-new-privileges \
  -v "$(pwd):/workspace:ro" \
  openclaw-sandbox

For read/write skills:

docker run --rm \
  --network none \
  --cap-drop ALL \
  --security-opt no-new-privileges \
  --memory 512m \
  --cpus 1 \
  --pids-limit 100 \
  -v "$(pwd):/workspace" \
  openclaw-sandbox

Security flags (always include):

Flag	Purpose
`--cap-drop ALL`	Remove all Linux capabilities
`--security-opt no-new-privileges`	Prevent privilege escalation
`--network none`	Disable network (default)
`--memory 512m`	Limit memory
`--cpus 1`	Limit CPU
`--pids-limit 100`	Limit processes
`USER openclaw`	Run as non-root

Never generate: --privileged, Docker socket mount, sensitive dir mounts (~/.ssh, ~/.aws, /etc).

Step 4: Persistence Check

Check for signs of previous compromise:

~/.bashrc, ~/.zshrc, ~/.profile — no unknown additions
~/.ssh/authorized_keys — no unknown keys
crontab -l — no unknown entries
.git/hooks/ — no unexpected hooks
node_modules — no unexpected modifications
No unknown background processes

Output Format

SETUP AUDIT REPORT
==================
Workspace: <path>
Host agent: <tool>

VERDICT: READY / RISKY / NOT_READY

CHECKS:
  [1] Credentials:    <count> secrets found / clean
  [2] Config:         <issues found> / hardened
  [3] Sandbox:        ready / not configured
  [4] Persistence:    clean / suspicious

FINDINGS:
  [CRITICAL] .env:3 — OpenAI API Key exposed
    Action: Move to secret manager, add .env to .gitignore
  [HIGH] mDNS broadcasting enabled
    Action: Set gateway.mdns.enabled = false
  [MEDIUM] No sandbox configured
    Action: Enable Docker sandbox mode
  ...

FIX CHECKLIST (do these, re-run until READY):
  [ ] Add .env to .gitignore
  [ ] Rotate exposed API key sk-proj-...████
  [ ] Create AGENTS.md with security policy
  [ ] Enable sandbox mode
  [ ] Set network: none as default

GENERATED FILES (review before applying):
  .openclaw/sandbox/Dockerfile
  .openclaw/sandbox/docker-compose.yml
  AGENTS.md (template)

Rules

Always ask the wizard questions — don't assume
Never display full secret values
Check .gitignore and warn if sensitive files are NOT ignored
If running before a skill with network access — escalate all findings to CRITICAL
Generated files go to .openclaw/sandbox/ — never overwrite existing project files
Require user confirmation before writing any file
Credential rotation is always recommended for any exposed secret, even if local-only

FAQ

What does the setup-auditor skill do?

Audit your OpenClaw environment for credential leaks, unsafe defaults, and missing sandbox configuration. Wizard-style: answers questions about your setup and produces a fix checklist.

How do I install setup-auditor?

Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill setup-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/setup-auditor/ (personal) or .claude/skills/setup-auditor/ (project).

Which AI agents can use setup-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 setup-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 setup-auditor?

It is published by useai-pro in useai-pro/openclaw-skills-security. It has 470 recorded installs.

Popular security skills

View category →

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.

OfficialSecurity567K installs

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.

Security477.4K installs

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.

Security238.7K installs

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.

OfficialSecurity139.1K installs

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.

Security81.9K installs

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.

Security79.3K installs

setup-auditor

Install

Install

Describe the task

Review the result

SKILL.md

Setup Auditor

When to Use

Wizard Protocol (ask the user these questions)

Audit Protocol (4 steps)

Step 1: Credential Scan

Step 2: Config Audit

Step 3: Sandbox Readiness

Step 4: Persistence Check

Output Format

Rules

FAQ

More from useai-pro/openclaw-skills-security

skill-vetter

skill-auditor

skill-guard

prompt-guard

credential-scanner

dependency-auditor

Popular security skills

azure-compliance

minimal-run-and-audit

seo-audit

firebase-security-rules-auditor

audit

competitors