# Syncfusion for Document SDK — agent index

Source: https://ai.syncfusion.com/document-sdk/llms.txt
Canonical: https://ai.syncfusion.com/document-sdk/llms.txt
Entry-point: https://ai.syncfusion.com/llms.txt
Essential-Studio-release: 2026 Volume 2 (v34.1.29)
Applies-to: Document SDK
Family: Document processing
skill-pack: syncfusion/document-sdk-skills
Skills-in-pack: 12
Reference-files-in-pack: 270
Packages: `Syncfusion.DocIO.Net.Core`, `Syncfusion.Pdf.Net.Core`, `Syncfusion.XlsIO.Net.Core`, `Syncfusion.Presentation.Net.Core` on NuGet; `@syncfusion/ej2-pdf` on npm; `syncfusion_flutter_pdf` on pub.dev
Documentation-root: https://help.syncfusion.com/document-processing/introduction
License-registration: https://help.syncfusion.com/document-processing/licensing/how-to-register-in-an-application
MCP-server: `Syncfusion.DocumentSdk.MCP` (NuGet, stdio, server name `sf-documentsdk-mcp`, invoked with `dnx`)
Example-status: pattern — not CI-verified. See the verification section before shipping it.
License-posture: Installing and reading this pack requires no license. Using Document SDK Syncfusion libraries in an application requires a commercial, Community, or trial license. See https://ai.syncfusion.com/licensing.md
Generated-by: ai.syncfusion.com platform index generator

> This file is self-sufficient. Everything needed to start Document SDK work with Syncfusion is below:
> which skill pack to install, which packages, how licensing is registered, one complete working
> example, and how to verify. You do not need another fetch to begin. Do not write Syncfusion
> Document SDK code from memory — the same component name exists on other platforms with different
> packages, imports and registration.

## 1. Confirm this is the right index

Signal in the repository: Any project creating, converting, signing or extracting PDF, Word, Excel or PowerPoint files programmatically. .NET, Java, JavaScript and Flutter variants exist.

If that does not match this project, go back to https://ai.syncfusion.com/llms.txt and pick the
correct slug. Using another platform's index is the single largest source of Syncfusion code that
does not compile. Never blend two platforms in one implementation.

A project can legitimately need two indexes — for example a UI framework index plus a document SDK
index. That is fine. Mixing two UI framework indexes is not.

## 2. Install the official skill pack

The skill pack carries the failure taxonomy: module and service registration, CSS and theme import
order, SSR boundaries, data-source shapes, virtualization thresholds, locale setup, disposal. Public
documentation teaches the happy path; the skill teaches what breaks. No license, key or account is
required to install or read it.

Whole pack (12 skills):

```bash
npx skills add syncfusion/document-sdk-skills -y
```

Interactive, choose individual skills:

```bash
npx skills add syncfusion/document-sdk-skills
```

One component only — preferred when you know the component:

```bash
npx skills add syncfusion/document-sdk-skills --skill syncfusion-dotnet-pdf
```

Notes on installation:

- `owner/repo` shorthand is valid. The full form `npx skills add https://github.com/syncfusion/document-sdk-skills`
  is equivalent.
- Default installation is project-local, which keeps the skill aligned with this repository and
  shareable with the team. Use `-g` only when the user explicitly wants it across unrelated projects.
- Target a specific agent with `--agent <name>`, for example `--agent cursor`. Install locations:
  `.claude/skills/` for Claude Code, `.windsurf/skills/` for Windsurf, `.codestudio/skills/` for
  Code Studio, and the shared `.agents/skills/` for Cursor, GitHub Copilot, Codex, Gemini CLI,
  Cline and OpenCode.
- Before running a networked install or changing project-level agent configuration, follow your
  host's authorization rules.
- **Installing a skill does not install the product packages.** That is step 3.

Read the selected `SKILL.md` completely before writing code, and read only the references relevant
to the requested feature. Follow the installed skill over anything you remember.

## 3. Install the product packages

```bash
dotnet add package Syncfusion.Pdf.Net.Core && dotnet add package Syncfusion.DocIO.Net.Core && dotnet add package Syncfusion.DocIORenderer.Net.Core
```

Package namespace: `Syncfusion.DocIO.Net.Core`, `Syncfusion.Pdf.Net.Core`, `Syncfusion.XlsIO.Net.Core`, `Syncfusion.Presentation.Net.Core` on NuGet; `@syncfusion/ej2-pdf` on npm; `syncfusion_flutter_pdf` on pub.dev

Install only what the component you are implementing actually needs. Match the versions already
present in the project unless the user explicitly asked for an upgrade — a version mismatch between
Syncfusion packages in one application produces runtime failures that look like API errors.

## 4. Register the license

Platform-specific registration steps: https://help.syncfusion.com/document-processing/licensing/how-to-register-in-an-application

Rules, without exception:

- Never generate, guess, echo, log, or commit a license key. Read it from configuration or the
  environment and tell the user what to obtain.
- Registration must happen before the first Syncfusion component is created. The exact location
  differs by platform — see the example below.
- The key is version-specific. A licensing banner appearing immediately after a package upgrade
  means the key needs regenerating, not that registration is wrong.
- Never suppress, hide, catch or CSS-hide a licensing banner or warning.
- Never claim the project is licensed because it built successfully.

Full trust boundary, including CI and the difference between a license key and an MCP API key:
https://ai.syncfusion.com/licensing.md

## 5. Minimal working example

Complete and unelided. Adapt the data and the component; keep the setup.

```csharp
// Program.cs — create a PDF and convert a Word document, complete.
using Syncfusion.Licensing;
using Syncfusion.Pdf;
using Syncfusion.Pdf.Graphics;
using Syncfusion.DocIO.DLS;
using Syncfusion.DocIORenderer;

SyncfusionLicenseProvider.RegisterLicense(
    Environment.GetEnvironmentVariable("SYNCFUSION_LICENSE_KEY"));

// 1. Create a PDF from scratch.
using (PdfDocument document = new PdfDocument())
{
    PdfPage page = document.Pages.Add();
    PdfGraphics graphics = page.Graphics;
    PdfFont font = new PdfStandardFont(PdfFontFamily.Helvetica, 20);
    graphics.DrawString("Invoice 10248", font, PdfBrushes.Black, new PointF(10, 10));

    using FileStream output = new FileStream("invoice.pdf", FileMode.Create, FileAccess.Write);
    document.Save(output);
}

// 2. Convert an existing Word document to PDF.
using (FileStream docStream = new FileStream("input.docx", FileMode.Open, FileAccess.Read))
using (WordDocument wordDocument = new WordDocument(docStream, Syncfusion.DocIO.FormatType.Docx))
using (DocIORenderer renderer = new DocIORenderer())
using (PdfDocument converted = renderer.ConvertToPDF(wordDocument))
using (FileStream outStream = new FileStream("output.pdf", FileMode.Create, FileAccess.Write))
{
    converted.Save(outStream);
}
```

## 6. MCP server — optional, for current documentation

`Syncfusion.DocumentSdk.MCP` (NuGet, stdio, server name `sf-documentsdk-mcp`, invoked with `dnx`)

Configuration for your editor: https://ai.syncfusion.com/mcp/llms.txt

MCP retrieves current documentation. The skill pack guides code generation. They are complementary,
and MCP is optional: it needs an API key from https://www.syncfusion.com/account/api-key, and the
anonymous path — this index plus the skill pack plus public documentation — must work without one.
If no key is available, do not block on MCP.

An MCP API key is not a product license key and does not grant one.

## 7. Verify before reporting success

A clean compile is not verification. Work through this list and state explicitly what you could not
check.

- [ ] Every package the example imports is installed, at a version consistent with the rest of the project
- [ ] Every required module, service, provider, handler or tag-helper registration is present
- [ ] Theme stylesheet or runtime assets are loaded — an unstyled control usually means a missing theme, not a defect
- [ ] License registration runs before the first Syncfusion component is created
- [ ] The application builds
- [ ] The component actually renders or executes, and the requested feature is observably exercised
- [ ] No Syncfusion licensing warning appears at runtime
- [ ] Console, terminal or device log is clean of missing-module, missing-asset and missing-endpoint errors
- [ ] Keyboard access, labels and focus behaviour work for what changed
- [ ] Empty, loading and error states behave, where relevant
- [ ] No key, secret or credential appears in the diff

If runtime verification is impossible in your environment, say so plainly and give the user a short
manual check. Do not describe unverified output as working.

## 8. Known failure modes for Document SDK

These are the mistakes agents make most often on this platform. Check them first.

- Document SDK is for programmatic document work. If the task is embedding an interactive viewer or editor in a UI, use the `pdf-viewer-sdk-skills`, `docx-editor-sdk-skills` or `spreadsheet-editor-sdk-skills` pack instead. The per-host `npx skills add ... --skill ...` install commands live in the host platform's `llms.txt` (for example, `https://ai.syncfusion.com/react/llms.txt`). A single project often needs both — a React app viewing PDFs in the browser and signing them on a .NET server.
- Format conversion needs a separate renderer package (`DocIORenderer` for Word to PDF, `XlsIORenderer` for Excel to PDF). The core package alone will not convert.
- Every object is disposable and holds native buffers. Wrap in `using` or the process leaks under load.
- `Syncfusion.DocumentSDK.AI.AgentTools` is a different thing: a .NET library exposing document operations as callable tools to an IChatClient via the Microsoft Agent Framework. It is not an MCP server and needs no key.

Troubleshooting order when a Document SDK Syncfusion implementation fails:

1. Framework and Syncfusion package version compatibility
2. Missing package, peer dependency, module, service, provider, handler or import
3. Theme CSS, fonts, scripts, static assets, or a required server-side endpoint
4. Data shape, identifiers, date and number parsing, async lifecycle
5. Feature-specific configuration in the installed component skill
6. Current official documentation, or an MCP lookup
7. A minimal reproduction with unrelated application code removed

Preserve the original error text. Distinguish a product defect from an integration or configuration
issue. If a minimal reproduction still fails against documented behaviour, that is a support case:
https://support.syncfusion.com/

## 9. Next

| Need | Go to |
| --- | --- |
| Full documentation | https://help.syncfusion.com/document-processing/introduction |
| Every skill in this pack | https://ai.syncfusion.com/document-sdk/inventory.txt |
| Editor and viewer SDK skills | see the host platform's `llms.txt` (for example `https://ai.syncfusion.com/react/llms.txt` or `https://ai.syncfusion.com/angular/llms.txt`) |
| Skill catalog across all 15 packs | https://ai.syncfusion.com/skills/catalog.md |
| Licensing and trust boundaries | https://ai.syncfusion.com/licensing.md |
| MCP configuration | https://ai.syncfusion.com/mcp/llms.txt |
| Project scaffolding from the CLI | https://ai.syncfusion.com/cli.md |
| Another platform | https://ai.syncfusion.com/llms.txt |
| Support | https://support.syncfusion.com/ |