agentsclimarketplace

Nutrient ai assistant

Skill PSPDFKit-labs/nutrient-skills/plugins/nutrient-sdk-dev/skills/nutrient-ai-assistant

AI agent skills for Nutrient APIs and SDKs — works with Claude Code, Codex, Gemini CLI, Cursor, and 35+ more agents

Install
npx -y skills add PSPDFKit-labs/nutrient-skills --skill nutrient-ai-assistant

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.9 KB, as published. Nobody here has run it

Nutrient AI Assistant

In-viewer document-AI feature for Nutrient client SDKs (Web, iOS, Android, React Native) backed by a Docker service. Users chat with the open document for Q&A, summarisation, translation, redaction, and form filling; from Q1 2026 onward an agents layer plans and executes multi-step edits autonomously under policy-defined approval gates.

Documentation

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

Key Concepts

  • Architecture: a Docker container (pspdfkit/ai-assistant, also at public.ecr.aws/pspdfkit/ai-assistant) plus a PostgreSQL database with the pgvector extension, plus credentials for an LLM provider (OpenAI / Azure OpenAI / AWS Bedrock / self-hosted OpenAI-compatible). The legacy pspdfkit/ai-document-assistant image is the pre-rebrand name; new deployments use pspdfkit/ai-assistant.
  • Client integration: existing Nutrient SDKs (Web / iOS / Android / React Native) — nothing extra to install; configure an aiAssistant block (Web) or an AIAssistantConfiguration on PDFConfiguration (iOS / Android / React Native), and add the ai-assistant toolbar item (Web) or aiAssistantButtonItem (mobile).
  • Current names: toolbar item ai-assistant; Web config block aiAssistant. The legacy ai-document-assistant / aiDocumentAssistant keys predate the rebrand — current docs and examples use the new names.
  • Required env vars on the backend: ACTIVATION_KEY, API_AUTH_TOKEN, JWT_PUBLIC_KEY, plus one LLM-provider credential (OPENAI_API_KEY / AZURE_API_KEY / BEDROCK_ACCESS_KEY_ID+BEDROCK_SECRET_ACCESS_KEY).
  • Two-JWT pattern: when the client SDK is paired with Nutrient Document Engine, the browser sends one JWT to the engine (authPayload.jwt) and a different JWT to AI Assistant (aiAssistant.jwt). They're signed with different keys, scoped differently, and shouldn't be reused.
  • Standalone vs paired: AI Assistant does not require Nutrient Document Engine. Standalone (WASM-only Web SDK) and paired (server-backed against Document Engine for collaborative storage, Nutrient Instant) are both first-class.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.