Session wrap-ups
Use the built-in wrap-up skill to end a session with a short summary for people. To pass a task to the next agent instead, use a session handoff.
Enable the skill
Add this to agnostic-ai.yaml, then run agnostic-ai sync:
requires: ">=0.94.0"
builtins: [wrap-up]
It is off unless you list it. For every project, add the same lines to ~/.agnostic-ai/agnostic-ai.yaml and run agnostic-ai sync --global.
Most tools get a skill; tools set to emit-skills-as-commands also get a command. Aider gets the text inline when outputs.aider.rules-file is set. Jules has no skill support.
Ask for a wrap-up
Say "wrap up" or "write a wrap-up". The reply has three parts, in this order:
## What changed
- Added a retry to the payment webhook (commits a1b2c3d, e4f5a6b).
## Still open
- The webhook tests are not run on Windows yet; no runner is set up.
## Note to share
```
The payment webhook now retries twice before it fails.
Windows tests are still missing.
```
An empty part says "nothing" on one line. The whole reply fits on one screen.
What it reads and what it never does
- It reads the session and local Git: the current branch,
git status, andgit log. - It makes no network call. It names a PR only when the session already showed one.
- The note has no secrets, no absolute home paths, and no text copied from files the session only read.
- It does not post, commit, push, or write a file unless you ask.
- It never runs by itself, at the start or at the end of a session.
Wrap-up or handoff
| Skill | For | Result | When |
|---|---|---|---|
handoff | The next agent | A private note per branch | Mid-task, to continue elsewhere |
wrap-up | People | A reply in the conversation | When the work ends |
See where it comes from
agnostic-ai list
agnostic-ai explain builtin:wrap-up
agnostic-ai why .claude/skills/wrap-up/SKILL.md
To replace the built-in, create your own project skill named wrap-up; it wins over the built-in.