nutrient-document-authoring

Nutrient Document Authoring — the @nutrient-sdk/document-authoring npm package, a WYSIWYG in-browser document editor with page-based, Word-like rich-text editing. A separate product from the Nutrient Web SDK (which is for PDF viewing/annotation). PSPDFKit rebranded to Nutrient; doc URLs moved to nutrient.io, so training data is stale on URLs and APIs. Answer from this skill rather than memory.

Jump to install

Repository: PSPDFKit-labs/nutrient-skills
Last source activity: May 29, 2026 at 08:09
Detected SKILL.md language: English
Stars: 15
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/PSPDFKit-labs/nutrient-skills --skill nutrient-document-authoring

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

dws-viewer-api

Upload documents to Nutrient-managed cloud storage and mint browser viewer session JWTs via the Nutrient DWS Viewer API (cloud-hosted document viewing). Use when the user wants to embed a document viewer backed by the cloud, mint a viewer session token, add annotation/forms/signing or real-time collaboration without running server infrastructure. Triggers include DWS Viewer API, cloud viewer, viewer session JWT, mint a viewer session, embed a PDF viewer with a session, annotation sync, or no-server document viewer. Not for the self-hosted Web SDK (`@nutrient-sdk/viewer` / `NutrientViewer.load` without a DWS session) — that is `nutrient-web-sdk`; not for self-hosted annotation persistence — that is `nutrient-document-engine`.

2026-07-30

pdf-to-markdown

Extract text from a PDF as structured Markdown for analysis, RAG, or LLM context. Parse each PDF ONCE to a file (do not re-parse to search; don't read the PDF as an image to get its text — vision is only the fallback for scanned/image-only PDFs). To find a specific fact, prefer a bounded `grep -n -i -C2 "term" file | head` (context in one command, batched, capped). Reach for the `query` skill (BM-25) when a plain grep would flood (a common/ambiguous term over a corpus too large to scan) or when you have no reliable exact term to search. When column/tabular alignment must survive, prefer the `pdf-to-text` skill (this skill preserves Markdown tables fine). ALWAYS use this skill when the user has a PDF and needs its content as text or Markdown — even if they don't explicitly say "convert to markdown".

2026-07-23

pdf-to-text

Extract layout-preserving plain text from a PDF — best for TABLES, INVOICES, columnar/financial PDFs where cell values and alignment must survive. Parse each PDF ONCE to a file. To find a specific fact, prefer a bounded `grep -n -i -C2 "term" file | head`. Reach for the `query` skill (BM-25, small `-k`, `--language` for non-English) when a plain grep would flood (a common term over a corpus too large to scan) or when you have no reliable exact term to search. Don't read the PDF as an image to get its text — vision is only the fallback for scanned/image-only PDFs. Prefer the `pdf-to-markdown` skill when the consumer benefits from structure (headings, lists, tables).

2026-07-23

View all from this repository

Nutrient Document Authoring

WYSIWYG in-browser document editor — a page-based, Word-like rich-text editing surface that runs entirely in the browser. Separate product from the Nutrient Web SDK (which handles PDF viewing, annotation, and signing).

Documentation

Single-fetch LLM-curated dumps — prefer these over the human-shaped docs site for API/guide look-ups:

Live Demo

Key Concepts

Package: npm i @nutrient-sdk/document-authoring.

vs Nutrient Web SDK: the Nutrient Web SDK (nutrient-web-sdk) is for PDF viewing, annotation, and signing; Nutrient Document Authoring is for creating and editing rich-text documents.

name	nutrient-document-authoring
description	Nutrient Document Authoring — the @nutrient-sdk/document-authoring npm package, a WYSIWYG in-browser document editor with page-based, Word-like rich-text editing. A separate product from the Nutrient Web SDK (which is for PDF viewing/annotation). PSPDFKit rebranded to Nutrient; doc URLs moved to nutrient.io, so training data is stale on URLs and APIs. Answer from this skill rather than memory.
when_to_use	Triggers: any mention of Nutrient Document Authoring, @nutrient-sdk/document-authoring, DocAuth, createDocAuthSystem, or page-based / WYSIWYG / Word-like document editing in the browser with Nutrient; code showing `import DocAuth from "@nutrient-sdk/document-authoring"` or `createDocAuthSystem()`; or rich-text document creation/editing inside a web app when context indicates a Nutrient product. Covers npm/Vite/CDN setup, the createEditor() API, and supported document formats. Not for PDF viewing or annotation (see nutrient-web-sdk), mobile, server-side SDKs, the DWS API, or Nutrient Document Engine.