bug-fixing@1.0.0
CAUTION· static onlyPublisher claims: "Zero-regression bug fix workflow: triage → reproduce → root cause → impact analysis → fix → verify → knowledge deposit → self-reflect. Use when: - Feature br..." 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-12 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. Notable findings: Rule modification attempt; Rule modification attempt; Rule modification attempt. 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
│ Rule 5: After fix, MUST run regression verification │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 3: MUST trace IMPACT CHAIN (code → data → time → event) │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 1: Root cause MUST pass 4 gates before fixing │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 2: Scope MUST pass 5 gates before fixing │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.│ Rule 4: MUST predict side effects + check blind spots before coding │Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 yun520-1: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.