workflow-capture — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited workflow-capture (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.
Maintain an append-only journal that survives compaction and /clear, capturing the signal (decisions, sequencing, corrections, dead ends) that should become a skill. Do not log keystrokes; the transcript already does that at the wrong altitude. Capture why, not just what.
figma-site-redesign)._worklogs/YYYY-MM-DD-<slug>/WORKLOG.md.Every entry carries exactly one tag:
Append, never rewrite history.
## [YYYY-MM-DD HH:MM] TAG
One-line summary.
Optional result and fix or lesson.
Tags: comma, separated, keywordsAppend an entry the moment one of these happens:
Keep entries short. The lesson matters, not the prose.
Before any compaction or /clear, write a CHECKPOINT entry: current state, open threads, next intended action. On resume in a fresh window, read the worklog and continue from the last CHECKPOINT plus accumulated tags.
The context window is volatile and mostly noise. A durable tagged journal is the only thing that lets a workflow survive a context reset and later become a skill that makes the next run cheaper and more correct.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.