gembox-skill

**Judgement** This skill is a strong, narrowly focused assistant for projects that already use (or plan to use) GemBox components. It materially improves the quality of GemBox-related coding help by anchoring answers in local XML API docs and official examples, instead of relying on guesswork. **What it does well** - Targets all major GemBox products (Spreadsheet, Document, Pdf, Presentation, Email, Imaging, PdfViewer). - Provides concrete guidance on *how* to look up the exact API (namespaces, types, methods) from NuGet-installed XML docs. - Curates a large list of official example URLs per component, enabling very targeted “do exactly this” solutions. - Promotes compilation-based validation to catch incorrect API usage early. **Key risks / limitations** - Assumes GemBox NuGet packages and XML docs are installed in standard locations; nonstandard environments or missing packages will reduce effectiveness. - The long, hardcoded list of example URLs may become stale as GemBox docs evolve, requiring maintenance to stay fully accurate. - Outside GemBox scenarios (general .NET, unrelated libraries), this skill adds little value and should not be used. - It does not itself execute or test code; correctness still depends on following the documentation and compiling. **Recommended scenarios** - You are building or maintaining .NET applications that use GemBox components for Office/PDF/email/image tasks and want precise API-level help. - You need guidance mapping business requirements (e.g., `convert Excel to PDF`, `fill PDF forms`, `send bulk emails`) to the appropriate GemBox component and sample. - You work in an enterprise or offline environment where you rely on local NuGet + XML docs and want the assistant to navigate them effectively. - You’re migrating from Office Interop or other libraries and need idiomatic GemBox equivalents and patterns.