skills/markdown-to-pdf/SKILL.md
Renders a markdown report to a PDF using pandoc with xelatex (11pt serif body, 1-inch margins, numbered footnotes, formal heading hierarchy). Requires a one-time install of pandoc and a LaTeX engine on the user's machine — basictex on macOS or texlive-xetex on Linux. Does not attempt automatic install. Fails loudly with the exact install commands if pandoc or xelatex is missing on the user's PATH. Use when producing a finished strategist or analyst report PDF from a polished markdown source.
npx skillsauth add lyndonkl/claude markdown-to-pdfInstall 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.
Converts a finished markdown report to a PDF using pandoc and the xelatex engine, with formatting tuned for analyst-style output.
This skill assumes pandoc and a LaTeX engine are already on the user's PATH. It does not install anything. If either tool is missing, the render command exits with the exact install instructions and the user installs once.
macOS:
brew install pandoc basictex
sudo tlmgr update --self
sudo tlmgr install xetex
basictex is about 90 MB. Do not install mactex unless the user specifically needs the full LaTeX stack (~5 GB).
Linux (Debian/Ubuntu):
sudo apt install pandoc texlive-xetex texlive-fonts-recommended
After installation, open a new shell so xelatex is on PATH.
Copy this checklist into the working response and tick each step as it completes:
Markdown-to-PDF render:
- [ ] Step 1: Verify the input markdown file exists.
- [ ] Step 2: Verify pandoc is on PATH. If missing, print the pandoc install block and stop.
- [ ] Step 3: Verify xelatex is on PATH. If missing, print the xelatex install block and stop.
- [ ] Step 4: Create the output directory if it does not already exist.
- [ ] Step 5: Run the pandoc command exactly as specified below.
- [ ] Step 6: Confirm the output PDF file exists. Report its path.
command -v pandoc
If this exits non-zero, print the block in "Failure messages" labelled pandoc-missing and stop. Do not proceed to Step 5.
command -v xelatex
If this exits non-zero, print the block in "Failure messages" labelled xelatex-missing and stop. Do not proceed to Step 5.
Substitute the input and output paths but do not modify any flag:
pandoc <INPUT_MD> \
--from markdown+footnotes+yaml_metadata_block \
--pdf-engine=xelatex \
--output <OUTPUT_PDF> \
--variable geometry:margin=1in \
--variable papersize=letter \
--variable fontsize=11pt \
--variable linestretch=1.2 \
--variable colorlinks=true \
--variable linkcolor=black \
--variable urlcolor=black \
--variable toccolor=black
The variables are tuned for analyst-style output: letter-size paper, 1-inch margins, 11pt body at 1.2 line height, all hyperlinks rendered in black so the printed page reads cleanly.
test -s <OUTPUT_PDF> && echo "PDF rendered: <OUTPUT_PDF>"
If the output file does not exist or is empty after pandoc returns success, treat that as a render failure and surface the pandoc stderr to the user.
Print these blocks exactly as written. They are the contract with the user.
ERROR: pandoc is not installed.
This skill requires pandoc and a LaTeX engine.
Install on macOS:
brew install pandoc basictex
sudo tlmgr update --self
sudo tlmgr install xetex
Install on Linux (Debian/Ubuntu):
sudo apt install pandoc texlive-xetex texlive-fonts-recommended
Open a new shell after installing so the new binaries are on PATH, then re-run.
ERROR: xelatex is not installed.
pandoc is present, but the LaTeX engine (xelatex) is missing.
Install on macOS:
brew install basictex
sudo tlmgr update --self
sudo tlmgr install xetex
Install on Linux (Debian/Ubuntu):
sudo apt install texlive-xetex texlive-fonts-recommended
Open a new shell after installing, then re-run.
text.[^1] in the body with [^1]: ... definitions later in the file. These render as proper LaTeX footnotes.title:, subtitle:, and date: fields, those will appear in the rendered title block.testing
Cluster a conference's event records into a small set of coarse themes with finer sub-clusters, an explicit outlier bucket, and soft (multi-membership) affinities — using the hybrid embed-then-label pipeline (embed abstracts, reduce, density-cluster, then LLM-label the clusters) when embedding libraries are available, and an LLM-reasoned hierarchical fallback when they are not. Embeddings do the grouping; the LLM only names the groups. Conference-agnostic. Use when turning structured event records into a navigable theme map for preference elicitation and scheduling, when you need 6-8 reasonable themes rather than 20 muddy ones, or when overlapping talks must belong to more than one theme. Trigger keywords - theme clustering, cluster talks, embed then label, soft membership, outlier talks, conference themes, topic map.
development
Build a personal conference schedule as a constraint-optimization problem — hard constraints (no time overlap, room-to-room travel time, capacity/registration, the attendee's own must-attends and blackouts) plus a user-owned weighted objective trading interest against breadth, pacing (maximize contiguous free time), and serendipity. Surfaces unbreakable conflicts (two high-value overlapping talks the model cannot rank) as decisions for the human rather than silently picking, and reports what each choice traded away. Conference-agnostic. Use to turn a preference profile plus a theme map into a day-by-day plan, to resolve overlapping sessions, or to balance a packed vs paced schedule. Trigger keywords - schedule optimization, conference schedule, constraint optimization, overlapping talks, contiguous free time, conflict surfacing, packed vs paced.
development
Parse a heterogeneous conference program (markdown, HTML, PDF-derived text, or JSON) into normalized event records with per-field confidence scores and independent classification axes (topic, depth, format, prerequisites, recorded, capacity). Detects the program's format before extracting, treats every inferred field as uncertain (present vs inferred vs missing), and flags thin or missing abstracts so downstream enrichment can target them. Conference-agnostic. Use when ingesting a conference or event schedule into a structured store, normalizing a talk/session list, or extracting per-session metadata with calibrated confidence. Trigger keywords - program ingestion, parse schedule, session extraction, event records, conference program, talk metadata, per-field confidence.
development
Build a personalized preference profile from a small number of well-chosen, cluster-grounded questions instead of a long survey. Represents the person's interests as an uncertainty region over the theme map, picks the single highest-information-gain choice-based question (contrasting real talks from different clusters), balances exploiting known interests against exploring uncertain ones, deliberately injects outlier probes to fight selection bias, and stops as soon as the schedule would be stable. Also elicits the user-owned objective weights and hard constraints. Interactive — runs where it can actually ask the person. Conference-agnostic. Use to turn a theme map into a preference profile, to decide what to ask a conference attendee, or to elicit scheduling priorities. Trigger keywords - preference elicitation, ask few questions, information gain, choice-based questions, selection bias probe, objective weights, attendee preferences.