Session save

Skill az9713/youtube-transcript-to-skills/.claude/skills/session-save

Extract Claude Code skills from AI workflow YouTube transcripts. 10 ready-to-use skills + a meta-skill that automates the extraction process. Built from John Kim's 50 Claude Code tips.

Install

npx -y skills add az9713/youtube-transcript-to-skills --skill session-save

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Save current session progress, TODOs, and context to a local file before ending a session. Enables picking up later with /session-load.

SKILL.md

2.1 KB, 478 tokens by cl100k_base, as published. Nobody here has run it

Session Save

Capture current session progress so you can resume later with /session-load.

Usage

/session-save

Procedure

Step 1: Gather Session Context

Collect the following information:

Current branch: Run git branch --show-current
Modified files: Run git status --short to see what's changed
Recent commits: Run git log --oneline -5 for recent history
Current working directory: Note the cwd

Step 2: Summarize the Session

Create a session summary by reviewing what was accomplished:

What was done: List completed tasks/changes in this session
What's pending: List unfinished work or known TODOs
Key decisions: Any architectural or design decisions made
Blockers: Anything that's blocking progress
Context notes: Important context that would be lost between sessions

Step 3: Generate Session File

Create the file at .claude/sessions/<date>-<topic>.md:

<date> = today's date in YYYY-MM-DD format
<topic> = a short slug describing the session's focus (e.g., auth-refactor, api-endpoints)

# Session: [Topic]
**Date**: [YYYY-MM-DD]
**Branch**: [branch-name]

## Completed
- [What was accomplished]
- [What was accomplished]

## Pending TODOs
- [ ] [Task description]
- [ ] [Task description]

## Key Decisions
- [Decision and rationale]

## Blockers
- [Blocker description, if any]

## Modified Files
[Output of git status --short]

## Context Notes
[Any important context for resuming, e.g., "The API design follows the pattern in src/api/users.ts",
"We chose approach X over Y because..."]

## Resume Instructions
To continue this work:
1. Check out branch: `git checkout [branch]`
2. Start with: [description of next step]

Step 4: Confirm Save

Tell the user:

Where the file was saved
How to resume: "Run /session-load in your next session to pick up where you left off"