CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nutrient-document-processing

Nutrient DWS API を使用してドキュメントの処理、変換、OCR、抽出、編集、署名、フォーム入力を行います。PDF、DOCX、XLSX、PPTX、HTML、画像に対応しています。

1.40x
Quality

84%

Does it follow best practices?

Impact

100%

1.40x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

A lean, highly actionable API reference: every section is an executable curl recipe with setup and an MCP alternative, and there is no padding. The main gaps are the absence of any error-handling or output-verification guidance (notably after PII redaction) and inline bulk reference lists that belong in a separate file.

Suggestions

Add a short verification note for redaction, e.g. re-run text extraction on the redacted output to confirm no PII remains, which would lift workflow clarity to 5.

Move the input-format list, redaction preset list, and OCR language codes into a references/ file (e.g. references/formats.md) linked from SKILL.md to improve progressive disclosure.

Add one line on handling API errors (non-200 response body format / retry guidance) so failures don't stall the workflow.

DimensionReasoningScore

Conciseness

The body is almost entirely executable curl commands with one-line framing per section ("すべてのリクエストは … マルチパート POST として送信されます"); it explains nothing Claude already knows and the format/preset/language lists each earn their tokens.

5 / 5

Actionability

Every operation is a fully executable, copy-paste-ready curl command with auth header, multipart instructions JSON, and output flag (e.g. the DOCX-to-PDF and fillForm examples), plus API-key setup and a ready-to-use MCP server config covering common cases.

5 / 5

Workflow Clarity

Each task is a single unambiguous API call, so sequencing is trivial, but no checkpoints exist anywhere: no guidance on handling API errors, and critically no verification step after PII redaction ("機密情報の編集"), where a silent failure would leak sensitive data — this fits 'minor validation gaps' rather than the explicit-validation anchor at 5.

4 / 5

Progressive Disclosure

No bundle files exist and the body has clean section headers with one-level external links ("[完全な OCR 言語表]", "[完全な API ドキュメント]"), but bulk reference data — the ~20-entry input format list, 13 redaction presets, and OCR language-code list — is inlined where a references/ file would keep SKILL.md lean, matching 'minor organization gaps' rather than the fully-split anchor.

4 / 5

Total

18

/

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.

A specific, well-scoped description that names concrete capabilities and the vendor API, weakened mainly by the total absence of any 'when to use' trigger clause. Keyword coverage is good but lacks common synonyms such as scan or text extraction.

Suggestions

Append an explicit trigger clause, e.g. "Use when converting documents, extracting PDF text or tables, OCR-ing scans, or redacting PII before sharing" — this would lift completeness from 3 to 4-5.

Add natural trigger synonyms like "スキャン" (scan), "テキスト抽出" (text extraction), "マージ" (merge), and "文書/PDFs" to improve trigger term coverage.

Drop the generic "処理" (processing) since the enumerated actions already convey it, freeing room for trigger phrases.

DimensionReasoningScore

Specificity

The description lists six concrete actions — "変換、OCR、抽出、編集、署名、フォーム入力" (conversion, OCR, extraction, redaction, signing, form filling) — plus the supported formats, matching the comprehensive-coverage anchor; the only generic token is "処理" (processing).

5 / 5

Completeness

The 'what' is clearly and concretely stated (specific actions via the Nutrient DWS API), but there is no 'Use when...' clause or any equivalent trigger guidance, which the guidelines explicitly cap at 3.

3 / 5

Trigger Term Quality

Keywords "PDF、DOCX、XLSX、PPTX、HTML、画像", "OCR", "フォーム入力" give good natural coverage including file formats, but common synonyms like "スキャン" (scan), "テキスト抽出" (text extraction), and "PDFs" are missing, so it fits 'a few natural terms missing' rather than the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Naming "Nutrient DWS API" gives a clear vendor niche distinct from generic document skills, but without explicit trigger phrases the bare format names (PDF, DOCX, etc.) leave minor overlap risk with generic PDF/document skills, fitting 'mostly distinct; minor overlap risk' rather than the 5 anchor whose example includes explicit triggers.

4 / 5

Total

16

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

affaan-m/ECC

Path

docs/ja-JP/skills/nutrient-document-processing/SKILL.md

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.