save-exit

VerifiedCaution

Save session context to documentation and track in open projects list.

Sby Skills Guide Bot
ProductivityBeginner
7/25/2026
Claude Code
#session-context#handoff#project-tracking#markdown#documentation

Recommended for

Automated summary

Saves work-session context to a dated markdown file under docs/ and records the project and session in ~/dev2/openprojects.md.

Strengths

  • Produces a structured handoff document (summary, modified files, current state, next steps, blockers) that is easy to pick up later
  • Automatically updates both the open-projects table and the recent-sessions log in a single tracking file
  • Detects the project root and name from CLAUDE.md, package.json, or .git, and creates the docs/ folder when missing
  • Accepts a user-supplied summary, otherwise drafts one from the conversation context

Limitations

  • The ~/dev2/openprojects.md path is hardcoded and must exist or be adapted to your directory layout
  • Modified files and next steps are model-generated and may be incomplete or inaccurate without review
  • One context file per date, so multiple sessions on the same day overwrite the earlier document
When to use it

Use it at the end of a work session to leave a clear resumption trail and register the project in your in-progress projects list.

When not to use it

Skip it if you don't maintain a global tracking file or prefer to capture context in git, an issue tracker, or a project management tool.

Security analysis

Caution
Quality score88/100

The skill is intended for legitimate session documentation and project tracking, with no destructive, exfiltration, or obfuscated behavior. However, it uses Write and Bash and modifies a file outside the project directory, so it warrants caution rather than a fully safe rating.

Findings
  • •Writes outside the project to ~/dev2/openprojects.md, which may modify a shared user-level tracking file.
  • •Declares Bash in allowed-tools but does not show concrete command guardrails; execution behavior depends on agent interpretation.
  • •May overwrite or duplicate session entries if run multiple times on the same date or if table formatting is not preserved.
How this analysis is made

Examples

Fin de session simple
/save-exit
Avec résumé personnalisé
/save-exit Refonte du module d'authentification : migration vers JWT terminée, tests d'intégration à écrire
Reprise après revue de code
/save-exit Revue de code complète et réorganisation de la documentation, roadmap mise à jour pour le lancement MVP

name: save-exit description: Save session context to a markdown document and register the project in openprojects.md. Use when ending a work session to capture context for future resumption. Creates a context file in the project's docs/ folder and adds/updates the project entry in ~/dev2/openprojects.md. allowed-tools:

  • Read
  • Write
  • Bash
  • Glob

save-exit

Save session context to documentation and track in open projects list.

Usage

/save-exit [optional summary]

What it does

  1. Writes session context to SESSION_CONTEXT_<date>.md in the project's docs/ directory (creates if needed)
  2. Updates ~/dev2/openprojects.md:
    • Adds/updates project in the "Open Projects" table if not present
    • Appends session entry to "Recent Sessions" log
  3. Shows summary of what was saved

Instructions

<command-name>save-exit</command-name>

When this command is invoked:

Step 1: Determine project info

  • Project root: Current working directory or nearest dir with CLAUDE.md, package.json, or .git
  • Project name: From CLAUDE.md title, package.json name, or directory name
  • Summary: User-provided argument OR generate from conversation context

Step 2: Write session context document

Create <project-root>/docs/SESSION_CONTEXT_<YYYY-MM-DD>.md with:

# Session Context - <YYYY-MM-DD>

**Project:** <project-name>
**Path:** <project-path>

## Summary

<1-2 paragraph summary of work done>

## Files Modified

- `path/to/file1.ts` - description
- `path/to/file2.md` - description

## Current State

<bullet points of where things stand>

## Next Steps

- [ ] Task 1
- [ ] Task 2

## Open Questions / Blockers

<any decisions needed or blockers>

Step 3: Update ~/dev2/openprojects.md

The file has two sections:

Section 1: Open Projects table (add project if not present)

| Project | Path | Description |
|---------|------|-------------|
| <name> | `<path>` | <description> |

Section 2: Recent Sessions log (append new entry at top)

## Recent Sessions

| Date | Project | Summary |
|------|---------|---------|
| 2026-02-01 | Story Magic | Code review completed, 9 docs written |

Step 4: Report to user

✓ Session saved:
  - Context: docs/SESSION_CONTEXT_2026-02-01.md
  - Project: Added to ~/dev2/openprojects.md
  - Session: Logged to Recent Sessions

Summary: <summary>

Example

User runs: /save-exit

Output:

✓ Session saved:
  - Context: docs/SESSION_CONTEXT_2026-02-01.md
  - Project: Story Magic (already in open projects)
  - Session: Logged to Recent Sessions

Summary: Comprehensive code review and documentation reorganization - 9 review documents written, master docs synced, roadmap updated for MVP 1.0 launch

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/save-exit-mrzxuq6s/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/save-exit-mrzxuq6s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/save-exit-mrzxuq6s/download' --output '.skill-downloads/save-exit-mrzxuq6s/SKILL.md.part' && mv '.skill-downloads/save-exit-mrzxuq6s/SKILL.md.part' '.skill-downloads/save-exit-mrzxuq6s/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/save-exit-mrzxuq6s/SKILL.md' && test -s '.skill-downloads/save-exit-mrzxuq6s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/save-exit' && cp -R '.skill-downloads/save-exit-mrzxuq6s' '.claude/skills/save-exit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/save-exit-mrzxuq6s'

openskills read 'save-exit-mrzxuq6s'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/save-exit-mrzxuq6s/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills