aget-save-state

Save workflow state as YAML checkpoints under sessions/checkpoints.

2|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/aget-framework/template-advisor-aget --skill aget-save-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-save-state
Source: https://github.com/aget-framework/template-advisor-aget/tree/main/.claude/skills/aget-save-state
Command: npx skills add https://github.com/aget-framework/template-advisor-aget --skill aget-save-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill saves workflow state to enable resume and recovery across sessions.

Core Features & Use Cases

  • Auto-name and timestamp checkpoints for session continuity.
  • Store a structured YAML checkpoint under sessions/checkpoints containing context, active tasks, and artifacts.
  • Retrieve and resume from the latest or a named checkpoint to minimize context loss.

Quick Start

Save a checkpoint at a natural break in your workflow to enable seamless resume later.

Frequently Asked Questions about aget-save-state

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

FAQPage Schema
How do I save and resume workflow state across sessions?

YAML checkpoints save workflow state by storing context, active tasks, and artifacts under sessions/checkpoints. You can retrieve and resume from the latest auto-timestamped checkpoint or a user-named checkpoint to minimize context loss.

What is the best way to checkpoint a workflow for recovery later?

Checkpointing a workflow involves writing context, active tasks, and artifacts to a YAML file under sessions/checkpoints. Save at natural workflow breaks to enable seamless resume and minimize context loss across sessions.

Can I use a custom name instead of an auto-timestamp when saving a checkpoint?

Yes, saving workflow checkpoints supports both auto-named timestamps and user-provided names. You can specify a custom checkpoint name to easily identify and retrieve that specific saved state during session resume.

Are there safety constraints for saving sensitive data in workflow checkpoints?

Yes, writing workflow checkpoints enforces safety constraints to avoid restricted paths and prevent sensitive data exposure. This ensures saved YAML state files remain secure and do not leak sensitive session context.

How do I retrieve the latest checkpoint to resume a previous session?

To retrieve and resume from the latest checkpoint, load the most recent YAML state file saved under sessions/checkpoints. This restores context, active tasks, and artifacts to minimize context loss during session resume.