nutrient-document-processing
使用Nutrient DWS API处理、转换、OCR识别、提取、编辑、签名和填写文档。支持PDF、DOCX、XLSX、PPTX、HTML和图像格式。
87
70%
Does it follow best practices?
Impact
100%
1.49xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-CN/skills/nutrient-document-processing/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at listing specific capabilities and supported formats, making it clear what the skill does. However, it lacks an explicit 'Use when...' clause, which limits Claude's ability to know precisely when to select this skill. The inclusion of the specific API name (Nutrient DWS) aids distinctiveness but is not a natural user trigger term.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to convert, OCR, extract text from, edit, sign, or fill documents in PDF, DOCX, XLSX, PPTX, HTML, or image formats.'
Include natural language trigger variations users might say, such as 'convert Word to PDF', 'scan document text', 'fill out a form', 'digitally sign a document', or 'extract tables from a spreadsheet'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 处理 (process), 转换 (convert), OCR识别 (OCR recognition), 提取 (extract), 编辑 (edit), 签名 (sign), and 填写 (fill) documents. Also specifies supported formats (PDF, DOCX, XLSX, PPTX, HTML, images). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and supported formats, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like PDF, DOCX, XLSX, PPTX, HTML, OCR, and action terms like 签名/签署 and 填写. However, it lacks common user-facing variations and natural language triggers (e.g., 'scan documents', 'convert to PDF', 'fill forms'). The mention of 'Nutrient DWS API' is technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Nutrient DWS API' as the specific tool, combined with the comprehensive list of document operations and supported formats, creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference skill with excellent actionability — every operation has complete, executable curl examples. The main weaknesses are the lack of error handling/validation guidance (no mention of checking response codes or handling failures) and some minor verbosity in the use cases section and format listings. The structure and progressive disclosure are well done for a standalone skill.
Suggestions
Add error handling guidance: check HTTP status codes (e.g., `|| echo 'Error: check API key and file path'`), mention common failure modes (invalid API key, unsupported format, file too large), and expected success response codes.
Remove or significantly condense the '使用场景' section — it merely restates what the operation headers already communicate and adds no new information.
Add a brief example of chaining multiple actions in a single request (e.g., OCR + redaction + watermark) since the API supports it via the actions array, which would demonstrate a multi-step workflow with implicit validation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete examples, but includes some unnecessary content like the '使用场景' (use cases) section which restates what's already obvious from the operations above, and the supported formats list could be more compact. The OCR language explanation is slightly verbose. | 2 / 3 |
Actionability | Every operation includes a complete, copy-paste-ready curl command with proper authentication, file handling, and JSON instructions. The examples cover all major use cases with real, executable commands that only need an API key substitution. | 3 / 3 |
Workflow Clarity | Each operation is presented as a standalone single-step API call, which is clear for individual tasks. However, there are no validation checkpoints (e.g., checking HTTP status codes, verifying output file integrity), no error handling guidance, and no guidance on chaining operations together despite the API supporting multi-action workflows. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with a clear overview, logically organized sections by operation type, and appropriate external references to full API docs, playground, and MCP server package. For a standalone skill with no bundle files, the organization is clean and navigable with well-signaled links. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- affaan-m/everything-claude-code
- Commit
841beea
- Reviewed
Table of Contents
Is this your skill?
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.