sunset-protocol

Transfer an agent's state and memory between engines with ring safety.

Updated May 30, 2026
One-click install
npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill sunset-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sunset-protocol
Source: https://github.com/InnerScopeHearing/otchealth-claude-tools/tree/main/skills/sunset-protocol
Command: npx skills add https://github.com/InnerScopeHearing/otchealth-claude-tools --skill sunset-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures seamless and secure transfer of an agent's state and memory across different engines, maintaining continuity without data loss.

Core Features & Use Cases

  • Cross-Engine Transfer: Safely move an agent's state and memory from one engine to another.
  • Ring Safety: Ensures that sensitive information remains protected during the transfer.
  • Use Case: For example, when an agent needs to transition between different platforms without losing their work or state.

Quick Start

Run the 'Sunset Transfer Protocol' by saying "Sunset Transfer Protocol" or "spin down for transfer" to safely flush and handoff the agent's state to durable memory.

Frequently Asked Questions about sunset-protocol

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

FAQPage Schema
How do I transfer agent state and memory between different engines without data loss?

To transfer agent state and memory without data loss, use a cross-engine transfer protocol to safely flush the agent's current state to durable memory. This ensures continuity of service across different platforms while maintaining complete memory integrity during the handoff.

How does memory continuity work when switching an agent to a new platform?

Memory continuity during engine switching works by securely transferring the agent's active state to durable storage. The new engine retrieves this preserved state, allowing the agent to resume operations seamlessly without losing context or sensitive information.

How do I protect sensitive data during an agent state transfer?

Protect sensitive data during agent state transfer by utilizing ring safety protocols. This mechanism ensures that sensitive information remains encrypted and protected throughout the entire transfer process, preventing exposure while moving state data between different engines.

What is the best way to spin down an agent for a secure state handoff?

The best way to spin down an agent for a secure state handoff is to invoke a transfer protocol that safely flushes the active memory to durable storage. This action prepares the agent for a secure state transition without data loss.

Do I need specific agent roles to perform a cross-engine state transfer?

Yes, proper agent roles are required to perform a cross-engine state transfer. The protocol mandates specific roles to ensure ring safety and authorize the secure handoff of state data to durable memory during the engine switching process.