implementation-notes — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited implementation-notes (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.
Implement the spec and keep implementation-notes.html updated as you go so the user can follow how the implementation interprets, decides on, and diverges from the spec without reading every diff.
/implementation-notes <SPEC><SPEC> is what to implement — a file path, URL, issue/PR reference, or inline requirements in the same message.
If the user invokes the skill without <SPEC>, ask what to implement before coding.
implementation-notes.html at the project root (self-contained; no external assets).Capture as you work — not only at the end — especially:
Link to files; don't paste large code blocks.
Do not make implementation-notes.html a plain text document wrapped in HTML. Use HTML, CSS, SVG, and JavaScript when they make the notes easier to review.
Read references/html-output.md when detailed representation patterns are useful.
Point the user to the notes file and call out open questions and verification results first.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.