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".

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 1.8k · 2 current installs · 4 all-time installs
byJonathan Rhyne@jdrhyne
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (upload/edit/export via Nudocs.ai) match the declared dependencies: a 'nudocs' CLI binary, an NUDOCS_API_KEY environment variable, and a Nudocs config file path. The npm package cited (@nutrient-sdk/nudocs-cli) and GitHub repo correspond to the CLI.
Instruction Scope
SKILL.md instructs only CLI actions (upload, list, link, pull, delete, config) and how to supply an API key. It does not ask for unrelated files, system credentials, or hidden network endpoints; it only reads/writes the expected document files and the configured Nudocs API key.
Install Mechanism
Installation uses a public npm package (@nutrient-sdk/nudocs-cli) which is a reasonable delivery for a CLI. npm packages can run install-time scripts, so verify the package source/maintainer and prefer installing from a reviewed publisher or pinned version. The provided GitHub repo points to PSPDFKit/nudocs-cli, which aligns with the package metadata.
Credentials
The single required secret (NUDOCS_API_KEY) and a single user config file (~/.config/nudocs/api_key) are proportional to a service-integration skill. No unrelated credentials or broad system secrets are requested.
Persistence & Privilege
The skill does not request 'always: true' or any elevated persistent presence. It installs a CLI binary (nudocs) into the environment when the npm package is installed, which is expected for a CLI-based integration and does not modify other skills or system-wide agent settings.
Assessment
This skill looks internally consistent, but take these practical precautions before installing: 1) Verify the npm package and GitHub repo (publisher, recent commits, issues) match the official Nudocs/PSPDFKit sources and pin a specific version. 2) Treat NUDOCS_API_KEY like any API secret—provide the minimum-privilege key, store it in your secrets manager, and rotate if needed. 3) Remember global npm installs can run arbitrary code at install time—review package install scripts if you will run npm install -g. 4) Consider installing and testing the CLI in an isolated environment (container or VM) first. 5) The agent can invoke this skill autonomously (platform default); if you want to limit that, control agent invocation settings in your platform rather than relying on the skill. If you need higher assurance, ask the skill author for a checksum or signed release or review the CLI source before installing.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.2.0
Download zip
latestvk97dyjsa0kd3h61zdzcgybhz79813250

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📄 Clawdis
Binsnudocs
EnvNUDOCS_API_KEY
Config~/.config/nudocs/api_key

Install

Install Nudocs CLI (npm)
Bins: nudocs
npm i -g @nutrient-sdk/nudocs-cli

SKILL.md

Nudocs

Upload documents to Nudocs.ai for rich editing, get shareable links, and pull back the results.

Setup

  1. Install the CLI:
npm install -g @nutrient-sdk/nudocs-cli
  1. Get your API key from https://nudocs.ai (click "Integration" after signing in)

  2. Configure the key:

# 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

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

ScenarioRecommended Format
User edited with rich formattingdocx (default)
Simple text/code contentmd
Final delivery/sharingpdf

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

ErrorCauseSolution
"No API key found"Missing credentialsSet 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 keyRegenerate key in Nudocs settings
"No ULID provided"Missing document IDSpecify ULID or upload a doc first

Links

Files

3 total
Select a file
Select a file to preview.

Comments

Loading comments…