defect-prevention-expert@4.2.0
CAUTION· static onlyPublisher claims: "全生命周期质量保障专家，覆盖需求、设计、编码、测试、上线、运维全阶段的质量保障活动。 融合缺陷预防（逆向操作、依赖踏空、并发冲突、新旧兼容、状态迁移、因果判定）与质量度量、持续改进三大支柱， 帮助团队建立「预防-评审-度量-改进」的质量闭环，实现软件质量的持续提升。 Use when: - 需求/设计/编码/测试..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-13 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Rule modification attempt; Rule modification attempt; Rule modification attempt. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
│ Rule 4: 不能只提问题不给建议，每个风险至少附带一条改进措施 │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 3: 每个发现必须标注严重程度（P0-P3）和优先级 │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 2: 必须覆盖六大方法论（逆向/依赖/并发/兼容/状态/因果），按阶段侧重应用 │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 1: 必须先明确质量保障类型（预防/评审/度量/改进），再路由到对应工作流，不可混用流程 │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 5: 必须区分"设计意图"和"实现风险"，避免混淆 │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zengqch: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.