What is the difference between snapshot and /park?

Snapshot provides an inline, review-friendly view of the current state without interrupting work, while /park saves a full checkpoint file for later resume.

How do I save a snapshot to a file?

Use the --save flag; the tool writes to snapshot-[timestamp].md in the parking location.

What does the snapshot include?

Focus, Progress (completed/in-progress/pending), Key decisions, Files touched, and Current thread.

snapshot

Scanned

npx machina-cli add skill technicalpickles/pickled-claude-plugins/snapshot --openclaw

Files (1)

SKILL.md

1.5 KB

Snapshot

Capture current session state for review without parking.

Use Cases

Session is getting long, want a checkpoint summary
Want to share progress with someone
Need to orient yourself on where you are

Output Format

━━━ Session Snapshot ━━━
Focus: [Current focus/goal]

Progress:
✓ [Completed item]
✓ [Completed item]
○ [In progress item]
○ [Pending item]

Key decisions:
- [Decision 1]
- [Decision 2]

Files touched:
- path/to/file.ts (new)
- path/to/other.ts (modified)

Current thread: [What we're actively discussing/working on]

Flags

`--save`

Write the snapshot to the parking location as a checkpoint file.

Filename: snapshot-[timestamp].md

Format when saved:

# Snapshot: [Focus]

**Captured:** [Date/time]
**Branch:** [branch-name]

## Progress
- [x] [Completed item]
- [x] [Completed item]
- [ ] [In progress item]
- [ ] [Pending item]

## Key Decisions
- [Decision 1]
- [Decision 2]

## Files Touched
- path/to/file.ts (new)
- path/to/other.ts (modified)

## Current Thread
[What we're actively discussing/working on]

Report: "Snapshot saved to [path]"

Difference from /park

Aspect	/snapshot	/park
Intent	Review progress	Stop work for later
Output	Inline (default)	Always file
Resume prompt	No	Yes
Next steps	Current state	Future direction

Source

git clone https://github.com/technicalpickles/pickled-claude-plugins/blob/main/plugins/agent-meta/skills/snapshot/SKILL.md

View on GitHub

Overview

Snapshot captures the present focus, progress, key decisions, and files touched without interrupting work. It provides a quick, shareable view of where you are in a session, aiding reviews, handoffs, and orientation.

How This Skill Works

It assembles a structured view that includes Focus, Progress, Key decisions, Files touched, and Current thread. You can review the inline output immediately, or save a checkpoint to a parking location using --save, which writes a file named snapshot-[timestamp].md.

When to Use It

When a session is getting long and you want a checkpoint summary.
When you need to share progress with a teammate or stakeholder.
When you want to orient yourself on current focus, progress, and decisions.
When preparing for a handoff or collaboration and need up-to-date context.
When you want a portable record to review later without interrupting ongoing work.

Quick Start

Step 1: Run the snapshot command to capture the current session state.
Step 2: If you want a file, run with --save to write snapshot-[timestamp].md to the parking location.
Step 3: Review the inline output or open the saved file to confirm Focus, Progress, and Key Decisions.

Best Practices

Update Focus and Current thread just before taking a snapshot for accuracy.
List completed, in-progress, and pending items in Progress for clarity.
Use the --save flag to create a persistent checkpoint file.
Verify the Files touched section reflects recent edits.
Share snapshots promptly after milestones to align stakeholders.

Example Use Cases

I captured a snapshot at the end of the sprint to share with the product owner.
Snapshot showed Focus: optimize database calls; Progress: 2 done, 1 in progress.
Saved a checkpoint with --save to park for a quick review later.
Used the Current thread to drive a team review session.
Shared a snapshot to show where we paused for handoff.

Frequently Asked Questions

Add this skill to your agents