share-transcript
This skill should be used when the user asks to "share this session", "upload transcript", "create gist", "share conversation", or wants to publish the current Claude Code session as a GitHub Gist.
What this skill does
# Share Transcript
Uploads the current Claude Code session to GitHub Gist and adds it to the project's gist index.
## Instructions
### Step 1: Find Current Session File
1. Get the current working directory to identify the project
2. Find the most recent session file for this project:
```bash
# Extract project path from current directory
PROJECT_PATH=$(pwd)
PROJECT_SLUG=$(echo "$PROJECT_PATH" | sed 's/\//-/g')
# Find most recent session file for this project
SESSION_FILE=$(find ~/.claude/projects -path "*${PROJECT_SLUG}*" -name "*.jsonl" -type f -printf "%T@ %p\n" 2>/dev/null | sort -rn | head -1 | awk '{print $2}')
# Verify file exists
if [ -z "$SESSION_FILE" ]; then
echo "Error: No session file found for this project"
exit 1
fi
echo "Found session: $SESSION_FILE"
```
### Step 2: Upload to GitHub Gist
Run the claude-code-transcripts tool:
```bash
claude-code-transcripts json --gist "$SESSION_FILE"
```
This will output something like:
```
Generated page-001.html
Generated page-002.html
Generated /tmp/claude-session-<id>/index.html (13 prompts, 3 pages)
Creating GitHub gist...
Gist: https://gist.github.com/username/gist-id
Preview: https://gisthost.github.io/?gist-id/index.html
```
### Step 3: Parse Output
Extract the two URLs from the output:
- Look for line starting with "Gist: " to get the gist URL
- Look for line starting with "Preview: " to get the preview URL
### Step 4: Get Description from User
Use AskUserQuestion to ask the user for:
**Question**: "What's a brief description for this session?"
**Options**:
- "Feature planning session"
- "Implementation work"
- "Debugging session"
- "Architecture discussion"
Allow custom text input via "Other" option.
Also ask for the feature number if relevant (optional).
### Step 5: Update gist-list.md
1. Check if `aidocs/gist-list.md` exists in the current project
2. Get current date in YYYY-MM-DD format
3. Create the new entry:
```markdown
- **{description}** ({date})
- Gist: {gist-url}
- Preview: {preview-url}
```
4. Append to the file (after the `---` separator and any existing entries)
### Step 6: Confirm Completion
Display:
- ✅ Gist created successfully
- The preview URL (as a clickable link if possible)
- ✅ Added to aidocs/gist-list.md
- Suggested next action: "Share the preview URL with your team"
## Error Handling
**If session file not found**:
```
❌ Error: Could not find session file for this project
The session may not have been saved yet, or this directory may not be a Claude Code project.
Try running a command first to ensure a session exists.
```
**If gist upload fails**:
```
❌ Error: Failed to upload gist
Verify GitHub authentication:
gh auth status
gh auth login
Then retry: /share-transcript
```
**If gist-list.md doesn't exist**:
Create it with the header:
```markdown
# Claude Code Session Gists
Shareable links to notable Claude Code sessions for this project.
---
```
## Example Output
```
Finding current session...
✓ Found: ~/.claude/projects/-home-cip-src-giant-computer-aegis/af4d62e3.jsonl
Uploading to GitHub Gist...
✓ Generated 3 pages (13 prompts)
✓ Gist created: https://gist.github.com/ianphil/ef6f4483dc1dda8e8865b629e143752f
[User provides description: "Feature 001 MCP Integration - Planning & Work Plan Setup"]
✓ Added to aidocs/gist-list.md
Preview URL: https://gisthost.github.io/?ef6f4483dc1dda8e8865b629e143752f/index.html
Share this URL with your team!
```
## Notes
- Always append to gist-list.md, never overwrite
- Keep descriptions concise (under 80 characters)
- Include feature number if applicable
- Use current date in YYYY-MM-DD format
- Preview URL is the one to share (more readable than raw gist)
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.