home / skills / openclaw / skills / nudocs

nudocs skill

/skills/jdrhyne/nudocs

This skill helps you manage Nudocs documents by uploading, editing, and exporting shareable links for collaborative work.

npx playbooks add skill openclaw/skills --skill nudocs

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
4.3 KB
---
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".
homepage: https://nudocs.ai
metadata:
  {
    "openclaw":
      {
        "emoji": "📄",
        "requires":
          {
            "bins": ["nudocs"],
            "env": ["NUDOCS_API_KEY"],
            "config": ["~/.config/nudocs/api_key"],
          },
        "install":
          [
            {
              "id": "npm",
              "kind": "node",
              "package": "@nutrient-sdk/nudocs-cli",
              "repo": "https://github.com/PSPDFKit/nudocs-cli",
              "bins": ["nudocs"],
              "label": "Install Nudocs CLI (npm)",
            },
          ],
      },
  }
---

# 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 (`@nutrient-sdk/nudocs-cli` on npm)
- MCP Server: https://github.com/PSPDFKit/nudocs-mcp-server
- Nudocs: https://nudocs.ai

Overview

This skill connects to Nudocs.ai to upload, edit, and export documents from an agent flow. It automates creating shareable edit links, listing stored documents, and pulling edited content back in a chosen format. Use voice or text triggers like "send to nudocs" or "pull from nudocs" to activate the flow.

How this skill works

The skill uses the Nudocs CLI and API key to upload files, receive a shareable editing URL, and list or fetch documents by ULID. For uploads it posts the provided file (markdown, docx, etc.) and returns the edit link. For pulls it downloads the edited document in the requested format (docx, md, pdf) so the agent can present or store the updated content.

When to use it

  • Create a collaborative, shareable editing link for a draft or document
  • Move markdown or docs into Nudocs for rich WYSIWYG editing and media additions
  • Fetch the edited document after collaborators finish changes
  • List or manage stored documents and their ULIDs for reference
  • Export final content in docx or pdf for distribution or publishing

Best practices

  • Provide a well-structured markdown file (clear H1/H2/H3 and short paragraphs) before upload
  • Choose output format based on use: docx for rich edits, md for simple text, pdf for final delivery
  • Store the returned ULID or link so you can reliably pull edited versions later
  • Ensure NUDOCS_API_KEY is configured as env var or in ~/.config/nudocs/api_key to avoid auth errors

Example use cases

  • Write a blog draft, upload it with "send to nudocs", share the edit link with an editor, then pull the polished doc as docx
  • Upload meeting notes in markdown for teammates to add action items and images, then download the updated notes
  • Archive a generated report by exporting a PDF after collaborators finalize layout in Nudocs
  • List stored documents to find a ULID and get the corresponding shareable link for review

FAQ

What credential setup is required?

Set NUDOCS_API_KEY as an environment variable or place the key in ~/.config/nudocs/api_key. The skill will fail if no valid key is found.

Which format should I pull for rich edits?

Use docx for rich formatting and images, md for plain text or code, and pdf for final shareable output.