writeup-sop — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited writeup-sop (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
HARD RULE: every publication-critical result metric or statistical claim in a report must be traceable via mcp__verify__check_provenance. Context numbers (dates, versions, seed counts, baseline counts, model sizes, timeouts) should be accurate, but they are not provenance gates by themselves. The PreToolUse hook may block obvious unprovenanced labelled metrics on file write.
Workflow:
mcp__verify__check_provenance. Missing provenance means re-run, downgrade the claim to exploratory/context, or remove it.$bt-tournament, include the BT strength / interval only when it is part of the argument. Do not turn every rank, seed count, or version number into a hard provenance gate.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.