nano-pdf
Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).
- License 许可
- MIT
- 所属仓库
- ZDStudios/AIOS
- 最近更新
- 2026-10-06
- Stars
- ★ 7
- Forks
- 1
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/" } }
- platforms
- [ "linux", "macos", "windows" ]
- description
- Edit PDF text/typos/titles via nano-pdf CLI (NL prompts).
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
ruflo
Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
ponytail
Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.
ponytail-review
Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.
ponytail-help
Quick reference for ponytail's modes, skills, and commands. One-shot display.
ponytail-gain
Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.