Session load

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

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-load

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

Load saved session context from a previous session. Lists available sessions and restores TODOs, context, and pending work.

SKILL.md

2.2 KB, 496 tokens by cl100k_base, as published. Nobody here has run it

Session Load

Restore context from a previously saved session (created with /session-save).

Usage

/session-load — List available sessions and choose one
/session-load <filename> — Load a specific session file

Procedure

Step 1: Find Available Sessions

Check if $ARGUMENTS specifies a file. If not:

List files in .claude/sessions/ directory
Sort by date (newest first)
Show the user a numbered list:

Available sessions:
1. 2025-01-15-auth-refactor.md
2. 2025-01-14-api-endpoints.md
3. 2025-01-12-initial-setup.md

Which session would you like to load?

If $ARGUMENTS specifies a file, use that directly.

If .claude/sessions/ doesn't exist or is empty, tell the user:

"No saved sessions found. Use /session-save to save your current session before ending it."

Step 2: Load Session File

Read the selected session file and extract:

Branch name
Pending TODOs
Context notes
Resume instructions

Step 3: Verify Current State

Check if the current environment matches the session:

Branch check: Is the user on the same branch? If not, ask:

"The session was on branch [branch] but you're on [current]. Switch branches?"
File check: Do the modified files mentioned in the session still exist?
Git status: Are there uncommitted changes that might conflict?

Step 4: Present Session Context

Display a concise summary of what was happening:

## Restored Session: [Topic]
**Date**: [date]
**Branch**: [branch]

### Where We Left Off
[Resume instructions from the session file]

### Pending TODOs
- [ ] [Task 1]
- [ ] [Task 2]

### Key Context
[Context notes]

Step 5: Offer to Continue

Ask the user:

"Ready to pick up where we left off? The next step was: [resume instruction]. Should I start with that?"

Do NOT automatically start working. Let the user confirm what they want to do first. They may have changed priorities since the last session.