verify-conclusion@1.3.0
VERIFIED· install onlyPublisher claims: "诊断结论、调研发现或推断出炉后就地开始自检:先逐环拆推理链,再换思路从零盲推;审查对象是计划/方案/变更单时第一轮就先建外部完备性基线再逐维对照,拦截过早结论、未经验证的假设与因果混淆。用户说「确认吗/再验一下/复查」也触发。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 1.2.0
vet-skills diff verify-conclusion 1.2.0 1.3.0In the sandbox, this version reached for nothing 1.2.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-16 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
ΔpartFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.catch-up window, how the systemd unit is produced, backup duration, interpreter identity, `.env`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.