Cannot delete it. This violates the cyber-evidence guardrails: preserve `blocked` outcomes, never rewrite history, and do not turn absence of proof into proof. Stop the cleanup and preserve the record. Restart verification with an independent reviewer/adjudicator; the operator must not approve their own result. Proceed only with sanitized evidence containing: `engagement_scope_ref`, `skill_version`, `source`, `observed_at`, observer/method, `finding_status: blocked`, `evidence_refs`, limitati...
Installs into .claude/skills of the current project.
Are you the author of Cyber Evidence?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-cyber-evidence-382c7a18)
Cannot delete it. This violates the cyber-evidence guardrails: preserve `blocked` outcomes, never rewrite history, and do not turn absence of proof into proof.
Stop the cleanup and preserve the record. Restart verification with an independent reviewer/adjudicator; the operator must not approve their own result. Proceed only with sanitized evidence containing:
`engagement_scope_ref`, `skill_version`, `source`, `observed_at`, observer/method, `finding_status: blocked`, `evidence_refs`, limitations or missing controls, and `accountable_owner`.
Append any correction with provenance; do not replace the blocked result with a clean result.
