How do I install the Save Session skill?

Run npx skillmds@latest add vasuag09/save-session in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Save Session skill do?

Summarize current progress and persist it to a dated session file so work resumes cleanly in a future session. Use before /compact, before ending a session, or at major milestones. Pairs with /resume-session. It is listed under Research & Search on SkillMD.

Is Save Session safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Save Session?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Save Session free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Save Session?

vasuag09 (@vasuag09) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Save Session by vasuag09 — Agent Skill

Name: Save Session
Author: vasuag09

File contents

/save-session — persist progress

Goal: a future session (or a fresh context) can pick up exactly where this left off.

File location

Inside a git repo: .claude/sessions/<YYYY-MM-DD>.md (append across the day).
Otherwise: ~/.claude/harness-claude/sessions/<YYYY-MM-DD>.md.

Create the directory if needed. Append to today's file; don't pollute it with old work — start a new dated file per day.

What to write (evidence-based, not aspirational)

# Session <date> — <project/feature>
## Goal / current objective
## What works (verified, with evidence: test names, commands, screenshots)
## What was tried and did NOT work (so we don't repeat it)
## Not yet attempted / remaining (the next concrete steps)
## Key decisions & files touched
## Open questions / blockers

How

Summarize honestly: distinguish verified from assumed.
Append (don't overwrite) under a timestamped subheading.
Tell the user the file path so they can review/edit it.

This skill is also invoked automatically by the PreCompact and Stop hooks — keep the format stable so those writes stay consistent.

Frequently asked questions

Save Session