scratch

Store ephemeral context in a dedicated scratch file across sessions.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/multicam/ikigai-rev --skill scratch-multicam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scratch
Source: https://github.com/multicam/ikigai-rev/tree/main/.claude-i/library/scratch
Command: npx skills add https://github.com/multicam/ikigai-rev --skill scratch-multicam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Carry ephemeral context across sessions by saving information to a dedicated scratch file that survives restarts.

Core Features & Use Cases

  • Persist notes, decisions, and interim state between sessions
  • Overwrite the scratch file deterministically to avoid accumulating stale data
  • Use cases include resume prompts, handoffs, and quick temporary memory

Quick Start

Write a new note to scratch to replace the current content.

Frequently Asked Questions about scratch

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

FAQPage Schema
How do I carry context across sessions without losing temporary notes?

To carry context across sessions, store ephemeral notes, decisions, and interim state in a dedicated scratch file that survives restarts. Writing to this file replaces the current content, preserving information deterministically.

What is the best way to persist interim state between work sessions?

Persisting interim state between sessions is done by saving prompts and decisions to a scratch file. This mechanism uses deterministic overwrite behavior to replace content, preventing the accumulation of stale data over time.

How does deterministic overwrite behavior work for session memory?

Deterministic overwrite behavior replaces the entire content of the scratch file with the new note. This ensures your session memory reflects only the latest context, avoiding conflicts or bloated files from accumulated past entries.

Can I use a scratch file for resume prompts and quick handoffs?

A scratch file is suitable for resume prompts and quick handoffs. It stores ephemeral context like decisions and state, requiring only the scratch mechanism and a write command to replace content for the next session.

Why does my session memory overwrite previous notes instead of appending?

Session memory overwrites previous notes to avoid accumulating stale data. The mechanism replaces content deterministically rather than appending, ensuring only current, relevant context survives restarts for your next session.

Do I need any dependencies to preserve context across restarts?

No dependencies are required to preserve context across restarts. The mechanism needs only a dedicated scratch file and a write command that replaces content, keeping the setup basic and dependency-free.