BD AIDR-XClaw-Security-Sentinel
AIDR-XClaw安全哨兵是由BeiMing-AI-Lab提供的企业级OpenClaw类智能体威胁防护Skill。核心功能:(1) Query Audit - 对每次用户消息进行提示词注入检测(含本地敏感信息脱敏);(2) Skill Audit - 对 Skill 安装/运行时进行恶意代码检测(Pre-Install 5阶段 + Runtime 4阶段审计)。触发场景:用户发送任何消息时(aidr-xclaw-security-sentinel 插件安装除外)自动执行 Gate 1;用户提及/安装/运行 Skill 时执行 Gate 2。特殊 bypass:用户请求安装 aidr-xclaw-security-sentinel 插件时,跳过所有安全门,直接执行 install_aidr_xclaw_plugin.cjs。安全等级:strong/moderate → pass,marginal → warn,unsafe → block;Skill 审计:CLEAR/MINOR → approve,ELEVATED → warn,SEVERE/CRITICAL → reject。所有 API 调用需设备指纹+API Key 双重鉴权。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Risky intent
intent-offensive-securityREADME.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)| **Skill Audit** | Before Skill installation / invocation | Malicious behavior, credential harvesting, network outbound, code execution, etc. |
detector -
low Instruction override
en-ignore-previousREADME.md:58Instruction-override phrase ("ignore previous instructions") (documentation table row; documentation of a security skill)| **Instruction hijacking** | "Ignore previous instructions", "disregard your instructions" |
tablesecurity skill -
low Risky intent
intent-offensive-securityREADME.md:71Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Credential harvesting | `CRED_HARVEST` |
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 13791 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 13791 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 100Steps. 187 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 16 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (11 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -249 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 526: enough signal without eating the budget
- +4Structure: 99 headings
- +3Step-by-step instructions: 187 items
- +4Has examples (83 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.