nano-pdf
Edit PDFs with natural-language instructions using the nano-pdf CLI. Modify text, fix typos, update titles, and make content changes to specific pages without manual editing.
- License 许可
- MIT
- 最近更新
- 2026-05-24
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- nano-pdf
- author
- community
- license
- MIT
- version
- 1.0.0
- metadata
- { "hermes": { "tags": [ "PDF", "Documents", "Editing", "NLP", "Productivity" ], "homepage": "https://pypi.org/project/nano-pdf/" } }
- description
- Edit PDFs with natural-language instructions using the nano-pdf CLI. Modify text, fix typos, update titles, and make content changes to specific pages without manual editing.
03 SKILL.md 正文
nano-pdf
Edit PDFs using natural-language instructions. Point it at a page and describe what to change.
Prerequisites
# Install with uv (recommended — already available in Hermes)
uv pip install nano-pdf
# Or with pip
pip install nano-pdf
Usage
nano-pdf edit <file.pdf> <page_number> "<instruction>"
Examples
# Change a title on page 1
nano-pdf edit deck.pdf 1 "Change the title to 'Q3 Results' and fix the typo in the subtitle"
# Update a date on a specific page
nano-pdf edit report.pdf 3 "Update the date from January to February 2026"
# Fix content
nano-pdf edit contract.pdf 2 "Change the client name from 'Acme Corp' to 'Acme Industries'"
Notes
- Page numbers may be 0-based or 1-based depending on version — if the edit hits the wrong page, retry with ±1
- Always verify the output PDF after editing (use
read_fileto check file size, or open it) - The tool uses an LLM under the hood — requires an API key (check
nano-pdf --helpfor config) - Works well for text changes; complex layout modifications may need a different approach
04 同仓库更多 Skills
writing-plans
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
subagent-driven-development
Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).
requesting-code-review
Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.
plan
Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.