elegant-reports — Claude Code skill: Nordic PDF reports, install guide
elegant-reports turns markdown into a clean PDF report — executive brief, analysis write-up or slide-style deck — with bundled templates and themes.
MIT ★ 239 updated 2026-08-30
npx skills add jdrhyne/agent-skills --skill elegant-reports -a claude-codeWhat elegant-reports does
The skill reads a markdown file and returns a PDF rendered by Nutrient DWS. Layout comes from templates instead of being improvised each time. executive handles short briefings, report handles denser analysis, presentation gives one idea per page; two demo variants sit alongside for comparison. Themes are light and dark.
The bundle carries a generate.js CLI, the HTML templates and themes, sample markdown, and a note on the Nordic design system. Title, subtitle, author, template and theme are declared in YAML frontmatter. Pass --output-html and the rendered HTML is written next to the PDF, which is how you trace a bad margin back to the template.
You need Node.js 18+, the pinned dependencies from package-lock.json, and NUTRIENT_DWS_API_KEY in the environment. No key means no PDF, since rendering runs on a remote service and the source document leaves your machine. On internal material that trade-off outweighs the styling. The skill also instructs the agent to stay inside approved directories and to leave dependency versions untouched unless asked.
What it helps with
- turn a markdown draft into a board-ready PDF
- switch a finished report to the dark theme
- inspect the rendered HTML to fix spacing in a template
- build a slide-style PDF with one idea per page
- compare a new layout against the demo template
Example prompts for the agent
- Generate a PDF from
examples/sample-executive.mdusing theexecutivetemplate and the light theme - List the templates and themes this skill ships with
- Rebuild the report with
--output-htmlso I can check the HTML
How to install elegant-reports
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill elegant-reports -a claude-code2Manually: put the files in place
~/.claude/skills/elegant-reports/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/elegant-reports/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill elegant-reports -a codex2Manually: put the files in place
.agents/skills/elegant-reports/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill elegant-reports -a cursor2Manually: put the files in place
.cursor/skills/elegant-reports/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jdrhyne/agent-skills skills/elegant-reports2Manually: put the files in place
.github/skills/elegant-reports/SKILL.md1Skills CLI (Vercel)
npx skills add jdrhyne/agent-skills --skill elegant-reports -a gemini-cli2Platform CLI
gemini skills install https://github.com/jdrhyne/agent-skills --path skills/elegant-reportsManually: put the files in place
.devin/skills/elegant-reports/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about elegant-reports
How do I install elegant-reports in Claude Code?
Run npx skills add jdrhyne/agent-skills --skill elegant-reports -a claude-code. The skill lands at ~/.claude/skills/elegant-reports/SKILL.md.
What does elegant-reports do?
It converts markdown with YAML frontmatter into a styled PDF, picking a template and theme and sending the render to Nutrient DWS.
Do I need an API key for PDF output?
Yes. NUTRIENT_DWS_API_KEY must be set in the environment, because rendering happens on the Nutrient DWS side rather than locally.
Source text
SKILL.md · MIT
---
name: elegant-reports
description: Generate beautifully designed PDF reports with a Nordic/Scandinavian aesthetic. Use when creating polished executive briefings, analysis reports, or presentation-style PDF outputs from markdown and HTML via Nutrient DWS.
metadata: {"clawdbot":{"requires":{"bins":["node","npm"]}}}
permissions:
- exec: "Runs the local Node generator to list templates, render preview HTML, and create PDF outputs when the user asks."
- file_read: "Reads bundled templates, themes, examples, and design references inside the skill directory plus user-approved input markdown files."
- file_write: "Writes generated HTML/PDF outputs and user-requested template or theme files inside approved working directories."
- network: "Calls Nutrient DWS and any hosted font assets used by the bundled templates when the user requests report generation."
---
# elegant-reports
Generate minimalist PDF reports inspired by Scandinavian editorial design.
## When to Use
Use this skill when the user wants:
- polished executive briefings or board-style reports
- presentation-like PDFs generated from markdown
- a clean Nordic visual language instead of default developer styling
- a reusable report template system that can be extended carefully
## Quick Start
Install the pinned dependencies from `package-lock.json`, then run:
```bash
cd /path/to/elegant-reports
node ./generate.js --list
node ./generate.js examples/sample-executive.md output.pdf --template executive --theme light
```
For HTML debugging, add `--output-html` so the generator saves the rendered HTML alongside the PDF.
## Available Templates
| Template | Use Case |
|----------|----------|
| `executive` | polished briefings and compact executive summaries |
| `report` | denser narrative reports and analysis writeups |
| `presentation` | bold slide-like outputs with one idea per page |
| `report-demo` | legacy report variant for comparison/testing |
| `presentation-demo` | legacy presentation variant for comparison/testing |
Each template supports `light` and `dark` themes where available.
## Frontmatter
Add YAML frontmatter to control the rendered output:
```markdown
---
title: Q4 Competitive Analysis
subtitle: Market Intelligence Report
author: Report Author
template: report
theme: dark
---
Your content here...
```
## Workflow
1. Pick the closest existing template instead of starting from scratch.
2. Write or refine the source markdown.
3. Generate a PDF.
4. If layout tuning is needed, inspect the emitted HTML with `--output-html` and adjust the corresponding template/theme pair.
5. Re-run until the design is clean and the PDF is stable.
## Extending the Skill
When authoring a new visual variant:
- start from the nearest bundled template and theme
- keep token names and spacing scales consistent with the existing system
- make one visual change at a time and regenerate after each step
- prefer additive variants over rewriting the whole design language
- keep legacy/demo templates available until the replacement is verified
The bundled Nordic design research note is the canonical reference for the visual system. Read it only when you need deeper design rationale.
## Safety Boundaries
- Do not send sensitive source documents to third-party services unless the user explicitly requested PDF generation through Nutrient DWS and accepts that network boundary.
- Do not browse arbitrary local files. Limit reads to the skill bundle and user-approved input/output paths.
- Do not overwrite or delete files outside the user-approved working directory.
- Do not install extra packages, change dependency versions, or add new external services unless the user explicitly asks for that setup work.
- Do not claim a report was generated successfully unless the output artifact exists and the generator completed without error.
- Do not fetch external design inspiration or web references unless the user explicitly wants fresh visual research.
## Dependencies
- Node.js 18+
- pinned npm dependencies from `package-lock.json`
- `NUTRIENT_DWS_API_KEY` environment variable for PDF generation
## File Map
- main generator CLI and module entrypoint
- bundled HTML templates
- bundled visual themes
- sample markdown input
- optional deeper design rationale bundled with the skill
## Validation
Before calling the skill done:
- run `node ./generate.js --list`
- run `npm test`
- verify the expected PDF or HTML artifact exists in the requested output path
© jdrhyne · MIT · jdrhyne/agent-skills