wrap-session

Summarizes a session conversation into notes.md and stamps the close marker headlessly.

6|1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill wrap-session-t-mercier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-session
Source: https://github.com/t-mercier/ai-agents-orchestrator/tree/main/skills/wrap-session
Command: npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill wrap-session-t-mercier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a session is closed from a dashboard button rather than an interactive terminal, no human is present to answer questions, so the usual interactive close workflow cannot run. This Skill performs the unattended wrap-up: it writes the session summary into the given notes.md, refreshes PR and ticket frontmatter, and stamps the Session history entry that marks the session Closed. ## Core Features & Use Cases - Headless session summary: Distils the restored conversation into dated decisions, files touched, open questions, and a rewritten next-steps queue of at most 7 open items. - Append-only frontmatter refresh: Collects PR URLs via gh pr view and conversation scanning, plus ticket IDs and their observed statuses, without ever removing existing links. - Close marker stamping: Always appends a Session history line with the original session id, which is what moves the session to Closed in the dashboard. - Use Case: A user clicks Close on a stale session in the AI Agents Orchestrator dashboard; the app resumes the session with --print and invokes this Skill to wrap it up without any interactive prompts. ## Quick Start Run /wrap-session with the path to the session's notes.md and the original session id to close it out unattended.

Frequently Asked Questions about wrap-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I close an AI agent session without an interactive terminal?

Invoke /wrap-session with the session's notes.md path and its original session id. It summarizes the conversation, refreshes PR and ticket frontmatter, and writes the Session history close marker without asking any questions.

What arguments does the wrap-session command require?

It requires exactly two arguments: the path to an existing notes.md file and the original session id. If either is missing or the file does not exist, it prints one line and stops rather than guessing a path.

Does wrap-session update PR and ticket links automatically?

Yes, it collects PR URLs via gh pr view on the session branch and by scanning the conversation, plus ticket IDs matching a tracker pattern. All updates are append-only and never remove existing links.

Why must the session id be passed as an argument instead of detected?

Because --resume runs the conversation under a new session id, so a pid or registry lookup would find the headless wrapper process instead of the session being closed. The close marker must name the original resumable session.

What is the difference between wrap-session and close-session?

wrap-session is the headless twin of close-session, performing only the wrap-up steps: summary, frontmatter refresh, and history stamp. The knowledge-notes distillation and skill proposal remain in close-session because they require human judgement.