Memory

Close Loop

Wrap up a session with gated shipping, memory consolidation, improvements, and structured outputs.

What it does

Close an agent session through an ordered workflow covering execution gates, ship state, memory consolidation, improvements, and a publish queue. It runs when users ask to wrap up or invoke `/wrap-up`, then returns one consolidated inline report with a human-readable artifact and a machine-readable JSON block.

When to use it

  • Wrapping up an agent session
  • Closing out a completed task
  • Consolidating memory before ending work
  • Preparing end-of-session publish outputs

The skill document

Close Loop

Use this skill when the user says "wrap up", "close session", "end session", "close out this task", or invokes /wrap-up.

Run four phases in order and return one consolidated inline report.

Modular structure

This skill is split into components for maintainability:

  1. components/01-design-principles.md
  2. components/02-phase-1-ship-state.md
  3. components/03-phase-2-memory.md
  4. components/04-phase-3-4-and-output.md

Follow these components in order.

Quick run order

  1. Apply execution policy and action gates (01-design-principles.md)
  2. Execute Ship State (02-phase-1-ship-state.md)
  3. Consolidate Memory (03-phase-2-memory.md)
  4. Run improvements + publish queue + output contract (04-phase-3-4-and-output.md)

Required output

Return:

  • Artifact A: human-readable report sections exactly as defined in component 04
  • Artifact B: machine-readable JSON block exactly as defined in component 04

Resources

  • references/memory-frameworks.md
  • assets/templates/wrap-report-template.md

Questions people ask

When does the workflow run?
Use it when the user says “wrap up,” “close session,” “end session,” “close out this task,” or invokes `/wrap-up`.
What sequence does it follow?
It applies execution policy and action gates, executes Ship State, consolidates Memory, then runs improvements, the publish queue, and the output contract—in that order.
What output does it return?
It returns one consolidated inline report containing a human-readable report and a machine-readable JSON block, both following the definitions in component 04.

Related skills

Organize, verify, archive, and erase authorized project memory while keeping registry truth under owner control.

116 installs2 stars

Turn complex change requests into confirmed requirements, technical design, and traceable implementation tasks.

50 installs

Add persistent local memory with trust-aware recall and enforcement against injection, leaks, and poisoning.

97 installs2 stars

Turns mobile product, revenue, crash, acquisition, store, and repo signals into actionable proposal drafts.

90 installs

Reduce OpenClaw token waste with lazy context, model routing, heartbeat planning, and local budget checks.

459 installs30 stars

Guide safe installation, operation, auditing, and extension of the read-only OpenClaw operations dashboard.

174 installs9 stars