Save session context

VerifiedSafe

Updates task tracking (tk) and AI documentation files (ai/) to persist session state. Logs findings, marks tasks complete, creates new tasks, then updates status, design, decisions, and sprint files. Helps capture progress before context switches or session end.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#session-management#context-save#task-tracking#ai-files

Recommended for

Automated summary

Persists session state by updating ai/ files and tk tasks, then committing changes.

Strengths

  • Automates context persistence between sessions
  • Manages tasks with tk (add, complete, log)
  • Keeps documentation files (STATUS, DESIGN, etc.) tidy
  • Includes a structured git commit

Limitations

  • Depends on the tk tool for task management
  • Assumes an existing git repository
  • Can be overkill if little has changed in the session
When to use it

At the end of a session, before switching context, or explicitly to snapshot current state.

When not to use it

When the project does not use tk or have a git repo, or you do not want to record state.

Security analysis

Safe
Quality score88/100

The skill uses bash and git commands for legitimate context-saving purposes, with no destructive or exfiltrating actions.

No concerns found

How this analysis is made

Examples

Save session state
Save the current context to ai/ files and update tk tasks, then commit.
Save before compacting
Before compacting the conversation, run the save skill to persist what we've done.

name: save description: Update ai/ files and tk tasks. allowed-tools: Read, Write, Edit, Glob, Grep, Bash

Context Save

Persist session state to ai/ and tk. Priority: tk and ai/ first (from context), git last.

Trigger: Before /compact, session end, context switch, or explicitly.

1. Update tk Tasks

tk ls

For each task:

  • Log findings first: tk log <id> "what was learned" — errors, root cause, file paths
  • Mark complete: tk done <id>
  • Add new: tk add "title" -d "context"

Don't leave stale tasks.

2. Update ai/

STATUS.md (always): Current focus, blockers, what worked. Prune stale content.

DESIGN.md (if architecture changed): Components, patterns, interfaces.

DECISIONS.md (if decisions made): Context → Decision → Rationale.

SPRINTS.md (if sprint progress): Mark completed, update status.

Keep files <500 lines. Move details to subdirs if needed.

3. Commit

git add ai/ .tasks/
git commit -m "Update session context"

4. Report

## Saved

Tasks: [N done, N added, N pending]
ai/: [what changed]

## Next Session

[2-4 bullets: what to do next based on pending tasks, blockers, incomplete work]

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-session-context-mm5t8arg/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-session-context-mm5t8arg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/save-session-context-mm5t8arg/download' --output '.skill-downloads/save-session-context-mm5t8arg/SKILL.md.part' && mv '.skill-downloads/save-session-context-mm5t8arg/SKILL.md.part' '.skill-downloads/save-session-context-mm5t8arg/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.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep, Bash

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-session-context-mm5t8arg/SKILL.md' && test -s '.skill-downloads/save-session-context-mm5t8arg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/save' && cp -R '.skill-downloads/save-session-context-mm5t8arg' '.claude/skills/save'

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-session-context-mm5t8arg'

openskills read 'save-session-context-mm5t8arg'

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-session-context-mm5t8arg/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