CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An efficient, highly actionable skill body: executable commands for every supported format, environment-specific details, troubleshooting, and clear scope boundaries. The only gaps are a missing output-verification step before attachment and slightly awkward path handling in the brief example.

DimensionReasoningScore

Conciseness

Every section earns its tokens with information Claude would not already know: "Pandoc is installed at `/usr/bin/pandoc`... Both work non-interactively in the agent workspace", the flag table, attach-tool constraints, and a when-not-to-use section. There is no re-teaching of known concepts and no padding, matching the lean anchor 5.

5 / 5

Actionability

Commands are fully executable and copy-paste ready — "pandoc input.md -o output.pdf --pdf-engine=xelatex" plus DOCX/EPUB/HTML variants, a complete heredoc brief example with concrete flags, and specific troubleshooting fixes. This covers the common cases exactly as anchor 5 asks.

5 / 5

Workflow Clarity

The sequence is clear (write the Markdown, run pandoc with the listed flags, then attach via `commonly_attach_file`), but there is no checkpoint verifying the PDF was actually produced before attachment, and the `/workspace/$(basename "$PWD")` path construction is confusing to adapt. It is better than anchor 3 because the core action is unambiguous and the operation is neither destructive nor batch, but lacks anchor 5's explicit validation step.

4 / 5

Progressive Disclosure

The single file is well-organized into clearly labeled sections with no buried references and no content that demands a separate file, which is good structure per anchor 4. At roughly 83 lines with everything inline (the flag table and the full brief example), it sits past the lean under-50-line threshold where inline-only structure earns anchor 5.

4 / 5

Total

18

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states the tool, the conversion direction, and all four output formats, with an explicit and natural 'Use when...' trigger clause. The only weaknesses are minor: no file-extension or synonym keywords, and a slightly broad tail clause that dilutes distinctiveness.

DimensionReasoningScore

Specificity

"Convert Markdown to PDF (or DOCX/EPUB/HTML) using the `pandoc` CLI" names the tool and four concrete output formats, which is several specific actions. It falls short of anchor 5 because every action is a single conversion verb with no additional capabilities listed, but exceeds anchor 3's '1-2 concrete actions' bar.

4 / 5

Completeness

It explicitly answers both questions: the what is "Convert Markdown to PDF (or DOCX/EPUB/HTML) using the `pandoc` CLI" and the when is "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" — concrete trigger phrases matching anchor 5. It is not 4 because the when-clause is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Natural user phrases like "PDF report, brief, summary" and "polished, paginated file" give good keyword coverage alongside format names (Markdown, DOCX, EPUB, HTML). It misses the file extensions (.pdf, .docx) and synonyms ("Word document") that anchor 5 requires, but coverage is well beyond anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The Markdown-input and paginated-output constraints carve a clear niche with distinct triggers, but "any document where the input is Markdown and the output should be a polished, paginated file" broadens scope, leaving minor overlap risk with general document-creation/office skills. It is more distinct than anchor 3's generic 'Works with document files' but does not fully meet anchor 5's minimal-conflict bar.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Team-Commonly/commonly

Path

backend/commonly-bundled-skills/pandic-office/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.