spec-flow@1.0.0
CAUTION· static onlyPublisher claims: "轻量级 SDD（规范驱动开发）文档流水线。当用户描述一个新功能、产品想法或改进需求， 希望在动手写代码前先把"做什么/为什么/怎么做/拆成哪些任务"梳理清楚时使用。 自动完成 constitution → spec → plan → tasks 全流程，产出对齐 GitHub spec-kit 的 .specify/ 目录。 触发："我想加一个 XX 功能""帮我规划/设计 XX""这个需求先出个开发文档"。 不触发：纯代码实现、bug 修复、已有 spec 的局部修改、多智能体编排（那属于完整版 Harness 场景）。" 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-10 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. 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
No findings across 416 lines in 7 files.
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 denghuayuan: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.