wrap-up
End-of-session persistence of the session's work to Obsidian as a session note per project and the daily note. Use when closing a work session and recording what it changed. Not for mid-session checkpoints, conversation handoffs, standalone project or meeting notes, or repository-wide project context.
How do I install this agent skill?
npx skills add https://github.com/adeonir/agent-skills --skill wrap-upIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill automates documenting work sessions to Obsidian by reading a handoff file and managing a local project registry via a bundled Python script. It follows strict guidelines to filter out process noise and ensure only project-relevant facts are recorded.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Wrap Up Session
Triggers
- End-of-session command (
/wrap-up) → run the workflow below
End-of-session documentation to Obsidian. The skill is single-trigger: every invocation runs the full workflow.
Workflow
mapping → handoff:Load → notes (compose) → handoff:Cleanup → archive offer
Copy this checklist and tick it off:
Progress:
- [ ] Step 1: Resolve the project entry
- [ ] Step 2: Load the session's handoff blocks
- [ ] Step 3: Write the session note and the daily note
- [ ] Step 4: Remove the session's handoff blocks
- [ ] Step 5: Collect past-month daily notes
- [ ] Step 6: Report
Step 1. Resolve the project. Load mapping.md and resolve the project entry and the base tags. When the registry or the entry is missing, load bootstrap.md as mapping directs. Every later step depends on this output. Done when the entry's name, obsidian.path, and tags are known.
Step 2. Load the handoff. Load handoff.md and run its Load phase — the blocks of the consolidated handoff at .artifacts/HANDOFF.md that this session worked on, when present, feed the note content. They enter as a claim to check, not as authority: record the current state where the session's work superseded a claim, and report a claim only when the session's work does not explain the contradiction. A block that describes work this session did not do is not used and not removed. Done when the fields of this session's blocks are in working context, or the handoff is known to be absent or unrelated.
Step 3. Write the notes. Load notes.md and write the Obsidian session note and the daily note. If a draft fails the check in notes.md, rewrite it and check again before writing. Done when each configured write returned success or a failure to report.
Step 4. Remove the handoff blocks. Run the Cleanup phase of handoff.md — remove this session's blocks once every configured note write succeeded. Done when this session's blocks are gone from the file, or preserved because a write failed.
Step 5. Collect past months. Offer to archive past months as notes.md sets out — daily notes from earlier months still at the root of Daily/ are listed in the report, and moved into their monthly folder only on the user's yes. Done when the list is collected, or none exist.
Step 6. Report. End with one report: the session note path when one was written and the daily note path, what the notes record in one to three sentences — what changed, on an update — and the open items: handoff blocks left in the file because they belong to other sessions, a handoff claim the session's work does not explain, a failed write, an old Obsidian folder the user did not rename, older notes updated or left with a link to the previous project name, and the past-month daily notes awaiting the archive answer, grouped by target folder. Never paste either note. Done when the report carries the note paths, the summary, and every open item, or states that none exist.
Run the six steps in one pass. The initial invocation authorizes the first four: never pause for confirmation between them, never preview the note content in chat, and report only at the end. Four exceptions: the bootstrap questions in Step 1, the warning or question about a missing project folder in Step 3, which waits for the user, the question whether to open Obsidian when the CLI finds the app closed, and the archive question in Step 5, asked once alongside the report.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/adeonir/agent-skills/wrap-up">View wrap-up on skillZs</a>