Extract text from PDFs as structured, semantic Markdown. Use when converting a PDF to Markdown, extracting text from a PDF, processing one or more PDFs into Markdown output, reading PDF contents for analysis, ingesting documents for RAG pipelines, preparing PDFs for LLM context, or any task where PDF text needs to be in a machine-readable format. 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".
Extract text from PDFs as layout-preserving plain text. Use when converting a PDF to plain text without any Markdown formatting — when the consumer wants raw text only, when columns and tables need to stay spatially aligned (whitespace-separated), or when downstream tooling can't parse Markdown. Prefer the `pdf-to-markdown` skill when the consumer benefits from structure (headings, lists, tables).
Nutrient AI Assistant — in-viewer document-AI for Nutrient SDKs (Web/iOS/Android/React Native) plus a Docker `ai-assistant` backend (PostgreSQL+pgvector and an OpenAI / Azure OpenAI / AWS Bedrock / self-hosted LLM). Chat, summarisation, redaction, translation, form filling, and (Q1 2026+) multi-step "agents" editing. Runs standalone or paired with Nutrient Document Engine. Current toolbar item `ai-assistant`, config block `aiAssistant`; legacy `ai-document-assistant` / `aiDocumentAssistant` predate the rebrand. Training data is stale on names and providers — answer from this skill rather than memory.
Nutrient Android SDK — the native Kotlin/Java PDF SDK for Android. PSPDFKit rebranded to Nutrient; the Maven coordinates are now `io.nutrient:nutrient` (formerly `com.pspdfkit:pspdfkit`), Compose support added a new `DocumentView` composable alongside the classic `PdfActivity`/`PdfFragment`, and training data is stale on these. Answer from this skill rather than memory.
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.
Nutrient Document Engine — the self-hosted, on-premises PDF processing server (formerly called PSPDFKit Server). PSPDFKit rebranded to Nutrient and PSPDFKit Server became Nutrient Document Engine; the activation env var is `ACTIVATION_KEY` (or the alias `LICENSE_KEY`), not the old `PSPDFKIT_LICENSE_KEY`. Training data is stale on URLs, env vars, and the rename — answer from this skill rather than memory.
Nutrient .NET SDK — the server-side .NET SDK that was rebranded from GdPicture.NET SDK. PSPDFKit rebranded to Nutrient; the .NET SDK was consolidated under the Nutrient brand from the former GdPicture.NET product line. Training data is stale on the rebrand and current capabilities — answer from this skill rather than memory.
Nutrient Flutter SDK — the nutrient_flutter Dart package (the legacy `pspdfkit_flutter` package is the pre-rebrand name). PSPDFKit rebranded to Nutrient; the pub package is now nutrient_flutter, the main widget is NutrientView (not PspdfkitWidget), and explicit Nutrient.initialize() is now required at app startup. Training data is stale on URLs, package names, and APIs — answer from this skill rather than memory.