operations-on-docs-ownership — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited operations-on-docs-ownership (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.
Distribution projects must have requirements spec as minimum docs. New or small projects: one requirements spec file is minimum acceptable form. Larger projects may split requirements spec across multiple docs. Requirements spec fixes accepted purpose, premise, and constraints from issues. For behavior change, bug fix, or spec change: update requirements spec first then update code and tests to implement and verify that spec delta
Li+ behavior and governance decisions belong in numbered requirements plus the corresponding operational docs. Standalone memo or experiment log may exist, but it is not source of truth. Requirements spec may be split across multiple numbered docs when it improves readability.
Docs check on commit: If this commit changes spec (Li+*.md) or behavior code = verify docs/ has corresponding update. If not yet updated = add docs update before push. Do not defer to a separate PR.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.