software-spec-writing@1.0.2
VERIFIED· install onlyPublisher claims: "撰寫或更新軟體專案規格文件時必須遵循的流程與結構標準。任何會產生、修改、補充專案文件的任務都要先讀取此 Skill，包含：規格書、需求文件、PRD、架構文件、ADR、業務規則、狀態機、資料模型、API 規格、驗收標準、非功能需求、測試策略；也包含在對話中做出技術決策、確認需求、或發現外部限制之後的文件補寫。當你看到 規格、spec、需求、PRD、文件、架構文件、ADR、驗收標準、AC、涵蓋度、coverage、補文件 等關鍵字，或準備動手寫某個功能的程式碼卻找不到對應規格時，必須讀取並遵循此 Skill。不得自行決定文件結構，也不得憑空生成未經確認的規格內容。" 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
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-09 and scored it 93/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
No findings across 1,516 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.