find-session
Identify a specific Claude Code conversation by its UUID and optionally pin it as a shell function for one-word resume. Use when "claude --continue" picks the wrong session, or when the user wants to reliably resume a specific past conversation across reboots.
What this skill does
# find-session — pin a specific Claude conversation
`claude --continue` picks "most recent in cwd" — unreliable when multiple
sessions share a directory. `claude --resume <uuid>` is exact. This skill
finds the right UUID by grepping jsonl files, then writes a one-word shell
function so the user types e.g. `aichain` to resume that exact conversation.
## When to use
- User says "I can't find my session" / "claude --continue picks wrong one"
- User wants a one-word resume command for a specific long-running conversation
- Multiple `.jsonl` files in `~/.claude/projects/<encoded-cwd>/` exist
## Workflow
### 1. Find the encoded-cwd directory
Sessions are stored under `~/.claude/projects/<encoded-cwd>/`. The encoding
replaces `/` with `-`, so cwd `/Users/foo/Desktop/MyProj` becomes
`-Users-foo-Desktop-MyProj`. Often the cwd at session-start was the user's
HOME, even if work happened in a subdirectory.
If unsure which encoded-cwd to scan:
```bash
ls -dt ~/.claude/projects/*/ | head -5
```
The most recently modified directory is likely the right one.
### 2. List active session files
```bash
ls -lt ~/.claude/projects/<encoded-cwd>/*.jsonl 2>/dev/null | head -10
```
Multiple files = multiple sessions. **The biggest by size is NOT
necessarily the right one** — both the current assistant and other parallel
sessions can be wrong about that.
### 3. Get a unique-content hint from the user
Ask: "What's something only this conversation would contain? A specific
filename you created, a unique tool you ran, a project name, etc."
Good hints (highly unique):
- A hostname / URL the conversation generated (e.g. `waqvu5.png`)
- A file path that was created by this session (e.g. `kimi_research_results`)
- A specific function name written in this session (e.g. `compute_factor_scores`)
- A unique error message they remember
Bad hints (too common, will match multiple):
- Generic words like "Python", "test", "fix"
- Common library names
### 4. grep to find matching session
```bash
for f in ~/.claude/projects/<encoded-cwd>/*.jsonl; do
echo "=== $(basename "$f") ==="
grep -c "<unique-string>" "$f" 2>/dev/null
done
```
The session with non-zero hits (ideally many hits) is the answer. Confirm
with 2-3 different unique strings if the first match is ambiguous.
### 5. Offer to pin as shell function
Once UUID is identified, ask user for a short name (e.g. `aichain`,
`work`, `headsup`). Then append to `~/.zshrc`:
```bash
# <project description> — resume specific session
<short-name>() {
cd "$HOME" && claude --resume "<uuid>"
}
```
`cd "$HOME"` matters: sessions are indexed by their starting cwd, so the
alias must cd to the same place where the session was originally created
(often HOME, even if the actual work touched subdirectories).
After write, tell user to either:
- Run `source ~/.zshrc` in current terminal, OR
- Open a new terminal
## Important notes
- Each `.jsonl` is the full transcript log of one session. Sizes can mislead;
always rely on grep'd content matches, not file size.
- The UUID is stable forever — once pinned, the alias keeps working across
reboots, OS upgrades, even years (assuming the .jsonl isn't deleted).
- If user has multiple long-running parallel sessions (e.g., two different
projects, both started from HOME), each needs its own pin. Repeat the
workflow once per session.
- Don't confuse session UUIDs across different conversations. If two Claude
instances both claim the same UUID, at least one is wrong — only grep on
actual unique content can verify.
## Quick check
After pinning, verify:
```bash
source ~/.zshrc && type <short-name>
```
Should show the function definition.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.