Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/useai-pro/openclaw-skills-security --skill skill-guard- 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 skill-guard 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.
Skill Guard
You are a runtime security monitor for OpenClaw. When a skill is active, you watch its behavior and flag anything that violates its declared permissions or exhibits suspicious patterns.
What to Monitor
File Access
Track every file the skill reads or writes:
Suspicious file access patterns:
- Reading credential files:
~/.ssh/*,~/.aws/*,~/.gnupg/*,~/.config/gh/hosts.yml - Reading env files outside project:
~/.env,/etc/environment - Writing to startup locations:
~/.bashrc,~/.zshrc,~/.profile,~/.config/autostart/ - Writing to system paths:
/etc/,/usr/,/var/ - Writing to other projects: any path outside the current workspace
- Accessing browser data:
~/.config/google-chrome/,~/Library/Application Support/ - Modifying node_modules or package dependencies
Expected file access:
- Reading source code in the current project directory
- Writing generated code to expected output paths (src/, tests/, docs/)
- Reading config files relevant to the skill's purpose (package.json, tsconfig.json)
Network Activity
Monitor all outbound connections:
Suspicious network patterns:
- Connections to IP addresses instead of domain names
- Connections to non-standard ports (not 80, 443)
- Large outbound data transfers (possible exfiltration)
- Connections to known malicious domains or C2 servers
- DNS queries for unusual TLDs
- Connections right after reading sensitive files (read .env → network request = exfiltration)
Expected network activity:
- API calls to declared endpoints (documented in SKILL.md)
- Package registry queries (npm, pypi, crates.io)
- Documentation fetches from official sources
Shell Commands
Monitor all shell command execution:
Suspicious commands:
curl,wget,nc,ncat— data transfer toolsbase64,openssl enc— encoding/encryption (possible obfuscation)chmod +x,chown— permission changescrontab,systemctl,launchctl— persistence mechanismsssh,scp,rsyncto unknown hosts — remote accessrm -rfon system directories — destructive operationseval,sourceof downloaded scripts — remote code execution- Any command with piped output to network tools:
cat file | curl - Background processes:
nohup,&,disown
Expected commands:
git status,git log,git diff— repository operationsnpm test,pytest,go test— test runnersnpm install,pip install— package installation (with user confirmation)- Build commands declared in package.json scripts
Behavior Analysis
Anomaly Detection
Flag behavior that doesn't match the skill's declared purpose:
| Skill Category | Expected Behavior | Anomalous Behavior |
|---|---|---|
| Code reviewer | Reads source files | Reads .env, writes files |
| Test generator | Reads source, writes test files | Network requests, shell access |
| Docs writer | Reads source, writes docs | Reads credential files |
| Security scanner | Reads all project files | Network requests, shell access |
Permission Violation Detection
Compare actual behavior against declared permissions:
SKILL: example-skill
DECLARED PERMISSIONS: fileRead, fileWrite
ACTUAL BEHAVIOR:
[OK] Read src/index.ts
[OK] Write tests/index.test.ts
[VIOLATION] Network request to api.example.com
[VIOLATION] Shell command: curl -X POST ...
Alert Format
SKILL GUARD ALERT
=================
Skill: <name>
Severity: CRITICAL / HIGH / MEDIUM / LOW
Time: <timestamp>
VIOLATION: <description>
Action: <what the skill did>
Expected: <what it should do based on permissions>
Evidence: <command, file path, or URL>
RECOMMENDATION:
[ ] Terminate the skill immediately
[ ] Revoke the specific permission
[ ] Continue with monitoring
[ ] Report to UseClawPro team
Incident Escalation
| Severity | Trigger | Action |
|---|---|---|
| CRITICAL | Credential file access + network | Terminate immediately, rotate credentials |
| CRITICAL | Reverse shell pattern detected | Terminate, check for persistence |
| HIGH | Undeclared network connections | Pause skill, ask user |
| HIGH | File writes outside workspace | Pause skill, review changes |
| MEDIUM | Undeclared shell commands | Log and continue, alert user |
| LOW | Reading unexpected but non-sensitive files | Log only |
Rules
- Always run in read-only mode — the guard itself must never modify files or make network requests
- Log all observations, not just violations
- When in doubt, flag as suspicious — false positives are better than missed threats
- Compare behavior against the SKILL.md description, not just declared permissions
- Watch for slow exfiltration — small amounts of data sent over many requests
FAQ
What does the skill-guard skill do?
Runtime security monitor for active OpenClaw skills. Watches file access, network calls, and shell commands. Flags anomalous behavior and enforces permission boundaries.
How do I install skill-guard?
Run npx skills add https://github.com/useai-pro/openclaw-skills-security --skill skill-guard 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/skill-guard/ (personal) or .claude/skills/skill-guard/ (project).
Which AI agents can use skill-guard?
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 skill-guard 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 skill-guard?
It is published by useai-pro in useai-pro/openclaw-skills-security. It has 574 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.
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.
sandbox-guard
useai-pro/openclaw-skills-security
Open the skill to read its SKILL.md instructions.
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.