save-context

Save session context to CLAUDE.local.md after meaningful exchanges.

1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/eci-global/80HD --skill save-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-context
Source: https://github.com/eci-global/80HD/tree/main/.claude/skills/save-context
Command: npx skills add https://github.com/eci-global/80HD --skill save-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures continuity across CLAUDE sessions by automatically saving session context to CLAUDE.local.md after meaningful exchanges and when explicitly requested.

Core Features & Use Cases

  • Incremental saving: automatically records decisions, insights, and architectural directions after meaningful exchanges.
  • On-demand saving: trigger saves with natural language commands like 'save context', 'save progress', 'dump context', 'wrap up', or 'hand off'.
  • Handoff readiness: updates Last Session, Active Threads, and Key Insights, and creates context files as needed to support seamless handoffs in future sessions.

Quick Start

  • During a Claude session, allow automatic saves after meaningful exchanges to CLAUDE.local.md.
  • Use the trigger phrases 'save context', 'save progress', 'dump context', 'wrap up', or 'hand off' to manually save.
  • After saving, review CLAUDE.local.md to confirm Last Session, Active Threads, and Key Insights are up to date.

Frequently Asked Questions about save-context

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

FAQPage Schema
How do I save session context for a seamless handoff to a future Claude session?

To save session context for a seamless handoff, use natural language triggers like 'save context', 'wrap up', or 'hand off'. The skill then automatically updates CLAUDE.local.md with Last Session, Active Threads, and Key Insights.

Does session context save automatically during meaningful exchanges?

Yes, session context saves automatically to CLAUDE.local.md after meaningful exchanges. The skill triggers when a decision, insight, architectural direction, or significant finding emerges during your workflow.

What is the best way to dump progress before closing a session?

The best way to dump progress is to invoke the skill on demand using phrases like 'dump context' or 'save progress'. This action updates your context files and ensures continuity for future handoffs.

How do I record architectural directions and key insights incrementally?

You record architectural directions and key insights incrementally by allowing the skill to automatically save session context to CLAUDE.local.md after each meaningful exchange, preserving continuity without manual intervention.

Can I manually update Active Threads and Last Session details on demand?

Yes, you can manually update Active Threads and Last Session details by triggering the skill with commands like 'save context' or 'hand off', which immediately writes the current state to CLAUDE.local.md.