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".
What this skill does
# Nudocs Upload documents to Nudocs.ai for rich editing, get shareable links, and pull back the results. ## Setup 1. Install the CLI using the repo's declared install metadata or your preferred package manager before first use. 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 `formats.md` in this skill's `references` folder 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 `document-design.md` in this skill's `references` folder 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 (`@nutrient-sdk/nudocs-cli` on npm) - MCP integration repo: https://github.com/PSPDFKit/nudocs-mcp-server - Nudocs: https://nudocs.ai ## Safety Boundaries - Do not upload sensitive documents unless the user confirmed that third-party processing is acceptable. - Do not print API keys, edit links meant to stay private, or document contents the user did not ask to expose. - Do not delete documents from Nudocs without explicit confirmation. - Do not assume the default download format is correct; confirm the output format when it matters.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.