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: what was created or significantly changed? What decisions were made? What was discovered or learned? Were new key files created (e.g. in work/) that a fresh session would need to know about?
Check every .md file in the project root. Follow each file's own update instructions (found at the top of the file); if a file has none, update it whenever this session's work has made it stale.
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 only what passes the file's inclusion criteria — a durable insight a future session would act on. Most sessions add nothing. 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.
For each file CLAUDE.md references beyond the root (e.g. work/ artefacts, orchestration logs): does the pointer still point to the right location? Has this session's work made the file stale? Update if needed.
Structural checks only — don't deep-read files.
git status: junk files (.DS_Store, *.swp, __pycache__/, .pyc) → add to .gitignore; untracked files that don't look like this session's work → flag to the user, don't delete.Tell the user: which files were checked; which were updated and briefly what changed; hygiene issues found (with actions taken or flagged); anything that needs the user's judgement.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.