Coding assistance for [GemBox components](https://www.gemboxsoftware.com/). Use when users ask about any GemBox component or coding task that can be performed with a GemBox component. This includes GemBox.Spreadsheet (.NET read/write Excel files), GemBox.Document (.NET read/write Word files), GemBox.Pdf (.NET read/write PDF files), GemBox.Presentation (.NET read/write PowerPoint files), GemBox.Email (.NET read/write email files, send/receive emails), GemBox.Imaging (.NET read/write image files), and GemBox.PdfViewer (JavaScript display/print/save PDF files).
84
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the GemBox ecosystem and provides comprehensive coverage of all seven components with specific file operations. The explicit 'Use when' clause and brand-specific terminology make it highly functional for skill selection. Minor weakness is potential overlap with generic document/file handling skills when users don't mention 'GemBox' explicitly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions across seven distinct components, including 'read/write Excel files', 'read/write Word files', 'display/print/save PDF files', and 'send/receive emails' - all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Coding assistance for GemBox components' with detailed component list) and when ('Use when users ask about any GemBox component or coding task that can be performed with a GemBox component') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'GemBox', 'Excel files', 'Word files', 'PDF files', 'PowerPoint files', 'email files', 'image files', plus .NET and JavaScript context. Users asking about these file types or the GemBox brand would naturally match. | 3 / 3 |
Distinctiveness Conflict Risk | While 'GemBox' is a distinct brand trigger, the file type mentions (Excel, Word, PDF, PowerPoint) could overlap with generic file handling skills. The .NET/.JavaScript context helps but doesn't fully eliminate conflict risk with other document processing skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionable guidance with clear CLI commands, search patterns, and a logical workflow including validation. However, it severely violates progressive disclosure by embedding hundreds of example URLs inline rather than referencing external files, making the skill unnecessarily long and difficult to navigate.
Suggestions
Move the example URL lists to separate reference files (e.g., examples/SPREADSHEET.md, examples/DOCUMENT.md) and link to them from SKILL.md
In SKILL.md, provide only the URL pattern (BASE + example path) with 1-2 examples per component, directing Claude to the reference files for the full list
Consider condensing the URL lists into a searchable format or JSON file that Claude can query rather than scanning hundreds of lines
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with CLI commands and search patterns, but the massive URL lists (300+ example URLs) are verbose and could be condensed into a pattern or reference file rather than inline content. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands with specific paths, ripgrep patterns, and clear URL construction patterns. The examples are copy-paste ready and cover multiple platforms. | 3 / 3 |
Workflow Clarity | Clear workflow: check CLI first → search XML docs → if insufficient, search online → validate by compiling. The validation step with explicit guidance to ignore unrelated errors is a good checkpoint. | 3 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with 300+ URLs inline. The example URLs should be in separate reference files (e.g., SPREADSHEET_EXAMPLES.md) with SKILL.md providing just the URL pattern and linking to references. | 1 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
6bf1316
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.