checkpoint

Save and resume Claude conversation context across Hapi sessions.

9|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/mkSteady/mkSkills --skill checkpoint-mksteady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/mkSteady/mkSkills/tree/main/checkpoint
Command: npx skills add https://github.com/mkSteady/mkSkills --skill checkpoint-mksteady

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill saves and resumes work context across Claude sessions, enabling thread-level continuity with Hapi integration.

Core Features & Use Cases

  • Thread-scoped continuity across multiple Claude sessions
  • Environment-aware operation (local vs Hapi) and delayed archiving
  • Deterministic checkpointing and optional history archiving

Quick Start

Enable checkpoint for the current task and then save to create a resumable checkpoint.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I preserve Claude context across multiple sessions?▼

You preserve context by creating a checkpoint that saves the current session state into a thread schema, enabling deterministic resumption of your Claude conversation workflow later.

What is the best way to save and resume Claude conversation history?▼

Saving and resuming conversation history involves writing the current context to a thread file, allowing you to archive previous sessions and reload the exact state when needed.

Does Hapi session management support cross-session memory continuity?▼

Yes, Hapi session management supports cross-session memory by integrating with checkpoint systems to coordinate thread-level continuity and delayed history archiving across local and Hapi environments.

How do I archive Claude thread history before starting a new session?▼

You archive thread history by triggering an explicit user action for archival, which moves the current context into an archive before deterministically handling the steps to create a new session.

Why does my checkpoint require explicit user action for archiving?▼

Checkpoints require explicit user action for archiving to prevent unintended data loss, ensuring deterministic step handling and strict adherence to the thread schema when managing session transitions.