nudocs
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".
Best use case
nudocs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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".
Teams using nudocs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nudocs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How nudocs Compares
| Feature / Agent | nudocs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Nudocs Upload documents to Nudocs.ai for rich editing, get shareable links, and pull back the results. ## Setup 1. Install the CLI: ```bash npm install -g @nutrient-sdk/nudocs-cli ``` 2. Get your API key from https://nudocs.ai (click "Integration" after signing in) 3. Configure the key: ```bash # Option 1: Environment variable export NUDOCS_API_KEY="nudocs_your_key_here" # Option 2: Config file mkdir -p ~/.config/nudocs echo "nudocs_your_key_here" > ~/.config/nudocs/api_key ``` ## Commands ```bash nudocs upload <file> # Upload and get edit link nudocs list # List all documents nudocs link [ulid] # Get edit link (last upload if no ULID) nudocs pull [ulid] [--format fmt] # Download document (default: docx) nudocs delete <ulid> # Delete a document nudocs config # Show configuration ``` ## Workflow ### Upload Flow 1. Create/write document content 2. Save as markdown (or other supported format) 3. Run: `nudocs upload <file>` 4. Share the returned edit link with user ### Pull Flow 1. User requests document back 2. Run: `nudocs pull [ulid] --format <fmt>` 3. Read and present the downloaded file ### Format Selection | Scenario | Recommended Format | |----------|-------------------| | User edited with rich formatting | `docx` (default) | | Simple text/code content | `md` | | Final delivery/sharing | `pdf` | See `references/formats.md` for full format support. ## Natural Language Triggers Recognize these user intents: **Upload/Send:** - "send to nudocs" - "upload to nudocs" - "open in nudocs" - "edit this in nudocs" - "let me edit this in nudocs" - "put this in nudocs" **Pull/Fetch:** - "pull it back" - "pull from nudocs" - "get that doc" - "fetch from nudocs" - "download from nudocs" - "grab the updated version" - "what did I change" - "get my edits" **Link:** - "get the nudocs link" - "share link" - "where's that doc" - "nudocs url" **List:** - "show my nudocs" - "list my documents" - "what docs do I have" - "my nudocs documents" ## Document Best Practices Before uploading, ensure good structure: - Clear heading hierarchy (H1 → H2 → H3) - Consistent spacing - Appropriate list formatting - Concise paragraphs (3-5 sentences) See `references/document-design.md` for templates and guidelines. ## Example Session ``` User: Write me a blog post about remote work and send it to Nudocs Agent: 1. Writes blog-remote-work.md with proper structure 2. Runs: nudocs upload blog-remote-work.md 3. Returns: "Here's your Nudocs link: https://nudocs.ai/file/01ABC..." User: *edits in Nudocs, adds formatting, images* User: Pull that back Agent: 1. Runs: nudocs pull --format docx 2. Reads the downloaded file 3. Returns: "Got your updated document! Here's what changed..." ``` ## Error Handling | Error | Cause | Solution | |-------|-------|----------| | "No API key found" | Missing credentials | Set NUDOCS_API_KEY or create config file | | "DOCUMENT_LIMIT_REACHED" | Free tier limit (10 docs) | Delete old docs or upgrade to Pro | | "Unauthorized" | Invalid API key | Regenerate key in Nudocs settings | | "No ULID provided" | Missing document ID | Specify ULID or upload a doc first | ## Links - CLI: https://github.com/PSPDFKit/nudocs-cli - MCP Server: https://github.com/PSPDFKit/nudocs-mcp-server - Nudocs: https://nudocs.ai
Related Skills
portfolio-watcher
Monitor stock/crypto holdings, get price alerts, track portfolio performance
portainer
Control Docker containers and stacks via Portainer API. List containers, start/stop/restart, view logs, and redeploy stacks from git.
portable-tools
Build cross-device tools without hardcoding paths or account names
polymarket
Trade prediction markets on Polymarket. Analyze odds, place bets, track positions, automate alerts, and maximize returns from event outcomes. Covers sports, politics, entertainment, and more.
polymarket-traiding-bot
No description provided.
polymarket-analysis
Analyze Polymarket prediction markets for trading edges. Pair Cost arbitrage, whale tracking, sentiment analysis, momentum signals, user profile tracking. No execution.
polymarket-agent
Autonomous prediction market agent - analyzes markets, researches news, and identifies trading opportunities
polymarket-5
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-4
Query Polymarket prediction markets. Use for questions about prediction markets, betting odds, market prices, event probabilities, or when user asks about Polymarket data.
polymarket-3
Query Polymarket prediction market odds and events via CLI. Search for markets, get current prices, list events by category. Supports sports betting (NFL, NBA, soccer/EPL, Champions League), politics, crypto, elections, geopolitics. Real money markets = more accurate than polls. No API key required. Use when asked about odds, probabilities, predictions, or "what are the chances of X".
polymarket-2
Query Polymarket prediction markets - check odds, trending markets, search events, track prices.
pollinations
Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images, videos, audio, vision/analysis, transcription) or mentions Pollinations. Supports 25+ models (OpenAI, Claude, Gemini, Flux, Veo, etc.) with OpenAI-compatible chat endpoint and specialized generation endpoints.