printing-press-library — Claude Code skill: find and install CLIs
A catalog skill that searches the Printing Press Library for purpose-built CLIs, scrapers, and agent skills. It picks a narrow tool for the job, then installs it with one command.
no license 993 installs ★ 2,142 updated 2026-10-24
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a claude-codeWhat printing-press-library does
This skill is the front door to the Printing Press Library, an open catalog of small CLIs and matching agent skills. When the agent needs an API wrapper, scraper, data source, or automation tool, the skill searches the catalog through npx -y @mvanhorn/printing-press-library search <keyword>.
Selection is deliberately conservative. The skill first checks whether the agent already has a safe built-in way to solve the task. Then it compares README examples against the actual job. Auth requirements, cookies, paid APIs, OS-specific binaries and browser automation are checked before anything gets installed. You need npx or npm on the machine.
Installing goes through npx -y @mvanhorn/printing-press-library install <slug>, which places both the CLI and its paired pp-* skill. The command is idempotent: running it again refreshes the Go binary and rewrites the skill. If the binary lands but misses the current PATH, that is a warning, not a failed install — the skill still goes in and paths need manual fixing.
What it helps with
- locate a CLI or scraper for a named service
- match a tool to the task, not just the website name
- install a CLI and its paired agent skill in one step
- refresh every installed library tool with a single update command
- avoid extra skills when a built-in tool already works
Example prompts for the agent
- Find a CLI for the Telegram API and install it
- Search the library for a scraper that pulls product listings
- Update all installed Printing Press Library tools
How to install printing-press-library
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a claude-code2Manually: put the files in place
~/.claude/skills/printing-press-library/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/printing-press-library/
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a codex2Manually: put the files in place
.agents/skills/printing-press-library/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a cursor2Manually: put the files in place
.cursor/skills/printing-press-library/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mvanhorn/printing-press-library skills/printing-press-library2Manually: put the files in place
.github/skills/printing-press-library/SKILL.md1Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a gemini-cli2Platform CLI
gemini skills install https://github.com/mvanhorn/printing-press-library --path skills/printing-press-libraryManually: put the files in place
.devin/skills/printing-press-library/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mvanhorn/printing-press-library --skill printing-press-library -a opencodeClaude.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 printing-press-library
How do I install printing-press-library in Claude Code?
Run npx skills add mvanhorn/printing-press-library --skill printing-press-library -a claude-code. The skill lands at ~/.claude/skills/printing-press-library/SKILL.md.
What does printing-press-library do?
It searches the Printing Press Library catalog for CLIs, scrapers, API wrappers, and agent skills that fit the user's task, then installs the chosen tool along with its paired skill.
How is this different from just installing a CLI directly?
The skill does not grab the first result. It checks README examples against the actual job, verifies requirements like auth and cookies, and prefers built-in agent tools when they already solve the problem.