session-state-manager

Save conversation state to an append-only log at .claude/state/session.md.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill session-state-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-state-manager
Source: https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon/tree/main/.claude/skills/session-state-manager
Command: npx skills add https://github.com/sarimofficial/HackathonlPhase-IV-AI-Powered-Kubernetes-Deployment-Minikube-Helm-kubectl-ai-Kagent-Gordon --skill session-state-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents loss of context across sessions by automatically saving state after significant interactions, enabling seamless continuation of conversations.

Core Features & Use Cases

  • Auto-save after every user message to capture the latest instruction.
  • Log file changes, completed phases, and key decisions in an append-only store.
  • Load and resume from the last saved state with a concise summary to reestablish context.
  • Enforce a deterministic, timestamped record at .claude/state/session.md for traceability and recovery.

Quick Start

The skill runs automatically; to test, perform a chat action and then say "resume" to continue from the last saved point.

Frequently Asked Questions about session-state-manager

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

FAQPage Schema
How do I persist conversation state across chat sessions?

You can resume a chat session by loading the last saved state from the append-only log at .claude/state/session.md, which provides a concise summary to reestablish context.

How does automatic state logging work for long-running multi-step tasks?

Automatic state logging for long-running tasks enforces mandatory auto-execution after significant actions, capturing the latest instruction and appending it to a deterministic timestamped record for traceability.

What is the best way to save context automatically before a session restart?

The best way to save context before a session restart is through auto-save after every user message, which logs file changes, completed phases, and key decisions into a persistent append-only store.

Can I use an append-only log to trace key decisions in a multi-step workflow?

Yes, you can use an append-only log to trace key decisions in a multi-step workflow, as the skill enforces a deterministic, timestamped record at .claude/state/session.md for recovery and traceability.

Do I need any dependencies to automatically save and resume conversation state?

No dependencies are required to automatically save and resume conversation state, as the skill operates independently to manage session continuity through a local markdown state file.