critical-writing@1.0.0
CAUTION· static onlyPublisher claims: "多角色辩论写作工作流。通过"前置三问 → 规划 → 分步写作 → 辩论法庭 → 综合改写" 的闭环流程,让多个批评者角色互相对抗,在争论中打磨出高质量内容。 核心差异:不是单个名人单向批评,而是 2-3 个批评者就同一篇稿子展开辩论—— 一方指出问题,另一方反驳或补充,最终从争论中提炼出真正有价值的改写方向。 触..." 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-22 and scored it 71/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
# Test Cases — critical-writing v2.0Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.No other findings across 1,505 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
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim boboy-j: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden zero-width characters detected≈ +2 on the totalKeep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.