Token导航 LogoToken导航

Agent Skill · 研究检索

skill-safety-auditor(技能安全审核员)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

skill-safety-auditor 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 14,206。

总安装 8,739周安装 357GitHub Stars 公开资料未说明下载 2,799核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:skill-safety-auditor(技能安全审核员)
来源仓库:https://github.com/harrylabsj/skill-safety-auditor
安装命令:
openclaw skills install skill-safety-auditor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install skill-safety-auditor

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

对技能进行全面安全审核识别漏洞和不安全模式。适用于安全相关技能的深度合规检查。skill-safety-auditor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。通过 clawhub 安装,支持多维度威胁建模。建议结合渗透测试等实际验证手段交叉确认。注意部分高危模式可能被标记为误报需人工判断。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install skill-safety-auditor;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

skill-safety-auditor 怎么安装?

在终端执行 openclaw skills install skill-safety-auditor。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

skill-safety-auditor 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

skill-safety-auditor 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

skill-safety-auditor 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

skill-safety-auditor 用的人多吗?

公开数据是累计安装 8,739 次,近一周安装 357 次,下载 2,799 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

skill-safety-auditor 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
skill-safety-auditor

技能安全审核员 · 本页

8,739—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
skill-safety-auditor
description
Perform comprehensive security audits on skills to identify vulnerabilities, unsafe patterns, and compliance issues. Use when auditing skills for security, checking for hardcoded secrets, injection risks, or before releasing skills.

Skill Safety Auditor

Overview

The skill-safety-auditor skill performs comprehensive security audits on skills to identify vulnerabilities, unsafe code patterns, permission issues, and compliance violations. It helps ensure skills meet security standards before release or deployment.

When to Use

  • During skill development for early issue detection
  • Before releasing a new skill to production
  • As part of the release approval process
  • When the user asks to "audit" or "security check" a skill
  • During periodic security reviews
  • When reviewing third-party skills

Core Concepts

Audit Types

TypeDescriptionSpeed
quick-scanFast surface-level check~1s
auditComprehensive analysis~5-10s
reportFull audit with JSON output~10s

Vulnerability Categories

CategoryChecks ForSeverity
secretsHardcoded API keys, passwords, tokensCritical
injectionCommand injection, path traversalHigh
permissionsUnsafe file permissionsMedium
dependenciesKnown vulnerable dependenciesHigh
networkInsecure HTTP connectionsLow

Severity Levels

  • Critical: Immediate security risk, must fix before release
  • High: Significant risk, strongly recommended to fix
  • Medium: Moderate risk, should address
  • Low: Minor issue, consider fixing
  • Info: Informational, optional to address

Input

Accepts:

  • Path to skill directory
  • Audit type specification
  • Output format preference
  • Vulnerability type filters

Output

Produces:

  • Console output with findings
  • JSON audit reports
  • Summary statistics
  • Pass/fail status

Workflow

Quick Security Check

  1. Run quick-scan on target skill
  2. Review any immediate issues
  3. Address critical/high findings

Comprehensive Audit

  1. Run full audit with verbose output
  2. Review all findings by severity
  3. Generate JSON report for records
  4. Address findings in priority order
  5. Re-run audit to verify fixes

Pre-Release Audit

  1. Audit skill with all checks enabled
  2. Generate formal report
  3. Review with team
  4. Fix all critical/high issues
  5. Document accepted low-risk items

Commands

Quick Scan

./scripts/quick-scan.sh /path/to/skill

Full Audit

./scripts/audit-skill.sh /path/to/skill --verbose

Generate Report

./scripts/audit-skill.sh /path/to/skill --output report.json

Filter by Type

./scripts/audit-skill.sh /path/to/skill --types secrets,injection

List Past Audits

./scripts/list-audits.sh [--skill <name>] [--since 2024-01-01]

Output Format

Console Output

🔍 Starting security audit: my-skill
================================
✅ SKILL.md exists
Scanning for secrets...
Scanning for injection vulnerabilities...
[high] injection: eval() detected
  File: src/utils.js:15
  Recommendation: Avoid eval(), use safer alternatives

================================
Validation complete:
  Errors: 0
  Warnings: 1
❌ Validation FAILED

JSON Report

{
  "audit_id": "AUDIT-20240313-001",
  "skill": "my-skill",
  "timestamp": "2024-03-13T10:30:00Z",
  "summary": {
    "critical": 0,
    "high": 1,
    "medium": 2,
    "low": 3,
    "info": 1
  },
  "findings": [
    {
      "id": "SEC-001",
      "severity": "high",
      "type": "injection",
      "file": "src/utils.js",
      "line": 15,
      "description": "eval() detected - potential code injection",
      "recommendation": "Avoid eval(), use safer alternatives"
    }
  ],
  "passed": false,
  "recommendations": [
    "Remove eval() from src/utils.js:15",
    "Add input validation to all user inputs"
  ]
}

Audit Checks

Secrets Detection

  • API keys and tokens
  • Database passwords
  • Private keys
  • Access credentials
  • Environment variable patterns

Code Safety

  • eval() usage
  • Function constructor
  • setTimeout/setInterval with strings
  • Child process execution
  • Dynamic code execution

File Permissions

  • World-writable files
  • Executable permissions on data files
  • Sensitive file accessibility

Dependencies

  • Known CVE vulnerabilities
  • Deprecated packages
  • Potentially dangerous packages

Network Security

  • HTTP vs HTTPS URLs
  • Insecure API endpoints
  • Missing certificate validation

Quality Rules

  • Always run before releasing skills
  • Fix all critical/high findings
  • Document accepted risks
  • Re-audit after fixes
  • Keep audit history

Good Trigger Examples

  • "Audit this skill for security issues"
  • "Security check before release"
  • "Scan for hardcoded secrets"
  • "Check for injection vulnerabilities"
  • "Run security audit on skill X"

Limitations

  • Static analysis only; cannot detect runtime vulnerabilities
  • May produce false positives for legitimate patterns
  • Cannot verify external service security
  • Does not test actual runtime behavior
  • Limited to known vulnerability patterns

Resources

scripts/

  • audit-skill.sh - Full security audit
  • quick-scan.sh - Fast security check
  • list-audits.sh - View audit history
  • test.sh - Test skill functionality

references/

  • Security best practices
  • Common vulnerability patterns
  • OWASP guidelines reference

平台分布

OpenClaw

82.14%
按下载量换算2,299

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills