// Convert Markdown to PDF (or DOCX/EPUB/HTML) using the `pandoc` CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file.
| name | pandic-office |
| description | Convert Markdown to PDF (or DOCX/EPUB/HTML) using the `pandoc` CLI. Use when asked to produce a PDF report, brief, summary, or any document where the input is Markdown and the output should be a polished, paginated file. |
Pandoc is installed at /usr/bin/pandoc. The XeLaTeX engine (xelatex) is
installed for PDF output. Both work non-interactively in the agent workspace.
# Markdown → PDF (default LaTeX engine)
pandoc input.md -o output.pdf --pdf-engine=xelatex
# Markdown → DOCX (Word document)
pandoc input.md -o output.docx
# Markdown → EPUB (e-book)
pandoc input.md -o output.epub
# Markdown → standalone HTML
pandoc input.md -o output.html --standalone
cat > /workspace/$(basename "$PWD")/brief.md <<'EOF'
# Q1 Engineering Brief
## Highlights
- Shipped feature X
- Closed Y bugs
## Risks
- Z dependency upgrade pending
EOF
pandoc /workspace/$(basename "$PWD")/brief.md \
-o /workspace/$(basename "$PWD")/brief.pdf \
--pdf-engine=xelatex \
-V geometry:margin=1in \
-V fontsize=11pt
| Flag | Effect |
|---|---|
--toc | Insert a table of contents |
-V geometry:margin=1in | Set page margins |
-V fontsize=11pt | Set body font size |
--number-sections | Auto-number headings |
--metadata title="..." | Set document title |
-o file.pdf | Output filename + format (inferred from extension) |
Attach it to chat using the commonly_attach_file tool (a kernel verb):
commonly_attach_file({
podId: "<the pod>",
filePath: "brief.pdf", // workspace-relative
message: "Q1 brief attached."
})
The file path must stay inside /workspace/<accountId>/ — .. and absolute
paths outside the workspace are rejected.
--pdf-engine=xelatex.--variable=tables:true and use simple
Markdown table syntax (no merged cells).officecli instead.pdf skill.markdown-converter.Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.
Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable'. Routes to `officecli merge` with one of three pre-built starter templates that already carry the Commonly palette, fonts, and structure — so you populate content with one merge call instead of 30 individual `officecli set` commands. DO NOT use for fundraising decks (use `officecli-pitch-deck`), academic papers (use `officecli-academic-paper`), or financial models (use `officecli-financial-model`).
Interact with GitHub (issues, PRs, repos, releases) using the `gh` CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
Convert binary documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, images) to clean LLM-friendly Markdown using Microsoft's `markitdown` Python tool. Use when a user attaches a binary file and you need to read its contents.
Manipulate PDF files — extract text, count pages, render thumbnails, merge or split documents. Use for PDF-specific operations that don't fit `markdown-converter` (general read) or `pandic-office` (write from markdown).
Manage long-running shell sessions with tmux — start a detached session, run a long task, reattach later, capture output. Use when a task takes longer than a single tool call (build, test, log tail).