使用Nutrient DWS API处理、转换、OCR、提取、编辑、签署和填写文档。支持PDF、DOCX、XLSX、PPTX、HTML和图像文件。
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill nutrient-document-processing81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
60%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 effectively lists specific capabilities and supported file formats, demonstrating good specificity. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. The broad file format support, while comprehensive, may create overlap with other document-focused skills.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., '当用户需要处理PDF、转换文档格式、进行OCR识别、或需要电子签名时使用'
Include natural user phrases that would trigger this skill, such as '文档转换', '扫描识别', '电子签名', 'convert to PDF'
Consider specifying what distinguishes this from other document skills - emphasize the Nutrient DWS API's unique capabilities or use cases
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: '处理、转换、OCR、提取、编辑、签署和填写文档' (process, convert, OCR, extract, edit, sign, and fill documents). Also specifies supported file formats. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions and file types, but lacks explicit 'when should Claude use it' guidance. No 'Use when...' clause or equivalent trigger guidance is present. | 2 / 3 |
Trigger Term Quality | Includes relevant file format keywords (PDF, DOCX, XLSX, PPTX, HTML, 图像文件) and action terms, but uses Chinese which may limit trigger matching. Missing common user phrases like 'Use when...' or natural variations users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions specific API (Nutrient DWS) which adds distinctiveness, but the broad range of document types (PDF, DOCX, XLSX, PPTX, HTML, images) could overlap with other document-processing skills. The multi-format support makes it somewhat generic. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and conciseness. The curl examples are complete and immediately usable, covering a comprehensive range of document processing operations. The main weakness is the lack of validation steps or error handling guidance, particularly important for operations like redaction where verification is critical.
Suggestions
Add a brief validation section showing how to verify successful operations (e.g., checking HTTP response codes, verifying redaction completeness)
Include error handling guidance or common failure modes for critical operations like digital signing and redaction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what PDFs are or how APIs work - it jumps straight to actionable examples. | 3 / 3 |
Actionability | Every operation includes complete, copy-paste ready curl commands with proper authentication headers and JSON payloads. Examples cover all major use cases with executable code. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but there's no validation/verification guidance for batch operations or error handling. Missing feedback loops for operations like redaction or form filling where verification would be important. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate external links to full documentation, API playground, and language tables. Content is appropriately scoped for a SKILL.md overview. | 3 / 3 |
Total | 11 / 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.
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.