pdf

Export to PDF

Export summaries, research, or any content from the conversation to a professionally styled PDF for sharing.

Arguments

• $ARGUMENTS - Optional: filename (without .pdf extension) or "last" to export the last assistant message

Instructions

You are exporting content from the current conversation to a shareable PDF document.

Step 1: Identify Content to Export

Determine what content the user wants to export:

1. If user says "last" or no arguments: Export the most recent substantive assistant response (summary, research, analysis, etc.)
2. If user provides a topic: Find the relevant content from the conversation about that topic
3. If user provides specific text: Use that text directly

Step 2: Prepare the Content

Clean up the content for PDF export:

• Keep all markdown formatting (headers, tables, bullets, code blocks)
• Remove any conversation artifacts or meta-commentary
• Ensure links are preserved
• Keep the "Sources" section if present

Step 3: Determine Filename and Title

Generate appropriate names:

• Filename: Use provided argument, or generate from content (e.g., ai-orchestration-tools-2026)
  • Use lowercase, hyphens for spaces
  • Keep under 50 characters
  • Add date suffix if relevant (e.g., -2026-02-05)
• Title: Generate a professional title from the content's main heading or topic

Step 4: Generate PDF

Write the content to a temporary markdown file using a Bash heredoc (do NOT use the Write tool — it may be sandboxed to the workspace directory and reject /tmp paths), then convert to PDF:

# Write content to temp file — MUST use Bash heredoc, not the Write tool
cat << 'CONTENT_EOF' > /tmp/export_content.md
{markdown content here}
CONTENT_EOF

# Convert to PDF using the colocated script
python ~/.claude/skills/pdf/scripts/md_to_pdf.py \
  --input /tmp/export_content.md \
  --output ~/Downloads/{filename}.pdf \
  --title "{title}"

Important: Always use the Bash tool with cat << 'CONTENT_EOF' > /tmp/... for the temp file. The Write tool is sandboxed in some environments (e.g., Conductor workspaces) and will refuse paths outside the workspace.