Document Template System — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Document Template System (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.
A template is not a filled-out document with blanks. It is a decision made once so the team does not have to make it again. The best template systems are lightweight, self-explanatory, and maintained by one person.
Audit what documents the team actually produces. List the top 10 by frequency. Build templates only for the top 5. Attempting to template everything produces a system nobody uses.
For each candidate template, answer:
Every template should contain four elements:
Documentation style is a team-level decision, not a document-level decision. Establish once and enforce everywhere:
A file name should answer three questions without opening the file: what is it, who owns it, and how current is it.
Default format: [DocumentType]-[Subject]-[Owner]-[Date or Version] Example: Report-Q2-Revenue-Ouellet-2026-06
Avoid descriptors like 'final', 'final-v2', or 'latest' in file names — they are lies waiting to happen.
Assign one maintainer per template library. Schedule a quarterly review. At each review: retire templates unused in the past year, update style conventions, and collect one piece of author feedback per active template. A system that cannot be maintained will be abandoned.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.