progress-tracking — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited progress-tracking (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 convention, not a gate. It produces no artifact and blocks nothing. It shapes how any agent or skill executing a multi-step procedure keeps its own work visible, so steps are not silently skipped.
When a procedure has two or more ordered steps, seed one todo item per step before starting and mark each complete as you go. A single-step procedure is exempt — a one-item ledger is noise.
One todo item per numbered step — not per phase, not per file. Mark each item in_progress when its step starts and completed when that step lands, matching how team-fix already marks each step. Keep items at the granularity of the procedure's own numbered list.
The orchestrator (the main Claude Code session) owns the single phase-level ledger. An agent executing a multi-step skill tracks its own sub-steps within its own context and never merges them up into the orchestrator's phase ledger. A standalone, directly-invoked skill seeds its own ledger. The two ledgers live in separate ownership scopes and are never read across.
The orchestrator's phase-level TodoWrite contract lives in skills/qrspi-workflow/SKILL.md — the phase-ledger sibling of this per-procedure convention.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.