dump

Close a work session and emit a structured handover artifact.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nicsuzor/aops --skill dump-nicsuzor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dump
Source: https://github.com/nicsuzor/aops/tree/main/aops-claude/skills/end_session
Command: npx skills add https://github.com/nicsuzor/aops --skill dump-nicsuzor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close a work session cleanly and reliably, producing a consistent handover artifact that preserves critical context for the next responder.

Core Features & Use Cases

  • Short-form: Interactive handoffs for ongoing work, delivering a concise next-step update and preserving the session_id.
  • Full-form: End-of-day or emergency closures that commit session outputs, push changes, and generate a release payload for PKB tracking.
  • Automated handover: Ensures the bound task carries the session_id and captures the latest delta or release payload for downstream tasks.

Quick Start

Initiate end_session to perform a structured handover and update the bound task with the latest session delta.

Frequently Asked Questions about dump

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

FAQPage Schema
How do I close a work session cleanly and generate a structured handover?

To close a work session cleanly and generate a structured handover, initiate the end_session process. It finalizes your bound task using update_task and release_task with a session_id, producing a consistent handover artifact that preserves critical context for the next responder.

What is the difference between a short-form interactive handoff and a full-form session closure?

A short-form interactive handoff delivers a concise next-step update for ongoing work while preserving the session_id. A full-form session closure handles end-of-day or emergency exits by committing session outputs, pushing changes, and generating a release payload for PKB tracking.

When should I use an emergency session closure for task handover?

You should use an emergency session closure when an unexpected condition exists that halts your work. This full-form closure path commits whatever session outputs are available, pushes changes, and generates a release payload to ensure the bound task captures the latest state for downstream tasks.

Do I need a bound task to perform an end-of-day session handover?

Yes, a bound task is required to perform an end-of-day session handover. The handover process relies on the bound task to attach the session_id, capture the latest delta, and execute the update_task and release_task actions needed to finalize the structured release payload.