nutrient-openclaw

Use the pinned Nutrient OpenClaw plugin to convert, OCR, extract, redact, watermark, sign, or inspect the last-known local credit record for documents. Route only OpenClaw document-processing requests to its declared tools. Treat processing as an external, credit-consuming DWS transfer that requires a bounded estimate and action-time confirmation for every invocation.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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 body is a tightly written operational contract with exact routing, a copy-paste confirmation gate, and well-sequenced validation-heavy workflows for credit-consuming and destructive operations. Progressive disclosure is sound via a single verified reference, though the inline operational density leaves minor organization gaps.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence — it never explains what a PDF is or how libraries work — but the estimate/confirmation requirement is restated across several sections, adding tokens that could be tightened, so it sits just below the lean level-5 anchor.	4 / 5
Actionability	Provides exact tool names in a routing table, a copy-paste-ready confirmation block, and precise config field paths (plugins.entries.nutrient-openclaw.config.apiKey); the guidance is concrete and executable for every common case.	5 / 5
Workflow Clarity	The metered-call gate is a 5-step ordered sequence with an explicit action-time confirmation checkpoint, and the AI-redaction and signing subsections add staged validation/inspection steps with feedback loops (re-estimate before each retry), matching the level-5 anchor.	5 / 5
Progressive Disclosure	The body is a clear overview that signals a one-level-deep reference ({baseDir}/references/plugin-contract.md, verified to exist) for contract details, but the body itself is fairly dense with operational rules that could be split further, so it falls short of the level-5 'easy navigation' anchor.	4 / 5
	Total	18 / 20 Passed

Description

75%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 specific, distinctive, and names a comprehensive action set, but it lacks an explicit 'Use when...' trigger clause, leaving the activation condition only weakly implied and capping completeness. Trigger-term coverage is strong on action verbs but omits file-extension synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to convert, OCR, extract, redact, watermark, or sign documents via OpenClaw, or to check the local Nutrient credit ledger.'

Include natural file-extension synonyms (.pdf, .docx, .xlsx, .pptx) so the description matches phrases users actually say.

Lead with the 'what' then the 'when' in the standard '...Use when...' form rather than burying the trigger inside a routing constraint.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'convert, OCR, extract, redact, watermark, sign, or inspect the last-known local credit record' — covering the tool's full surface comprehensively, matching the level-5 anchor.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via 'Route only OpenClaw document-processing requests', so per the missing-trigger-guidance cap it cannot exceed 3.	3 / 5
Trigger Term Quality	Natural action verbs (convert, OCR, extract, redact, watermark, sign) give good keyword coverage, but file extensions and common synonyms (.pdf, .docx, 'PDFs') are absent, so it falls short of the level-5 comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Names the pinned 'Nutrient OpenClaw plugin' and its declared tools, establishing a clear niche with minimal overlap risk against generic document skills.	5 / 5
	Total	17 / 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_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: jdrhyne/agent-skills
Path: skills/nutrient-openclaw/SKILL.md
Commit: 439cd3a

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.