session-save
Compress and save current session context for handoff to next session. Use when: (1) context pressure >50%, (2) user says "сохрани сессию", "session save", "checkpoint", (3) before ending a long productive session, (4) switching to a different task mid-session. Supports named sessions: /session-save vpn-fix
Best use case
session-save is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Compress and save current session context for handoff to next session. Use when: (1) context pressure >50%, (2) user says "сохрани сессию", "session save", "checkpoint", (3) before ending a long productive session, (4) switching to a different task mid-session. Supports named sessions: /session-save vpn-fix
Teams using session-save should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/session-save/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How session-save Compares
| Feature / Agent | session-save | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Compress and save current session context for handoff to next session. Use when: (1) context pressure >50%, (2) user says "сохрани сессию", "session save", "checkpoint", (3) before ending a long productive session, (4) switching to a different task mid-session. Supports named sessions: /session-save vpn-fix
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Session Save — Named Context Checkpoints
Compress current session state → save to named checkpoint file.
## Storage
<!-- 📌 НАСТРОЙТЕ: путь к вашему проекту (Claude Code кодирует / как -) -->
```
~/.claude/projects/<YOUR-PROJECT-PATH>/memory/sessions/
{name}.md ← named checkpoints
_latest.md ← always points to last saved
~/.claude/projects/<YOUR-PROJECT-PATH>/memory/last-session.md ← legacy compat
```
## Naming Rules
- If user provides name: use as-is (slug, lowercase, hyphens). Example: `vpn-fix`, `auth-refactor`
- If no name: auto-generate from goal. Pattern: `{topic}-{MMDD}`. Example: `insights-0303`
- Sanitize: `[^a-z0-9-]` → `-`, max 40 chars
## Compression Format (InfoCompressor)
Use imperative, terse, scannable style. 40-60% reduction. Zero redundancy.
### Template
```markdown
# Session: {name}
saved: YYYY-MM-DDTHH:MM
context: XX% (XXK tokens)
branch: <git branch>
name: {name}
## Goal
<1-2 sentences: what user wanted to achieve>
## Done
- <completed step 1>
- <completed step 2>
## Pending
- <next step 1>
- <next step 2>
## Modified Files
- `path/to/file1` — what changed
- `path/to/file2` — what changed
## Key Decisions
- <decision 1: chosen → reason>
## Context (carry forward)
<2-5 lines of critical context that next session MUST know>
## Continuation Prompt
<Ready-to-paste prompt for next session to resume work>
```
## Steps
1. **Determine name** — from argument or auto-generate from goal
2. **Analyze session** — review conversation history, identify goal/progress/pending
3. **Check git** — `git status`, `git diff --stat`, current branch
4. **Compress** using InfoCompressor principles:
- Imperative mood, present tense, active voice
- 3-7 words per statement
- `→` for causality, `|` for alternatives
- Cut filler words, state each fact once
5. **Write checkpoint** to `sessions/{name}.md`
6. **Copy to legacy** — also write to `last-session.md`
7. **Save to memory** — `mcp__memory__add_observations` on entity `Session-Checkpoint-{name}`:
- goal, done count, pending, files, timestamp
8. **Confirm** — show:
```
✅ Session saved: {name}
📁 sessions/{name}.md
🔄 Resume: /continue {name}
```
## Rules
- Never lose: file paths, entity names, error messages, numeric values
- Checkpoint must be self-contained — readable without original session
- Continuation prompt must be specific enough to resume without questions
- Keep under 2KB (aim for 1KB)
- Overwrite existing checkpoint with same name (warn user first)
## Context Pressure Auto-Trigger
When context > 50% (🟡 WARNING):
1. Announce: "Context pressure 🟡 — saving checkpoint"
2. Run this skill automatically (auto-generate name)
3. Suggest: "Рекомендую `/continue {name}` в новой сессии"
When context > 72% (🔴 CRITICAL):
1. Save checkpoint immediately
2. **HANDOFF MODE** — refuse further execution
3. Write handoff blobRelated Skills
/tg-saved v2 — Telegram Saved Messages → Deep Analysis → Obsidian
## Назначение
session-status
Statusline shown in Claude Code UI status bar via settings.json. No action needed in responses.
continue-session
Restore context from a named or latest session checkpoint. Use when: (1) user says "продолжи", "continue", "что было в прошлой сессии", (2) starting work after a crash or context overflow, (3) "resume", "восстанови контекст", "где я остановился". Supports named sessions: /continue vpn-fix
writing-content
Интерактивный процесс написания текстов для вайб-маркетинга на основе Julian Shapiro framework. **Новые возможности (v2.0):** - Research & Gap Analysis (Perplexity → WebSearch fallback) - Scoring 0-5 вместо binary (Novelty + Resonance + Hook + Clarity) - AI-Slop Detection на всех этапах (10 типов patterns) - 3 варианта intro с self-scoring - Markdown export всех промежуточных результатов **Русские triggers:** "напиши пост по шапиро", "написать статью по фреймворку шапиро", "создай текст в стиле julian shapiro", "помоги написать контент по методу shapiro", "контент по julian shapiro фреймворку", "пост по julian shapiro", "напиши в стиле шапиро" **English triggers:** "write content using julian shapiro framework", "create post with shapiro method", "write article shapiro style", "help with julian shapiro writing" **Generic triggers:** "напиши статью", "помоги написать контент", "создай текст", "начать писать", "хочу написать пост", "нужна помощь с текстом", "write content", "write article", "создай контент", "придумай идею для статьи", or requests help with content creation process.
YT Transcribe — YouTube → Whisper → Obsidian
Транскрибирует YouTube-видео через mlx-whisper (Apple Silicon, Metal-native) с параллельными чанками.
summarize-comments
Делает LLM-выжимку из комментариев менеджеров об одном или нескольких подрядчиках. Используй этот скилл когда нужно понять что говорят менеджеры о конкретном подрядчике, или получить JSON с выжимкой для дальнейшей обработки.
skill-security
This skill activates when the user mentions "security audit", "skill audit", "проверка безопасности скилла", "аудит скилла", "skill-security", "проверить скилл", "пересобрать скилл", "rebuild skill", "security check", "dual memory audit", "credential isolation check". Also activates on /skill-security command. Use this skill when the user wants to audit, validate, or rebuild any Claude Code skill for security compliance.
compress
Info-Compressor: compress text/context by 60-70% without losing meaning. Use when: (1) context pressure >50%, (2) user says "сжать", "compress", "compact", (3) need to fit more context into remaining window, (4) preparing handoff blob for next session.
seo-strategist
Strategic SEO planning and analysis toolkit for site-wide optimization, keyword research, technical SEO audits, and competitive positioning. Complements content-creator's on-page SEO with strategic planning, topic cluster architecture, and SEO roadmap generation. Use for keyword strategy, technical SEO audits, SERP analysis, site architecture planning, or when user mentions SEO strategy, keyword research, technical SEO, or search rankings.
roi-razvitie-draft
Generates a draft meeting document for the weekly "Roi Развитие" (Wednesday, product Roi Navigator). Use when the user asks for a draft for the meeting, for Wednesday's doc, for "Roi Развитие", or for the weekly team meeting agenda.
project-knowledge-base
Collects, structures and maintains a Project Knowledge Base (PKB.md) in Obsidian for a marketing agency. Aggregates data from Google Drive, Gmail, Telegram (group chat and DMs via MTProto), moo.team tasks/comments, and local Obsidian meeting transcripts. Uses async parallel collection and a two-stage LLM pipeline for init. Use when the user wants to initialize, update or enrich a project's knowledge base, mentions PKB, project knowledge base, синхронизация проекта, база знаний проекта, init_project_knowledge, update_project_knowledge, or ad_hoc_add_context.
product-strategist
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.