nutrient-document-engine
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.
What this skill does
# Nutrient Document Engine Self-hosted, on-premises document processing server. Provides the same core operations as Nutrient DWS but runs in the user's own infrastructure. Also backs the Nutrient Web SDK's server-backed mode — handling persistent annotation storage and Nutrient Instant real-time collaboration. ## Documentation Single-fetch LLM-curated dumps — prefer these over the human-shaped docs site for API/guide look-ups: - Guides: https://www.nutrient.io/guides/document-engine/llms.txt - Cross-product index (other Nutrient SDKs): https://www.nutrient.io/llms.txt ## Example Repositories - Node.js + Docker Compose (Nutrient Document Engine + Nutrient Web SDK): https://github.com/PSPDFKit/pspdfkit-server-example-nodejs - Rails + Docker Compose (Nutrient Document Engine + Nutrient Web SDK): https://github.com/PSPDFKit/pspdfkit-server-example-rails - Web examples catalog with Nutrient Document Engine (dashboard at localhost:5000): https://github.com/PSPDFKit/pspdfkit-web-examples-catalog - MCP server exposing Nutrient Document Engine capabilities to AI agents: https://github.com/PSPDFKit/nutrient-document-engine-mcp-server ## Key Concepts - **Docker image**: `pspdfkit/document-engine` on Docker Hub. - **License activation**: set `ACTIVATION_KEY` (or the alias `LICENSE_KEY` — either works). The pre-rebrand `PSPDFKIT_LICENSE_KEY` is **not** the current name; the engine fails on startup with "No `ACTIVATION_KEY` or `LICENSE_KEY` set" if missing. - **Nutrient Instant**: real-time collaboration backbone shared across the Nutrient client SDKs (Web, iOS, Android, React Native, Flutter). Enable in Document Engine config and point the client at the engine URL. - **Document Engine vs Nutrient DWS**: Document Engine runs on the user's infrastructure (no data leaves the environment); Nutrient DWS is Nutrient's hosted cloud service. Use Document Engine when data residency or offline operation is required.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.