Synthesizes session progress, saves notes, and creates a wrap-up report for Egregore sessions.
Install
mkdir -p .claude/skills/wrap-egregore-labs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17491" && unzip -o skill.zip -d .claude/skills/wrap-egregore-labs && rm skill.zipInstalls to .claude/skills/wrap-egregore-labs
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.
Wrap an Egregore session when the user invokes /wrap or $wrap, or says they are done, wrapping up, or at a stopping point in Codex.Key capabilities
- →Synthesize a topic, summary, and open notes
- →Confirm session state if ambiguous
- →Resolve the author from state or git config
- →Write notes to a temporary markdown file
- →Run agent.sh wrap command
How it works
The skill synthesizes a summary and notes from the session, confirms state if needed, resolves the author, writes notes to a file, and executes the wrap command, optionally saving code changes.
Inputs & outputs
When to use wrap
- →End session
- →Wrap up project work
- →Save session summary
About this skill
Egregore Wrap
Native Codex Egregore skill. Use this inside an Egregore checkout with
bin/agent.sh.
Flow
- Synthesize a topic, a one to three sentence summary, and concise open notes from the current session.
- If the session has ambiguous or potentially misleading state, confirm with
the user. Use structured Codex question tooling when available; otherwise
show numbered choices plus
Other:and wait. - Resolve the author from
.egregore-state.jsongithub_username, thenname, then git config. - Write the notes to a temp markdown file.
- Run:
bin/agent.sh wrap --from "$AUTHOR" --topic "$TOPIC" --summary "$SUMMARY" --body-file "$BODY_FILE"
- If
git status --porcelainreports repo changes after the wrap, run:
bin/agent.sh save --message "Wrap: $TOPIC" --topic "$TOPIC"
- Report the
memory/wraps/...path and whether code changes were saved.
Output
Structured UX parity is required. Finish with the standard Egregore wrap confirmation TUI, not a prose-only summary:
- Use a 72-column outer box with only the four standard line patterns: top rule, separator rule, content line, bottom rule.
- Header:
WRAP, author, and date. - Body: topic, one compact summary, open threads or "No open threads", and
the
memory/wraps/...path. - Footer: saved/pushed status. If code changes were saved, show that. If the wrap only touched memory, say so.
- Output the box directly, preferably in a
textfenced block, with no narration before it.
Rules
- Do not use Claude Code commands.
- Do not invent finished work. Separate completed work, verification, and open follow-ups.
- If save fails, report the failure and leave the local commits untouched.
When not to use it
- →When the user wants to invent finished work
- →When the user wants to leave local commits untouched after save failure
Limitations
- →Do not use Claude Code commands
- →Do not invent finished work
- →If save fails, report the failure and leave the local commits untouched
How it compares
This skill provides a structured, user-facing wrap-up confirmation with specific output formatting, unlike a simple prose summary of the session.
Compared to similar skills
wrap side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| wrap (this skill) | 0 | 1mo | Review | Beginner |
| notion-meeting-intelligence | 6 | 5mo | No flags | Intermediate |
| resume-handoff | 3 | 6mo | No flags | Intermediate |
| meeting-briefing | 2 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by egregore-labs
View all by egregore-labs →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.
resume-handoff
parcadei
Resume work from handoff document with context analysis and validation
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.
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.
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.
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.