content-publish-lifecycle@1.0.9
CAUTIONPublisher claims: "Turn a finished technical plan into something publishable by running it through one repeatable pipeline: design, build, check, verify, release and capture. Each stage has a defined exit condition, so nothing ships unchecked and lessons get written down afterwards. Use when a plan is done but the path to publication is unclear, or when a release checklist keeps being rebuilt from memory. 把技术方案 / 设计从「设计 → 落地 → 检查 → 验证 → 发布 → 沉淀」串成一条可复用发布流水线，用于回答「方案做完了怎么变成能发的东西」「发出去之前该查什么」这类问题" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-06 and scored it 67/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 775 lines in 11 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
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zhaoxinghua09-cell: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.