wrap
/wrap
Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save.
- Author
- egregore-labs ↗
- Repository
- egregore ↗
- Licence
- MIT
- Last repository change
- 16.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save.
Original author description
Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save.
How it works
- When to invoke
- Prepare
- Write once
- Lifecycle boundary
- Output
SKILL.md preview
---
name: wrap
description: "Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save."
---
# Personal session wrap
Record what this actor finished, what was verified, and what remains. A wrap is
personal session closure, not a handoff, notification, publication, or claim
that an organizational obligation is complete.
Canonical Markdown and Git provenance are authoritative. The Egregore Runtime
owns authorization, stable ActorContext resolution, persistence, provenance,
retrieval refresh, background embedding, and content-free telemetry through
one writeback transaction.
## When to invoke
Close the current Egregore session with a personal, canonical summary. Use for /wrap or when the user says they are done, wrapping up, or at a stopping point. Route work assigned to another person to /handoff and save-without-closing to /save.
## Prepare
1. Reuse the current conversation and relevant `EGREGORE_ORG_CONTEXT_V1`
evidence. Do not search organizational memory again merely to summarize the
session.
2. Derive a short topic, a two-to-four sentence summary, verified outcomes,
and concise open threads. Separate completed work from unverified work.
3. If the proposed summary is materially ambiguous, show it once and ask for
correction. Skip confirmation when the user already supplied exact wrap
wording.
4. If project changes need delivery, invoke `/save` once before the wrap. That
is a separate project-delivery action; do not reproduce Git commands in this
skill and do not run a second save after canonical wrap succeeds.
Use this body shape, omitting empty sections:
```markdown
## Summary
<what changed and the current state>
## Completed
- <completed outcome>
## Verification
- <test or check and its result>
## Open Threads
- [ ] <unfinished item or next step>
```
## Write once
Write this body to the file `tmp/wrap-body.md`, then pass it to
the Runtime-neutral wrap adapter in one command:
```markdown
<body markdown>
```
Use `{topic}` for the short topic and `{summary}` for the two-to-four sentence summary
derived from the session during preparation:
```bash
bash bin/agent.sh wrap \
--topic '{topic}' \
--summary '{summary}' --body-file tmp/wrap-body.md
```
Do not call `artifact-writeback.sh`, `capture-run.sh`, Git, QMD, graph,
telemetry, publication, or notification mechanics directly. The adapter enters
one personal canonical writeback transaction:
`authorize → persist Markdown → Git provenance → retrieval update → background embed → telemetry`
On success, report the returned `memory/wraps/...` path and the project save
status. If the adapter fails, show the concise error and stop; never fall back
to writing the file or updating projections directly.
## Lifecycle boundary
- A personal wrap never creates a recipient obligation; use `/handoff` for
work another person must receive or continue.
- A wrap never silently completes, expires, or supersedes a handoff, quest,
todo, or thread. Age is not completion evidence.
- The canonical wrap receipt may support a later, explicitly authorized
lifecycle transition. That lifecycle service must verify the target,
expected revision, actor membership, and typed evidence separately.
- Keep open threads in the wrap even when they are also promoted through their
own quest/todo/thread Runtime action.
## Output
The adapter renders the wrap result card — actor, topic, summary,
open-thread count, canonical path, and save/writeback status — as its
stdout. The card is already fully visible there and must appear exactly once
in the conversation. Never copy, re-render, summarize, or repeat it in your
reply; add nothing beyond an answer to something the user separately asked.
Do not claim `graphed`, `published`, `notified`, or `shared` unless a
separate explicit action actually occurred.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · egregore-labs/egregore | 100 | MIT |
| langri-sha/skills | 100 | MIT |
| clawnify/greybeard | 100 | MIT |
| egregore-labs/egregore | 100 | MIT |
| hazarsozer/ren-os | 100 | MIT |
| cdeistopened/skill-stack | 90 | MIT |
Database snapshot: 13.11.2026 · package version 419234995300 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95strata.handoff
Use when a session ends, when the task boundary is reached, before a context split or compaction, or when the user says handoff, wrap up, end session, save state. Keywords - handoff, ledger close, wrap up, end of session, pending, blocker. - 100forward
Hand off the current session to the next one. Use when user says "forward", "handoff", "wrap up", or before ending a session. - 86handoff
Close out a working session cleanly - save open questions and decisions to the role's memory file, file anything that needs building as a proposal issue, release the dispatcher lease, then tell the owner the session can be closed. Use for "/crew:handoff", "wrap up", "hand off",… - 90handoff
Write a structured session handoff so a fresh session resumes losslessly. Use when context is filling up (around half the window), when wrapping a work session, or when the user says "handoff", "checkpoint", "wrap up", or "save state". - 100kmg-session-wrap
Prompt for session summary when user indicates they are stopping work or approaching context limits - 100uninstall-watchdog
Removes the egregore watchdog daemon and its associated files. Use when stopping automated session relaunching or cleaning up egregore infrastructure.