delivery-spec-audit@1.0.0
VERIFIEDPublisher claims: "交付规格覆盖审计器。当一次 Coding Agent 开发任务完成(或即将宣布完成)时, 从会话记录(CC JSONL / OpenClaw trajectory)确定性抽取「做了什么、改了哪些文件、 验证了几次」的原始证据,再对照规格清单逐条判定覆盖情况——主目标之外的 接口兼容、状态一致、错误处理、回归风险等互依规格最容易被"逐条打勾式交付"漏掉。 先追问规格、再抽证据、后做语义判定,输出覆盖矩阵与反例场景。 触发词: 交付审计, 规格覆盖, 交付前检查, 这次改动覆盖了哪些需求, 完成了吗, 交付质量, spec coverage, delivery audit, coverage check, task complete audit, 交付核对, 需求覆盖, 上线前核对, 改动核对。 激活条件: 需要有明确的"一次开发任务/一轮改动"语境(用户给出任务描述、 会话记录路径或仓库路径);纯代码问答、与交付无关的闲聊不触发。 NOT for: 静态代码质量评分(用 code-review-ProMax)、Skill 质量评审 (用 skill-review-pro)、上下文预算分析(用 context-budget-analyzer)、 全仓库架构文档生成(用 project-doc-analyst)。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-11-02 and scored it 86/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
No other findings across 531 lines in 2 files.