Skill

export-resource-list-pdf

Use when the user wants to render an existing resource list to a PDF for sharing/archiving. Triggers — "export the <topic> list as PDF", "PDF of this resource list", "make a printable version of the eval list".

npx claudepluginhub danielrosehill/claude-code-plugins --plugin resource-list-builder

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Render the README of a resource list into a PDF using Typst (Daniel's preferred tooling).

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Stars0

Forks0

Last CommitApr 24, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Export Resource List to PDF

Render the README of a resource list into a PDF using Typst (Daniel's preferred tooling).

Procedure

Resolve the source. Default to the README of the list repo passed by the user.

Strip dynamic shields.io badges from the markdown copy used for rendering — they don't paginate well in print and the star counts are stale by the time the PDF is opened. Keep the bracketed link to the repo.

Convert to Typst input via the workspace's standard pipeline:

If the typst skill is available, hand off to it with a resource-list template.
Otherwise, render via pandoc <input>.md -o <output>.pdf --pdf-engine=typst (preferred) or --pdf-engine=tectonic as fallback.

Write the PDF to outputs/<list-name>-<YYYY-MM-DD>.pdf inside the list repo (create outputs/ if missing). Or honour an explicit path from the user.

Optionally upload to Google Drive via the save-to-gdrive skill if the user asks.

Report the output path and page count.

Notes

This is an export, not a snapshot of live data. Mention in the PDF footer: "Snapshot taken YYYY-MM-DD — star counts and project status may have changed since."

For very long lists (>200 entries), enable a 2-column layout in the Typst template to keep page count reasonable.

Don't commit the PDF unless the user asks — these are typically ephemeral.

Export Resource List to PDF

Render the README of a resource list into a PDF using Typst (Daniel's preferred tooling).

Procedure

Resolve the source. Default to the README of the list repo passed by the user.
Strip dynamic shields.io badges from the markdown copy used for rendering — they don't paginate well in print and the star counts are stale by the time the PDF is opened. Keep the bracketed link to the repo.
Convert to Typst input via the workspace's standard pipeline:
- If the typst skill is available, hand off to it with a resource-list template.
- Otherwise, render via pandoc <input>.md -o <output>.pdf --pdf-engine=typst (preferred) or --pdf-engine=tectonic as fallback.
Write the PDF to outputs/<list-name>-<YYYY-MM-DD>.pdf inside the list repo (create outputs/ if missing). Or honour an explicit path from the user.
Optionally upload to Google Drive via the save-to-gdrive skill if the user asks.
Report the output path and page count.

Notes

This is an export, not a snapshot of live data. Mention in the PDF footer: "Snapshot taken YYYY-MM-DD — star counts and project status may have changed since."
For very long lists (>200 entries), enable a 2-column layout in the Typst template to keep page count reasonable.
Don't commit the PDF unless the user asks — these are typically ephemeral.