home/dot_claude/skills/export-log/SKILL.md
Export Claude conversation logs to markdown
npx skillsauth add ivy/dotfiles export-logInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
tools
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.
data-ai
Use when the user wants to set, change, or clear git commit co-authors for pair or mob programming.
tools
Use when bootstrapping hk pre-commit hooks for a project.
testing
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".