Menü
Edit PDFs with natural-language instructions using the nano-pdf CLI.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | nano-pdf |
| description | Edit PDFs with natural-language instructions using the nano-pdf CLI. |
| homepage | https://github.com/gavrielc/Nano-PDF |
| metadata | {"openclaw":{"emoji":"📄","displayName":"PDF Editing","requires":{"bins":["nano-pdf"]},"install":[{"id":"uv","kind":"uv","package":"nano-pdf","bins":["nano-pdf"],"label":"Install nano-pdf (uv)"}]}} |
Use nano-pdf to apply natural-language edits to existing PDF pages or insert a
new generated page.
GEMINI_API_KEY with Gemini billing enabled.uv tool install nano-pdf when nano-pdf is missing.nano-pdf edit deck.pdf 1 "Change the title to 'Q3 Results' and fix the typo in the subtitle"
nano-pdf edit deck.pdf 1 "Make the title more concise" 5 "Replace the chart caption"
nano-pdf add deck.pdf 0 "Add a title page with a dark background and the title 'Q3 Results'"
nano-pdf add deck.pdf 3 "Insert a summary page after page 3"
--output <path> sets the output PDF path. The default is
edited_<filename>.--style-refs <file-or-dir> passes visual references for style matching.--resolution 4K|2K|1K controls generated-page/edit resolution.--use-context includes neighboring PDF context when editing.--disable-google-search disables Google Search grounding when supported.Notes:
edit page numbers are 1-based.add uses 0 to insert at the beginning; otherwise, the page number is
1-based and inserts after that page.Use when the user asks to use a consumer integration that is not set up yet: WhatsApp as Me, Email, Google Workspace, Apple Notes, Apple Reminders, Telegram as Me, Google Maps Search, or creative audio. Route here only when the right integration exists but is blocked by missing login, OAuth, QR pairing, permissions, local dependency setup, configuration, or API credentials, and the response should guide setup in product language instead of dumping CLI commands.
Use for Google Workspace requests tied to Gmail, Google Calendar, Drive, Docs, Sheets, or Contacts, especially when the user explicitly mentions Google or needs cross-surface Google account access. Prefer this over generic email skills when the task is clearly in the Google ecosystem.
Use when the user asks to triage messages, emails, chats, inboxes, unread messages, recent messages, open replies, who they owe replies to, outreach, or reply drafting across one or more channels such as WhatsApp, Telegram, Gmail/email, Slack, Signal, iMessage, browser portals, or files. For broad sweeps, first produce a scoped prioritized triage list; for one known target, use single-thread draft mode. Always require user approval before any external reply/send.
Use for generic email tasks on connected mail accounts: search, read, summarize, draft, reply, forward, send, and organize email over IMAP/SMTP. This is the better match for normal mailbox work that is not specifically a Gmail or Google Workspace request.
Use for Telegram-as-me requests on this Mac: reading, sending, replying, or waiting as the user's real Telegram account. Do not use it for the normal Telegram bot channel, BotFather setup, or generic bot onboarding.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).