CtrlK
BlogDocsLog inGet started
Tessl Logo

nutrient-document-processing

使用 Nutrient DWS API 进行文档处理、转换、OCR、提取、脱敏、签名以及表单填充。支持 PDF、DOCX、XLSX、PPTX、HTML 和图像格式。

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

87%

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

The body is a tight, highly actionable reference of copy-paste curl commands for each document operation, well-organized into clear sections. The main gap is the lack of validation/error-handling guidance for destructive operations such as redaction and signing.

Suggestions

Add a brief verification step for destructive operations (e.g., check the API HTTP status with curl -f, or confirm redacted output no longer contains the target PII pattern).

Show how to handle common API errors (non-200 responses, invalid instructions JSON) so failed builds can be diagnosed rather than silently producing empty output.

Optionally note an output-validation command after redaction/signing to close the feedback loop for irreversible actions.

DimensionReasoningScore

Conciseness

The body is lean and code-driven — section headers, curl blocks, and brief notes — without explaining concepts Claude already knows; the repeated curl boilerplate is justified for copy-paste executability, so every token earns its place.

3 / 3

Actionability

Each operation ships a complete, copy-paste-ready curl command with the real endpoint, Authorization header, file fields, and instructions JSON, plus concrete preset and language-code lists; this matches the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Operations are individually clear single API calls, but destructive actions like redaction and signing include no verification checkpoint (e.g., HTTP status checks or output validation), so per the rubric guideline workflow clarity is capped at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the single self-contained body is well-organized into Setup, per-operation subsections, MCP, When-to-use, and Links, with only one-level-deep external references; this satisfies the well-organized-sections anchor for progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

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 is specific and distinctive, clearly stating many concrete document-processing actions and supported formats. Its main weakness is the absence of an explicit 'Use when…' trigger clause and reliance on the technical API name rather than natural user phrasing.

Suggestions

Add an explicit 'Use when…' clause naming natural user triggers (e.g., 'Use when the user asks to convert, OCR, redact, sign, or fill PDF/Office documents').

Soften the lead-in jargon '使用 Nutrient DWS API' and surface natural terms like 'forms', 'PDFs', and '.pdf' that users actually say.

Keep the concrete action list but pair it with the trigger guidance so both 'what' and 'when' are explicit.

DimensionReasoningScore

Specificity

The description lists seven concrete actions — 处理、转换、OCR、提取、脱敏、签名和填充 — matching the 'lists multiple specific concrete actions' anchor; it is not the score-2 anchor because the action coverage is comprehensive rather than partial.

3 / 3

Completeness

The 'what' is strongly covered by the enumerated actions and formats, but there is no 'Use when…' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural file-format keywords (PDF, DOCX, XLSX, PPTX, HTML, 图像) appear, but the description leads with technical jargon ('使用 Nutrient DWS API') and omits common variations users say such as 'forms', '.pdf', or 'PDFs'.

2 / 3

Distinctiveness Conflict Risk

Naming a specific third-party API plus a distinct bundle of operations (OCR, redact, sign, fill) carves a clear niche unlikely to trigger competing skills; it is not score 2 because the operation set is specific rather than broadly overlapping.

3 / 3

Total

10

/

12

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
xu-xiang/everything-claude-code-zh
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.