Menu
Export Claude conversation logs to markdown
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when checking Buildkite CI/CD builds, investigating failures, viewing job logs, or answering questions about pipeline status.
Write a handoff brief summarizing the current conversation so a fresh agent can pick up the work. Writes to a file if given, otherwise copies to the clipboard.
Use when bootstrapping hk pre-commit hooks for a project.
Use when adding, updating, troubleshooting, or managing mise tool dependencies. Supplements /install with mise-specific context about backends, lockfiles, and the github-first policy.
Add a tool pattern to the global Claude Code permissions allow list in bin/sync-claude-settings
Use when labeling GitHub issues or triaging the backlog. Applies the project's label taxonomy from docs/labels.md.
| name | export-log |
| description | Export Claude conversation logs to markdown |
| argument-hint | [CONVERSATION...] |
| disable-model-invocation | true |
| context | fork |
| allowed-tools | Bash(claude-extract:*), Grep, Read |
Export conversations using claude-conversation-extractor.
Session ID: ${CLAUDE_SESSION_ID}
$ARGUMENTS
Parse the arguments and determine the export method:
claude-extract --list 2>/dev/null | grep -B5 "${CLAUDE_SESSION_ID:0:8}" to find the session numberclaude-extract --extract <number> --detailedIf arguments are comma-separated numbers like 1, 1,3,5:
claude-extract --extract <numbers> --detailedIf arguments look like hex strings (e.g., 97b86784, 14b9611d-cd1a):
claude-extract --list 2>/dev/null | grep -B5 "<prefix>" to find the session numberclaude-extract --extract <numbers> --detailedIf arguments are freeform text:
claude-extract --search "<text>"Report the exported file path(s) and message count to the user.
If unsure about available options, run claude-extract --help.