How do I install the Pandic Office skill?

Run npx skillmds@latest add team-commonly/pandic-office in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pandic Office safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pandic Office?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pandic Office free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pandic Office?

team-commonly (@team-commonly) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pandic Office by team-commonly — Agent Skill

Name: Pandic Office
Author: team-commonly

Pandic Office

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.

File contents

pandic-office — Markdown → PDF / DOCX / EPUB / HTML via pandoc

Pandoc is installed at /usr/bin/pandoc. The XeLaTeX engine (xelatex) is installed for PDF output. Both work non-interactively in the agent workspace.

Common conversions

# 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

Producing a one-page brief

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

Useful flags

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)

After producing the file

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.

Troubleshooting

"xelatex not found" — pandoc fell back to a missing TeX engine. Always pass --pdf-engine=xelatex.
"Could not convert image" — embedded images need to be local file paths inside the workspace, not http URLs (unless you pre-fetch them).
Tables render badly in PDF — add --variable=tables:true and use simple Markdown table syntax (no merged cells).

When NOT to use pandic-office

For DOCX/XLSX/PPTX with rich layouts → use officecli instead.
For PDF manipulation (extract text, merge, split) → use the pdf skill.
For converting binary docs → markdown for input → use markdown-converter.

---name: pandic-officedescription: 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.---# pandic-office — Markdown → PDF / DOCX / EPUB / HTML via pandocPandoc is installed at `/usr/bin/pandoc`. The XeLaTeX engine (`xelatex`) isinstalled for PDF output. Both work non-interactively in the agent workspace.## Common conversions```bash# 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 HTMLpandoc input.md -o output.html --standalone```## Producing a one-page brief```bashcat > /workspace/$(basename "$PWD")/brief.md <<'EOF'# Q1 Engineering Brief## Highlights- Shipped feature X- Closed Y bugs## Risks- Z dependency upgrade pendingEOFpandoc /workspace/$(basename "$PWD")/brief.md \ -o /workspace/$(basename "$PWD")/brief.pdf \ --pdf-engine=xelatex \ -V geometry:margin=1in \ -V fontsize=11pt```## Useful flags| 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) |## After producing the fileAttach 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 absolutepaths outside the workspace are rejected.## Troubleshooting- **"xelatex not found"** — pandoc fell back to a missing TeX engine. Always pass `--pdf-engine=xelatex`.- **"Could not convert image"** — embedded images need to be local file paths inside the workspace, not http URLs (unless you pre-fetch them).- **Tables render badly in PDF** — add `--variable=tables:true` and use simple Markdown table syntax (no merged cells).## When NOT to use pandic-office- For DOCX/XLSX/PPTX with rich layouts → use `officecli` instead.- For PDF *manipulation* (extract text, merge, split) → use the `pdf` skill.- For converting binary docs → markdown for *input* → use `markdown-converter`.

Frequently asked questions