Uncertainty Verification
v1.0.0事实核查与幻觉检测。在生成内容后检测并纠正可能的幻觉、编造或不准确信息。 触发条件：(1) 生成技术内容后 (2) 提供统计数据时 (3) 引用人物/事件时 (4) 生成代码示例后
⭐ 0· 309·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (fact‑check / hallucination detection) match the SKILL.md: it provides a verification checklist, triggers, and a validation workflow. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions stay within fact‑checking: check claims, verify numbers, validate citations, run code examples, and confirm external operations. Note: some steps (e.g., "run generated code" or "confirm API/file was created") implicitly require runtime execution or network/file access; the skill does not request those capabilities explicitly, so the agent will need separate permissions to actually perform those checks.
Install Mechanism
No install spec and no code files — instruction‑only skill. This minimizes disk/write risk and there is nothing downloaded or installed.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportionate to its stated purpose (a procedural guideline for verification).
Persistence & Privilege
always:false and default autonomous invocation are set. The skill does not ask for persistent system presence or to modify other skills or global agent configs.
Assessment
This skill is coherent and low‑risk as an instruction bundle: it teaches the agent how to verify outputs, labels confidence, and when to check sources. Before enabling it, consider: (1) if you allow the agent to actually execute generated code or access the network/filesystem, ensure those actions run in an isolated/sandboxed environment (verifying code can execute arbitrary commands); (2) the skill assumes the agent has permissions to perform external checks — grant network or file access only when you trust the execution environment; (3) treat the embedded statistic ("22% failure rate") as illustrative guidance, not an authoritative metric. If you want stricter control, require explicit user approval before the agent runs code or performs external validations.Like a lobster shell, security has layers — review code before you run it.
latestvk9763pmbtzbrt16vft5a9jsdt182ndpe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.