checkpoint

Save session decisions, progress, and pending items to an Obsidian vault note.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/fascari/ai-config --skill checkpoint-fascari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint
Source: https://github.com/fascari/ai-config/tree/main/skills/checkpoint
Command: npx skills add https://github.com/fascari/ai-config --skill checkpoint-fascari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checkpointing sessions by saving decisions, progress, and pending items to a persistent vault so you can resume exactly where you left off.

Core Features & Use Cases

  • Save decisions, progress, and pending items to a structured vault note per session for quick recall.
  • Read-only behavior for loading context, with write operations limited to appending new notes to avoid overwriting existing data.
  • Use Case: After a milestone or long-running task, checkpointing lets you continue with full context in the next session.

Quick Start

Instruct the AI to checkpoint the session by saving decisions, progress, and pending items to the Obsidian vault.

Frequently Asked Questions about checkpoint

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

FAQPage Schema
How do I save session progress to Obsidian for continuity across conversations?

To save session progress to Obsidian, instruct the AI to checkpoint by saving decisions, progress, and pending items to a structured vault note for quick recall and continuity across conversations.

Can I resume an Obsidian vault session exactly where I left off after closing it?

You can resume an Obsidian vault session exactly where you left off by checkpointing at a milestone, which preserves decisions and pending items for the next session to pick up.

Does the Obsidian checkpoint require any specific vault configuration?

The Obsidian checkpoint requires COPILOT_VAULT to be configured beforehand, ensuring session output saves correctly to the vault using write-only semantics to preserve data integrity.

When should I use a session checkpoint in my Obsidian vault?

Use a session checkpoint in your Obsidian vault at the end of a session or after reaching a milestone in a long-running task to preserve decisions, progress, and pending items.

Will checkpointing my session overwrite existing notes in my Obsidian vault?

Checkpointing your session will not overwrite existing notes in your Obsidian vault because it uses write-only semantics limited to appending new notes, ensuring data integrity.

How does the vault checkpoint load context without overwriting my session data?

The vault checkpoint loads context using read-only behavior for retrieval while restricting write operations to appending new notes, which prevents overwriting existing session data.