gaia-resume

Resume interrupted GAIA workflows from persisted checkpoint state.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-resume
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-resume
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-resume
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-resume

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resume interrupted GAIA workflows by selecting a live checkpoint, validating integrity, and guiding the user to either resume, start over, or review as needed.

Core Features & Use Cases

  • List active checkpoints under _memory/checkpoints/ and exclude those in completed/.
  • Read and load the checkpoint state via checkpoint.sh read, then verify file integrity with checkpoint.sh validate.
  • When drift or missing files are detected, present a Choice: Proceed / Start fresh / Review to determine the recovery action.

Quick Start

Tell GAIA to resume a paused workflow by typing /gaia-resume after context loss.

Frequently Asked Questions about gaia-resume

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

FAQPage Schema
How do I resume an interrupted workflow from a checkpoint?

To resume an interrupted workflow, the system lists active checkpoints under _memory/checkpoints/, reads the selected state, and validates file integrity to determine the next recovery steps. It uses checkpoint.sh read and validate to ensure the saved state is intact before proceeding.

What happens when checkpoint validation detects drift or missing files?

When checkpoint validation detects drift or missing files, it prompts the user with a choice to proceed, start fresh, or review the state. This deterministic handling ensures you can safely decide how to recover the interrupted workflow without losing data.

How does checkpoint state validation work for paused workflows?

Checkpoint state validation works by reading the persisted state with checkpoint.sh read and verifying its integrity with checkpoint.sh validate. It checks active checkpoints while excluding completed ones, ensuring only viable resume points are considered for continuing the workflow.

Can I recover a workflow if the checkpoint files are missing?

Recovering a workflow with missing checkpoint files triggers a user prompt offering the choice to proceed, start fresh, or review. The system excludes completed checkpoints and only operates on active ones under _memory/checkpoints/ to guide the recovery action safely.

When should I start fresh instead of resuming from a checkpoint?

You should start fresh instead of resuming when checkpoint validation detects drift or missing files that compromise integrity. The system presents this choice alongside proceeding or reviewing, allowing you to bypass corrupted states and safely restart the workflow from the beginning.