nutrient-document-processing

Process, convert, OCR, extract, redact, sign, and fill documents using the Nutrient DWS API. Works with PDFs, DOCX, XLSX, PPTX, HTML, and images. Use when converting, OCRing, extracting from, redacting, signing, or filling documents via the Nutrient DWS API.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is tdg-personal/nutrient-document-processing

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 content is highly actionable with executable curl examples and clean sectioning, but it lacks validation/verification steps for destructive operations like redaction and signing, which caps workflow clarity. Progressive disclosure is good despite the absence of bundle files.

Suggestions

Add a verification step after redaction (e.g., re-extract text from the output PDF and confirm the redacted patterns no longer appear) to satisfy the destructive-operation feedback-loop requirement.

Include brief error-handling guidance showing how to inspect a non-200 API response and retry, giving the workflow an explicit recovery loop.

Trim or fold the 'When to Use' bullet list since it duplicates the frontmatter description's trigger clause, recovering tokens without losing information.

Dimension	Reasoning	Score
Conciseness	The body is lean—commented curl examples and tight supporting lines with no concept explanations—but the 'When to Use' bullet list largely restates the frontmatter triggers, a minor redundancy that could be trimmed.	4 / 5
Actionability	Every operation ships a complete, copy-paste-ready curl command with auth header, multipart fields, and an instructions JSON payload, covering the common cases (convert, extract, OCR, redact, watermark, sign, fill).	5 / 5
Workflow Clarity	Setup and per-operation steps are present, but redaction and signing are destructive/irreversible operations with no validation or verification checkpoint (e.g., confirm PII was actually removed), which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist; content lives in one well-sectioned SKILL.md with clearly signaled external links (API Playground, Full API Docs, npm MCP Server), though the long preset/input/language lists are inlined rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

100%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 is exemplary: it enumerates concrete actions, names supported formats, and provides an explicit 'Use when' trigger clause tied to a specific API. It uses third-person imperative voice and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists seven concrete actions ('Process, convert, OCR, extract, redact, sign, and fill documents') plus the supported formats, giving comprehensive coverage of capabilities rather than vague language.	5 / 5
Completeness	Explicitly states what it does ('Process...documents using the Nutrient DWS API') and when to use it ('Use when converting, OCRing, extracting from, redacting, signing, or filling documents'), satisfying both halves with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural action verbs and their -ing variants ('converting, OCRing, extracting from, redacting, signing, or filling') alongside file extensions ('PDFs, DOCX, XLSX, PPTX, HTML, and images'), matching the comprehensive-synonym anchor.	5 / 5
Distinctiveness Conflict Risk	Tying every trigger to the named 'Nutrient DWS API' gives it a clear niche with distinct triggers and minimal overlap with generic document skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/everything-claude-code
Path: skills/nutrient-document-processing/SKILL.md
Commit: 06c5e11

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.