CtrlK
BlogDocsLog inGet started
Tessl Logo

nutrient-document-processing

使用Nutrient DWS API处理、转换、OCR识别、提取、编辑、签名和填写文档。支持PDF、DOCX、XLSX、PPTX、HTML和图像格式。

89

1.49x
Quality

73%

Does it follow best practices?

Impact

100%

1.49x

Average score across 6 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/nutrient-document-processing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable with complete curl recipes for each operation and clean organization, but it lacks validation/verification steps for destructive actions like redaction and signing. Adding quick verify checks would raise workflow clarity.

Suggestions

Add a verification step after redaction, e.g. re-extract text from the output to confirm the PII patterns are gone before sharing.

Add a verification hint after signing, e.g. checking the digital signature status of the output PDF.

Consider moving the full OCR language table or preset list into a reference file linked from the body to tighten the inline footprint.

DimensionReasoningScore

Conciseness

The body is lean with copy-paste curl examples and no concept over-explanation, though the trailing '使用场景' list partially restates the operations already demonstrated.

4 / 5

Actionability

Every operation ships as a complete, executable curl command with auth header, multipart upload, instructions JSON, and output flag, covering convert/extract/OCR/redact/watermark/sign/fill plus an MCP alternative.

5 / 5

Workflow Clarity

Destructive operations (redaction of PII, digital signing) include no validation or verification checkpoint that the result is correct, so workflow clarity is capped at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

Content is organized into clear sections (设置, 操作, MCP 服务器, 使用场景, 链接) with external links for deeper reference and no nested references, though most API detail lives inline rather than in split files.

4 / 5

Total

16

/

20

Passed

Description

71%Weight 40%Scale 1-5

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 clearly conveys a comprehensive set of concrete document-processing actions tied to a named API, but it lacks an explicit 'Use when...' trigger clause that would tell Claude when to invoke it. Adding trigger guidance would lift both completeness and distinctiveness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user needs to convert, OCR, extract, redact, sign, or fill PDF/Office documents.'

Add natural user phrases beyond file extensions, such as 'forms', 'tables', 'spreadsheets', or 'document extraction', to improve trigger-term coverage.

Mention 'PDFs' / '.pdf' synonyms alongside the format list to match how users actually phrase requests.

DimensionReasoningScore

Specificity

Lists seven concrete actions ('处理、转换、OCR识别、提取、编辑、签名和填写文档') plus supported formats, matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is explicit (process/convert/OCR/extract/edit/sign/fill via Nutrient DWS API) but there is no 'Use when...' trigger clause, so completeness is capped at 3 per the guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage via file extensions (PDF, DOCX, XLSX, PPTX, HTML, 图像), but missing natural user phrases like 'forms', 'tables', or 'document extraction' that the 5 anchor requires.

4 / 5

Distinctiveness Conflict Risk

Naming the specific 'Nutrient DWS API' gives a clear niche with minor overlap risk, but the absent explicit trigger phrases keep it below a 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.