Finalizes the session by updating local memory, reconciling todos, and cleaning up work plans.

Install

mkdir -p .claude/skills/prep && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17496" && unzip -o skill.zip -d .claude/skills/prep && rm skill.zip

Installs to .claude/skills/prep

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Session wrap-up. Update memories, check plans, review git state, check inbox, flag loose ends. Use before closing a session or compacting context.
146 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Update session entry with work summary and key learnings
  • Add collaboration insights to observations
  • Reconcile open todos against actual system state
  • Update execution logs and status of active plans
  • Report uncommitted git changes and open PRs

How it works

The skill reads passport.json, updates local.json with session summary and key learnings, adds observations, reconciles todos, updates active plans, checks git state, and reports inbox status and loose ends.

Inputs & outputs

You give it
User's request to wrap up a session or compact context
You get back
A confirmation list of all updated memories, plans, git state, inbox, and loose ends

When to use prep

  • Prep for next session
  • Update project memory
  • Reconcile todos

About this skill

Session Wrap-Up

Purpose: Button up everything at the end of a session — or before a /compact. Memories, plans, git — all tidy.

Execution

  1. Read .trinity/passport.json first — re-absorb your identity before writing anything
  2. Do ALL of the following, then confirm what was updated

1. Memories

  • .trinity/local.json — Add/update session entry with summary of work done. Add new key_learnings for anything learned this session.
  • .trinity/observations.json — Add collaboration insights if anything notable happened. Skip if nothing new.
  • .trinity/passport.json — Only update if role/purpose/principles genuinely changed this session.

Entry shape — one rule for all four types: key_learnings, sessions, todos (local.json) and observations (observations.json) are all lists, newest at top (index 0). Every entry carries a number (monotonic int per type — highest = newest, never reused; new = current max + 1) and a date (ISO), plus its text field + extras: key_learnings {number, date, key, value} · sessions {number, date, summary, status, tags} · todos {number, date, task, priority, status} · observations {number, date, note, tags}. Stamp number + date and prepend; don't hand-trim sessions/key_learnings/observations — rollover archives the oldest by number automatically. Todos are the exception — rollover never touches them, so you prune done ones by hand (see Reconcile).

Reconcile todos — verify against reality, don't trust the label. Stored status drifts (a todo finished a past session often never got closed). Audit every open todo against the actual system: file/dir still there? code path in or out? README says what it claims? audit passes? Close what's verifiably done → note it in the session entry, then DELETE the todo from the array (rollover never trims todos — they're operational — so done items left as status: done pile up and go stale across chats), re-scope partials, leave deferred/pending-decision ones open. Fail honestly — remove only on evidence, never to tidy the list. Use ls/find/git ls-files/grep/drone @seedgo audit, not assumptions.

2. Active Plans

  • Check any DPLANs or FPLANs referenced in this session
  • Update their execution logs, status, decision logs with current state
  • If a plan was completed, note it (but don't close — the user does that)

3. Git State

  • Run git status — report uncommitted changes
  • If there's a logical commit waiting, suggest it (don't commit without asking)
  • Note the current branch and any open PRs

4. Inbox

  • Run drone @ai_mail inbox 2>/dev/null — report any unread emails
  • Close any that were already processed but not formally closed

5. Loose Ends

  • Flag anything in-flight: running background agents, dispatched branches waiting for replies, pending decisions
  • If anything can't survive compaction, write it to local.json todos[]

Confirm

List everything updated. Format:

Prep complete:
- local.json: [what was added]
- Todos: [reconciled vs reality — N done & removed, M re-scoped, K still open]
- observations.json: [updated / skipped]
- Plans: [which ones updated]
- Git: [branch, uncommitted count, suggestion]
- Inbox: [count, action taken]
- Loose ends: [any flagged]

Ready to close out or compact.

When not to use it

  • When the user wants to hand-trim sessions, key_learnings, or observations
  • When the user wants to close a plan (user does that)
  • When the user wants to commit without asking

Limitations

  • Does not hand-trim sessions/key_learnings/observations
  • Does not close plans (user does that)
  • Does not commit without asking

How it compares

This skill performs a complete, structured wrap-up of all session artifacts, ensuring memory consistency and project readiness, unlike a simple save or commit.

Compared to similar skills

prep side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
prep (this skill)01moNo flagsIntermediate
notion-meeting-intelligence65moNo flagsIntermediate
resume-handoff36moNo flagsIntermediate
meeting-briefing25moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

notion-meeting-intelligence

openai

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

656

resume-handoff

parcadei

Resume work from handoff document with context analysis and validation

333

meeting-briefing

anthropics

Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.

213

personal-assistant

ailabs-393

This skill should be used whenever users request personal assistance tasks such as schedule management, task tracking, reminder setting, habit monitoring, productivity advice, time management, or any query requiring personalized responses based on user preferences and context. On first use, collects comprehensive user information including schedule, working habits, preferences, goals, and routines. Maintains an intelligent database that automatically organizes and prioritizes information, keeping relevant data and discarding outdated context.

36

digital-brain

muratcankoylan

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

15

meeting-sync

amanaiproduct

Sync new Granola meetings to local Knowledge folder. Use during morning planning, when user asks "what should I do today", or asks to review/sync meetings.

13

Search skills

Search the agent skills registry