save-session skill
✓ VerifiedCreates a dated recap of an agent session in Obsidian format, documenting outcomes, decisions, changed files, and deferred work.
- GitHub stars
- 16
- Files
- 1
- Last commit
- Oct 28, 2026
- License
- MIT
- Allowed tools
- —
What does the save-session skill do?
save-session creates a dated recap of an agent session in Obsidian format, documenting outcomes, decisions, changed files, and deferred work.
Summary generated from the skill's SKILL.md.
About the save-session skill
Developers who need to document agentic workflows can use this tool to generate dated Obsidian-formatted recaps of their work sessions. It creates a structured record that captures outcomes, specific decisions, code examples, modified files, and any tasks that were deferred for later. An agent should load this skill at the end of a task to ensure that the reasoning and results are preserved for future reference or human review.
The process relies on reviewing the conversation history, tool results, and files like AGENTS.md to build an evidence-based summary. It produces a markdown file within a schema-defined session directory, ensuring that no existing notes are overwritten without permission. Unlike general note-taking, this focuses on session-specific evidence and separates completed actions from unfinished work, providing a clear trail of what was actually achieved during the interaction.
What an agent can do with it
- 1Documenting completed coding tasksAsk the agent to record all file changes and decisions made during a refactoring session.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the save-session skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the save-session skill in Claude Code
~/.claude/skills/save-session/SKILL.md
$ npx degit kriscard/Skills/skills/obsidian/save-session ~/.claude/skills/save-sessionInstall the save-session skill in Claude Code (project)
.claude/skills/save-session/SKILL.md
$ npx degit kriscard/Skills/skills/obsidian/save-session .claude/skills/save-sessionInstall the save-session skill in Codex
~/.agents/skills/save-session/SKILL.md
$ npx degit kriscard/Skills/skills/obsidian/save-session ~/.agents/skills/save-sessionInstall the save-session skill in Gemini CLI
~/.gemini/skills/save-session/SKILL.md
$ npx degit kriscard/Skills/skills/obsidian/save-session ~/.gemini/skills/save-sessionInstall the save-session skill in Claude.ai
npx degit kriscard/Skills/skills/obsidian/save-session save-session && zip -r save-session.zip save-session # claude.ai → Customize → Skills → + → Create skill → Upload a skill → save-session.zip
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablekriscard/skills/skills/obsidian/save-session is public and reachablegithub.com/kriscard/skills/tree/HEAD/skills/obsidian/save-se ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-28github.com/kriscard/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/kriscard/skills/blob/HEAD/skills/obsidian/save-se ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/kriscard/skills/blob/HEAD/skills/obsidian/save-se ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/kriscard/skills/blob/HEAD/skills/obsidian/save-se ↗Finding
SKILL.md
View on GitHubSave Session
Preserve what happened in this session so the user can resume or understand it later. This is a dated
record, not an Atomic Note and not a replacement for the issue tracker. Use create-note separately
when a lesson deserves reusable Knowledge.
1. Establish the evidence
Read ../vault/SKILL.md and the live AGENTS.md. Review the available conversation and its tool
results. Incorporate supplied context without treating a request or attempted action as a completed
result. If history was compacted or unavailable, state the coverage limit.
Collect outcomes, decisions and reasons, useful examples, changed files, verification results, and work deliberately deferred. Separate pre-existing changes from work performed in this session. Exclude credentials, secrets, and unnecessary personal or workplace data.
Completion: every claimed outcome has session evidence; failures and unverified work remain explicit.
2. Resolve the session note
Use the real local date, a short descriptive title, and the schema-defined session directory. Inspect any existing note with the same title/date. Ask before updating it; otherwise choose a distinct path. Never overwrite a previous session merely because it happened on the same day.
Read a live session template if one exists. Otherwise use this outline with the session metadata required by the schema:
# Session title
## Summary
What this session was about and how it ended.
## What was done
Verified actions and outcomes.
## Decisions
What was chosen, why, and relevant alternatives.
## Useful examples
Commands, code, or explanations worth keeping.
## Changed files
Paths and the purpose of each session change.
## Deferred work
Unfinished work, known limitations, and questions left open.
Omit sections without evidence. Account for every known session-changed file, grouping repetitive paths only when the complete file list remains available in a linked receipt. Include useful detail without dumping the transcript or raw tool output. Keep planned and completed work distinct.
Completion: the path is collision-safe and the draft records both outcomes and remaining work.
3. Preview, save, and verify
Show the complete note and required log entry for approval. Write through the vault safe-write flow, reread the note, and verify metadata, links, and the approved log append. Report partial failures.
Keep daily notes unchanged. The inspiration's automatic daily append is not part of this vault's
permissions. Session records do not need wiki-index entries; offer a separate create-note proposal
for reusable explanations or questions, without creating them as a side effect.
Completion: the approved recap and log entry exist, no unrelated note changed, and the saved path plus any useful Knowledge candidates are reported.
Design source
Adapted from Fred Oliveira's done skill: retain decisions, examples, changed files, and deferred work. Use this vault's paths, ownership, approval, and safe-write rules rather than copying its shell writes or daily-note append.
Files in this skill
1save-session skill questions
How do I install the save-session skill in Claude Code?
Run npx degit kriscard/Skills/skills/obsidian/save-session ~/.claude/skills/save-session. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the save-session skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What information is included in the session recap?
The recap includes a summary, verified actions and outcomes, decisions made with their reasoning, useful code or command examples, changed files, and any deferred work.
Does this skill overwrite existing session notes?
No, the skill inspects existing notes and asks for permission before updating; otherwise, it chooses a distinct path to avoid overwriting.
Is this skill a replacement for an issue tracker or atomic notes?
No, it is a dated record intended for session continuity, not a replacement for an issue tracker or a reusable Atomic Note.