shutdown

Audit atoms, archive stale items, and build a 3×3 grid handoff.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill shutdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shutdown
Source: https://github.com/rudi193-cmd/Aionic-Claude-Skills/tree/main/skills/shutdown
Command: npx skills add https://github.com/rudi193-cmd/Aionic-Claude-Skills --skill shutdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Graceful session shutdown orchestrates audit, archiving, and drift correction to preserve state and ensure safe handoffs between the Source, Bridge, and Continuity rings.

Core Features & Use Cases

  • Audits atoms in the agent's schema to detect drift and staleness.
  • Archives superseded atoms to domain='archived' to preserve history.
  • Writes new atoms, creates edges, and builds a standardized handoff for continuity.
  • Use Case: When winding down a session, run the shutdown sequence to guarantee accountability and seamless handoff of work.

Quick Start

Trigger the three-ring shutdown sequence to audit, edge, and surface unpushed work.

Frequently Asked Questions about shutdown

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

FAQPage Schema
How do I perform a graceful session shutdown and preserve state for handoff?

Graceful session shutdown audits the agent's atoms, archives stale items, and corrects drift to ensure accurate state. It writes new atoms, creates edges, and builds a structured 3×3 grid for continuity before cleanly closing the session.

When should I run a session audit to detect drift and staleness?

Run a session audit when winding down an active session to detect drift and staleness. Archiving superseded atoms preserves history and guarantees accountability before initiating the handoff sequence.

What is the best way to archive superseded session atoms for continuity?

Archiving superseded atoms moves them to the archived domain to preserve history. This process corrects state drift and ensures accurate session handoffs across Source, Bridge, and Continuity rings.

How does a structured handoff sequence manage unpushed changes?

A structured handoff sequence surfaces unpushed changes, writes new atoms, and creates edges to establish relationships. It externalizes the handoff to the arm DB and central index for seamless continuity.

Can I use this session shutdown sequence without external dependencies?

Yes, the session shutdown sequence operates without external dependencies. It audits internal atoms, archives stale items, and builds the 3×3 handoff grid directly within the agent's schema.

Why does my session state drift during agent handoffs?

Session state drifts when active atoms become stale or superseded during runtime. The shutdown sequence corrects this drift by auditing the schema, archiving outdated items, and externalizing the accurate state.