Menu
Use when converting a Markdown file to a styled PDF — invokes the plugin converter. macOS only.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | markdown-to-pdf |
| description | Use when converting a Markdown file to a styled PDF — invokes the plugin converter. macOS only. |
Converts Markdown files to polished PDFs using pandoc + XeLaTeX. Produces navy-colored heading hierarchy, styled blockquotes, smart table column widths, and optional diagram rendering from code blocks.
macOS only. Requires zsh. Not supported on Windows or Linux.
${CLAUDE_PLUGIN_ROOT}/scripts/markdown-to-pdf <input.md> [output.pdf]
Invoke unsandboxed. The script spawns xelatex, pandoc, and optional diagram renderers, reads system fonts via fc-list, and writes temp + output files — operations that typically fail under the default Bash sandbox. Request unsandboxed access when calling it.
If output.pdf is omitted, the PDF is written alongside the source file with the same name.
# Generate alongside source
${CLAUDE_PLUGIN_ROOT}/scripts/markdown-to-pdf briefs/my-doc.md
# Specify output path
${CLAUDE_PLUGIN_ROOT}/scripts/markdown-to-pdf briefs/my-doc.md exports/my-doc.pdf
# Override monofont
MONOFONT="JetBrains Mono" ${CLAUDE_PLUGIN_ROOT}/scripts/markdown-to-pdf briefs/my-doc.md
Any error on startup — run ${CLAUDE_PLUGIN_ROOT}/scripts/markdown-to-pdf --check for a full diagnostic with versions and install hints for everything missing.
Diagram block silently skipped — the renderer for that diagram type isn't installed. Run --check to see which are present.
Command \underbar has changed — LaTeX package warning from texlive. Cosmetic only, does not affect output.
Use when writing, reviewing, or modifying Rust code to ensure idiomatic patterns, proper error handling, type safety, and adherence to community standards
Use when coordinating multi-agent development pipelines with phased investigation, planning, implementation, and review. Orchestrates teams of specialized agents through gated phases. Language-agnostic.
Use when setting up development toolchains with mise, managing tool versions, configuring project environments, or defining build/test/deploy tasks - covers both mise.toml for repos you control and mise.local.toml for repos you contribute to
Use when adopting mise for an existing project — detects current toolchain files and task runners, presents migration options, and generates mise.toml configuration
Use when building server-driven web applications with HTMX and Alpine.js - covers the interaction model, when to use each tool, and when NOT to use raw JavaScript
Use when writing Askama templates in Rust to ensure idiomatic patterns, fix compile errors by understanding module scope, and avoid common anti-patterns from Jinja2 muscle memory