handover — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited handover (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.
Update project files so the next session can pick up exactly where this one left off.
Before touching any files, reflect on what happened this session:
work/) that a fresh session would need to know about?Hold this in mind for the steps that follow.
Check every .md file in the project root. For each one, follow its update instructions (found at the top of the file). If a file has no explicit instructions, apply the default: check whether this session's work has made it stale, and update if so.
Common root files and their update logic:
| File | How to update |
|---|---|
| STATUS.md | Rewrite with current state (current position, recent decisions, next steps, open questions) |
| LEARNINGS.md | Append insights that need codifying later (e.g. system behaviours, agent failure modes that need rules). Do NOT use as a session log. |
| BACKLOG.md | Move new granular tasks or unresolved issues here. Keep STATUS.md "next steps" focused only on immediate session continuity. |
| CLAUDE.md | Update pointers — add new key files, remove stale pointers, update descriptions |
| README.md | Update if project description, status, or structure changed |
| PRD.md | Update if requirements shifted |
| ARCHITECTURE.md | Update if architectural decisions changed |
| ROADMAP.md | Update if chunks were completed, added, or reordered |
| ORCHESTRATION-PLAN.md | Mark completed chunks, update build progress |
Not every project has all of these. Check what exists.
CLAUDE.md points to key files beyond the root (e.g. work/ artefacts, orchestration logs). For each file CLAUDE.md references:
Lightweight structural checks to keep the project clean. Do not deep-read files — just verify structure and existence.
CLAUDE.md compliance — check against the lean pointer file standard:
Dangling pointers — verify every file path referenced in CLAUDE.md and STATUS.md:
Git hygiene — run git status and check for:
.DS_Store, *.swp, __pycache__/, .pyc, etc.) — if found, add them to .gitignoreTell the user:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.