| name | nudocs |
| description | Upload, edit, and export documents via Nudocs.ai. Use when creating shareable document links for collaborative editing, uploading markdown/docs to Nudocs for rich editing, or pulling back edited content. Triggers on "send to nudocs", "upload to nudocs", "edit in nudocs", "pull from nudocs", "get the nudocs link", "show my nudocs documents". |
| metadata | {"openclaw":{"emoji":"📄","requires":{"bins":"[Truncated]"},"install":["[Truncated]"]}} |
Nudocs
Use the authenticated Nudocs CLI to upload documents for hosted editing, retrieve private edit links, list or export documents, and delete a specific remote document.
Setup without exposing credentials
Inspect nudocs --help and nudocs config --help before setup because authentication UX can change by version.
Use one authentication method, not both:
- Interactive personal setup: if the current CLI exposes an interactive login/config flow, complete it in the user's terminal. Otherwise have the user enter the key directly in a protected local editor or secret manager, outside the agent transcript. Keep
~/.config/nudocs mode 0700 and its API-key file mode 0600.
- Protected environment setup: use
NUDOCS_API_KEY only when it is already supplied through protected local or CI secret storage.
Never ask the user to paste the key into chat, put it in a command argument, echo it into a file, display it with nudocs config, or print environment/config contents. Verify authentication through behavior such as a bounded nudocs list, not by inspecting the secret.