cli-skill-release@1.9.12
CAUTIONPublisher claims: "Release engineering for zero-dependency Python CLI agent skills: releaser.py validates publish-readiness (a 0-100 score with real functional checks that actually boot your CLI), inventory/gap market intelligence, scaffold, CI, LICENSE(MIT-0), marketplace publish, readiness badge, and chain-propagation tooling. Pre-publish checklist, skill publish checklist, "is my skill ready to publish?", "what am I missing before I push this skill to GitHub?", audit skill against Agent Skills spec, fix LICENSE shows Other, pytest exit code 2, CI keeps failing, ClawHub/SkillHub/agentskills.io publish guide, skill discoverability, quality gate. 把"以 Python CLI 形式交付的 WorkBuddy 技能做成可发布项目并上架"的全流程固化。 核心是零依赖 releaser.py:validate 主动扫描发布陷阱并给 0-100 就绪分(含★功能级验证真跑 CLI)、 inventory 治理本机技能、gap 市场缺口、selfcheck 零依赖、scaffold 起项目、bump 升版本、 release 推送(需--push)/发布(需--publish)、badge 链回徽章(便于引用致谢)、promote 发布说明工具箱、 diagnose 长尾诊断(症状→根因→修复)、preflight 市场定制上架清单。 当用户说"构建/发布技能""技能上架""发布技能""publish skill""上架 skill""技能发布前检查清单" "校验技能能不能发""技能质量门禁""skill CI gate""LICENSE 显示 Other""CI 一直红""pytest exit code 2" "零依赖 Python 工具""技能搜不到"时触发。 本技能是 skill-creator(写技能)的**发布阶段搭档**:它管"写好",本技能管"发出去 + 懂市场 + 帮你被找到 + 链回致谢"。" 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-10-30 and scored it 53/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: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. 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
What would make this Verified
27 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim cdhewei: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.