메뉴
Use when converting a Markdown file into a beautiful, print-ready PDF — reports, docs, specs, or exports with a styled cover page, running headers/footers, page numbers, tables, syntax-highlighted code, and mermaid diagrams.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when bootstrapping a repository — greenfield or brownfield — into Uhstray's standard development conventions, OpenSpec, and the two-store memory setup. Idempotent and non-destructive: safe to re-run, never overwrites existing docs. Triggers on "repo kickstart", "bootstrap this repo", "set up our conventions", "conform this repo", "initialize plans/openspec/memory", "initialize this repo for openspec and memory", "set up two-store memory here", "index this repo and create its memory bank".
Use when checking or setting up the four-strata memory system on this machine and in the current project — "is my memory set up right", "memory onboarding", "set up memory", "check my memory setup", after a fresh machine/repo, when repo-kickstart or buhhdy's preflight reports memory degradation, or when .claude/memory / MemPalace / evolve looks misconfigured.
Use when any orchestrating agent's development workflow — buhhdy's Workflow 2 is the canonical caller — has open PRs that need driving from creation through merge and cleanup — the terminal step once PRs are open. Triggers on "shepherd this PR", "drive the PR to merge", "babysit the PRs", "monitor the PR to merge", and post-merge close-out (close linked issues, archive the change, remove the worktree, janitor stale branches in the orchestrator's own prefix (buhhdy/* canonical)). Also load to verify PR-lifecycle preconditions (branch protection, CodeRabbit) before shepherding.
Use when the user says "remember", "don't forget", "save that", "keep that in mind", "recall", "what do we know about", "look that up", or any request to persist or retrieve project knowledge — stores memories in .claude/memory/ using the Claude Code memory format, committed to git so the whole team shares context.
Use when starting new planning/research on a project or picking up development against an existing plan — buhhdy's two standard, repeatable sequences: Planning & Research (fresh problem to a validated plan — an OpenSpec change where the repo has adopted the conventions — plus issues) and Development (fanout, audit, docs, and pr-shepherd).
Reference skill for buhhdy's provider routing logic — the decision tree, model tier table, per-provider strengths, skill-to-provider affinity, and cross-review pairings. Load when reasoning about which provider to use and why, or when a task doesn't clearly match the main routing tree.
| name | markdown-to-pdf |
| description | Use when converting a Markdown file into a beautiful, print-ready PDF — reports, docs, specs, or exports with a styled cover page, running headers/footers, page numbers, tables, syntax-highlighted code, and mermaid diagrams. |
Convert any Markdown file into a polished PDF: a gradient cover page, running
headers/footers with page numbers, a table of contents, GFM tables, task lists,
footnotes, Pygments-highlighted code, and rendered mermaid diagrams.
The skill ships a converter and a stylesheet — you drive them, you don't reimplement them:
${CLAUDE_PLUGIN_ROOT}/skills/markdown-to-pdf/md2pdf.py — the converter${CLAUDE_PLUGIN_ROOT}/skills/markdown-to-pdf/style.css — the print thememd2pdf.py declares its Python deps inline (PEP 723), so uv run installs
them into a throwaway env — nothing lands in the user's global Python:
@page, running headers via string-set, counter(page)/counter(pages),
named pages) — the only reliable way to get styled headers/footers and a cover.mmdc) via npx — renders ```mermaid blocks to images.# WeasyPrint needs the native Pango libs (not bundled in the wheel):
brew install pango # macOS (pulls cairo/harfbuzz/glib)
# sudo apt install libpango-1.0-0 libpangoft2-1.0-0 # Debian/Ubuntu
# uv runs the script + installs Python deps on demand: https://docs.astral.sh/uv/
# Node's npx (for mermaid) — only needed if the doc has mermaid diagrams.
On macOS, if WeasyPrint can't find Pango, prefix the command with
DYLD_FALLBACK_LIBRARY_PATH=/opt/homebrew/lib.
DIR=${CLAUDE_PLUGIN_ROOT}/skills/markdown-to-pdf
uv run "$DIR/md2pdf.py" report.md # -> report.pdf
uv run "$DIR/md2pdf.py" report.md -o out.pdf \
--title "Q3 Report" --subtitle "Revenue review" \
--author "Uhstray" --footer "Confidential"
uv run "$DIR/md2pdf.py" --help lists every flag. Useful ones:
--no-cover, --no-toc, --no-mermaid, --css PATH,
--pygments-style NAME (e.g. github-dark, monokai),
--mermaid-format png|svg (png is the most reliable).
A leading YAML block sets the cover and headers (CLI flags override it):
---
title: The Quarterly Report
subtitle: Revenue and outlook
author: Uhstray Engineering
eyebrow: Confidential
date: 2026-07-16
footer: Confidential draft
---
# First heading …
Missing title → derived from the filename. No front matter and --no-cover
→ straight into content.
| Construct | Notes |
|---|---|
| Headings, bold/italic, links, HR | Accent headings; H1/H2 feed the header |
| Bullet / ordered / nested / task lists | Custom checkboxes |
| Blockquotes | Tinted, colored left border |
| GFM tables | Accent header row, zebra striping, header repeats across pages |
| Fenced code | Pygments highlighting, kept off page breaks |
```mermaid diagrams | Rendered via mmdc, embedded as images |
| Footnotes, definition lists, strikethrough | Via pymdown-extensions |
Edit tokens in style.css (--accent, --font-body, --font-head, …) or pass
your own with --css mytheme.css. It's standard CSS Paged Media — the cover is
@page cover (full-bleed gradient, chrome suppressed); the running header/footer
live in @page margin boxes fed by string-set.
@page cover element steals page 1; keep the string-set carrier
position: absolute (see .doc-meta in style.css).npx missing (install Node) or a diagram syntax
error; the raw code block is kept and a warning printed. mmdc's first run
downloads headless Chromium (slow once).--mermaid-format png (default);
WeasyPrint's SVG renderer is a subset.--font-* tokens to families installed on the host.