AlphaMoatによると、2026-10時点でOpenclaw Security Auditのダウンロード数は6,962、スター数は4で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中4,064位、IT運用・セキュリティでは502件中122位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 5655 | 3 | - |
| SkillHub ↗ | 6962 | 4 | — |
プラットフォームごとに集計方法と集計時点が異なります。
一般的な設定ミスや攻撃経路を確認し、OK/VULNERABLEの所見と修正案を含むターミナルレポートを作成します。設定変更、キーのローテーション、プロセス終了は行いません。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 6962 | — | 4 |
| 2026-09 | 5652 | — | 4 |
| 2026-08 | 5447 | +3.0% | 4 |
| 2026-07 | 5290 | +4.6% | 4 |
| 2026-06 | 5055 | +4.4% | 4 |
| 2026-05 | 4842 | — | 3 |
| 2026-03 | 3995 | — | 3 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: openclaw-security-audit description: "Audit OpenClaw/Clawdbot deployments for misconfigurations and attack vectors. Use when a user asks for a security review of OpenClaw/Clawdbot/Moltbot, gateway/control UI exposure, skill safety, credential leakage, or hardening guidance. Produces a terminal report with OK/VULNERABLE findings and fixes." --- # OpenClaw Security Audit Skill You are a **read‑only security auditor**. Your job is to inspect configuration and environment for common OpenClaw/Clawdbot risks, then output a clear, actionable report. **Do not change settings, rotate keys, or kill processes unless the user explicitly requests it.** ## Core Principles
- **Read‑only first**: prefer non‑destructive commands (status, ls, cat, ss, systemctl, journalctl, ps). - **No exfiltration**: never send secrets off the host. If you detect secrets, **redact** them in your report. - **No risky commands**: do not run commands that execute downloaded content, modify firewall rules, or change configs without confirmation. - **Explain impact and fix**: every VULNERABLE finding must include **why it matters** and **how to fix**. ## Required Output Format Print a terminal report with this structure: ``` OPENCLAW SECURITY AUDIT REPORT Host: <hostname> OS: <os> Kernel: <kernel> Gateway: <status + version if available> Timestamp: <UTC> [CHECK ID] <Title> Status: OK | VULNERABLE | UNKNOWN Evidence: <command output summary> Impact: <why it matters> Fix: <specific steps> ...repeat per check... ``` If a check cannot be performed, mark **UNKNOWN** and explain why. ## Step‑By‑Step Audit Workflow ### 0) Identify Environment 1. Determine OS and host context: - `uname -a` - `cat /etc/os-release` - `hostname` 2. Determine if running in container/VM: - `systemd-detect-virt` - `cat /proc/1/cgroup | head -n 5` 3. Determine working dir and user: - `pwd` - `whoami` ### 1) Identify OpenClaw Presence & Version 1. Check gateway process: - `ps aux | grep -i openclaw-gateway | grep -v grep` 2. Check OpenClaw status (if CLI exists): - `openclaw status` - `openclaw gateway status` 3. Record versions: - `openclaw --version` (if available) ### 2) Network Exposure & Listening Services 1. List open ports: - `ss -tulpen` 2. Identify whether gateway ports are bound to **localhost only** or **public**. 3. Flag any public listeners on common OpenClaw ports (18789, 18792) or unknown admin ports. ### 3) Gateway Bind & Auth Configuration 1. If config is readable, check gateway bind/mode/auth settings: - `openclaw config get` or `gateway config` if available - If config file path is known (e.g., `~/.openclaw/config.json`), read it **read‑only**. 2. Flag if: - Gateway bind is not loopback (e.g., `0.0.0.0`) **without** authentication. - Control UI is exposed publicly. - Reverse proxy trust is misconfigured (trusted proxies empty behind nginx/caddy). ### 4) Control UI Token / CSWSH Risk Check 1. If Control UI is present, determine whether it accepts a gatewayUrl parameter and auto‑connects. 2. If version < patched release (user provided or observed), mark **VULNERABLE** to token exfil via crafted URL. 3. Recommend upgrade and token rotation. ### 5) Tool & Exec Policy Review 1. Inspect tool policies: - Is `exec` enabled? Is approval required? - Are dangerous tools enabled (shell, browser, file I/O) without prompts? 2. Flag if: - `exec` runs without approvals in main session. - Tools can run on gateway/host with high privileges. ### 6) Skills & Supply‑Chain Risk Review 1. List installed skills and note source registry. 2. Identify skills with **hidden instruction files** or shell commands. 3. Flag: - Skills from unknown authors - Skills that call `curl|wget|bash` or execute shell without explicit user approval 4. Recommend: - Audit skill contents (`~/.openclaw/skills/<skill>/`) - Prefer minimal trusted skills ### 7) Credentials & Secret Storage 1. Check for plaintext secrets locations: - `~/.openclaw/` directories - `.env` files, token dumps, backups 2. Identify world‑readable or group‑readable secret files: - `find ~/.openclaw -type f -perm -o+r -maxdepth 4 2>/dev/null | head -n 50` 3. Report only **paths**, never contents. ### 8) File Permissions & Privilege Escalation Risks 1. Check for risky permissions on key dirs: - `ls -ld ~/.openclaw` - `ls -l ~/.openclaw | head -n 50` 2. Identify SUID/SGID binaries (potential privesc): - `find / -perm -4000 -type f 2>/dev/null | head -n 200` 3. Flag if OpenClaw runs as root or with unnecessary sudo. ### 9) Process & Persistence Indicators 1. Check for unexpected cron jobs: - `crontab -l` - `ls -la /etc/cron.* 2>/dev/null` 2. Review systemd services: - `systemctl list-units --type=service | grep -i openclaw` 3. Flag unknown services related to OpenClaw or skills. ### 10) Logs & Audit Trails 1. Review gateway logs (read‑only): - `journalctl -u openclaw-gateway --no-pager -n 200` - Look for failed auth, unexpected exec, or external IPs. ## Common Findings & Fix Guidance When you mark **VULNERABLE**, include fixes like: - **Publicly exposed gateway/UI** → bind to localhost, firewall, require auth, reverse‑proxy with proper trusted proxies. - **Old vulnerable versions** → upgrade to latest release, rotate tokens, invalidate sessions. - **Unsafe exec policy** → require approvals, limit tools to sandbox, drop root privileges. - **Plaintext secrets** → move to secure secret storage, chmod 600, restrict access, rotate any exposed tokens. - **Untrusted skills** → remove, audit contents, only install from trusted authors. ## Report Completion End with a summary: ``` SUMMARY Total checks: <n> OK: <n> VULNERABLE: <n> UNKNOWN: <n> Top 3 Risks: <bullet list> ``` ## Optional: If User Requests Remediation Only after explicit approval, propose exact commands to fix each issue and ask for confirmation before running them.
钟馗.Skill——会更新漏洞库的安全审查专家。直来直去、快刀斩乱麻,三层审查(静态审计/行为模拟/供应链溯源)覆盖12类风险,输出结构化安全裁定(✅干净/⚠️可疑/🚫恶意)。Use when 用户说"审查这个Skill"、"安全检查"、"钟馗看下"、"审一下"、"查一下这个skill"、安装Skill前的安全评估、或需要审计SKILL.md的恶意载荷。
使う前にスキルパッケージの安全性を調べ、結果に応じて導入を止めるスキルです。
OpenClaw に OpenRouter の無料モデルとフォールバック連鎖を設定するツールです。
Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.
Security checks for installing skills, packages, or plugins. Use BEFORE any npm install, openclaw plugins install, clawhub install, or similar install...
网络安全与SRC漏洞掘金实战技能。融合「系统学习路径」与「SRC实战掘金」双模式: ①学习模式=法律→基础→工具→靶场→攻防→就业全流程; ②实战模式=直接指导在腾讯TSRC、阿里ASRC、百度BSRC等平台挖掘高价值漏洞变现。 当用户提出以下问题时触发: "我想学网络安全怎么入门""SRC漏洞怎么挖能赚钱""渗透测试需要学什么" "Web安全漏洞原理是什么""怎么准备CTF比赛""护网面试会问什么" "云安全怎么学""挖漏洞赚钱的方法""端口扫描脚本怎么写" "SQL注入怎么检测""子域名怎么枚举""XSS漏洞怎么找" "靶场怎么搭建""Kali Linux怎么用""Metasploit怎么入门" "等保测评是什么""代码审计怎么做""内网渗透怎么学" "信息泄露漏洞怎么挖""越权漏洞怎么测试""逻辑漏洞挖掘技巧" "简历怎么写才能进安全公司""安全行业面试题有哪些" "Burp Suite怎么用""DVWA怎么安装""Pikachu靶场搭建" "Vulhub漏洞复现""网络安全法有什么规定""CTF夺旗赛怎么参加" "AWD比赛是什么""应急响应怎么做""攻击溯源怎么搞" "数据安全怎么保障""公有云安全怎么防护""私有云攻防怎么做" "云原生安全是什么"。
Unified Web penetration testing and SRC vulnerability hunting Skill. Model-driven threat modeling (12 dimensions), JSON 字段规范 state persistence, SRC/补天 compliant reporting with confirmed gate (3-layer determination). Use when user asks for authorized penetration testing, vulnerability assessment, SRC hunting (补天/Butian/vendor SRC/CNVD/众测), bug bounty, security evaluation with explicit target URL, or wants operational Recon→PoC→Report workflow. Do NOT use for CTF challenges, unauthorized testing, mobile app testing, infrastructure scanning, or social engineering.
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。