nudocs

Upload, edit, and export documents via Nudocs.ai. Use when creating shareable document links for collaborative editing, uploading markdown/docs to Nudocs for rich editing, or pulling back edited content. Triggers on "send to nudocs", "upload to nudocs", "edit in nudocs", "pull from nudocs", "get the nudocs link", "show my nudocs documents".

Quality

85%

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 nudocs in jdrhyne/agent-skills

Quality

Content

78%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 well-structured, highly actionable CLI skill with excellent progressive disclosure and error coverage. Its main weakness is token efficiency: the duplicated trigger-phrase list and generic document-structure advice add roughly 40 lines of content Claude either already knows or already sees in the description.

Suggestions

Remove the 'Natural Language Triggers' section (or reduce it to only the phrases not already in the frontmatter description, e.g. 'open in nudocs', 'fetch from nudocs', 'grab the updated version') to eliminate ~30 lines of duplication.

Trim 'Document Best Practices' to a one-line pointer to references/document-design.md; heading hierarchy, spacing, and paragraph-length guidance is generic knowledge Claude already applies.

Add validation checkpoints to the workflows: after 'nudocs upload', verify an edit link was returned before presenting it; after 'nudocs pull', confirm the file downloaded successfully before reading and presenting it.

Dimension	Reasoning	Score
Conciseness	Setup, Commands, Workflow, and Error Handling sections are lean, but the ~30-line 'Natural Language Triggers' section duplicates the frontmatter description's trigger phrases and 'Document Best Practices' states generic writing knowledge (heading hierarchy, spacing, 3-5 sentence paragraphs) that Claude already knows.	3 / 5
Actionability	Fully executable throughout: exact npm install and API-key configuration commands, complete CLI syntax with per-flag comments, concrete per-flow commands, and an error table mapping each error to cause and solution.	5 / 5
Workflow Clarity	Upload and Pull flows are clearly sequenced and the Error Handling table provides recovery paths, but there are no explicit verification checkpoints (e.g., confirm a link was returned or that the file downloaded before presenting).	4 / 5
Progressive Disclosure	Both referenced files (references/formats.md, references/document-design.md) exist, are clearly signaled in context, and are one level deep with no nested references; format tables and design templates are appropriately split out of the main file.	5 / 5
	Total	17 / 20 Passed

Description

92%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 strong description with a clear what/when structure, third-person voice, and comprehensive coverage of the upload-edit-export lifecycle. The only gap is trigger-term breadth: a handful of natural synonyms users would plausibly say are absent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Upload, edit, and export documents via Nudocs.ai', 'creating shareable document links for collaborative editing', 'pulling back edited content' — comprehensively covering the skill's core capabilities with only secondary commands (list, delete) omitted.	5 / 5
Completeness	Explicitly answers both what ('Upload, edit, and export documents via Nudocs.ai') and when ('Use when creating shareable document links... Triggers on...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural phrases ('send to nudocs', 'upload to nudocs', 'pull from nudocs', 'get the nudocs link'), but misses common synonyms the body itself lists ('open in nudocs', 'fetch/download from nudocs', 'pull it back') and no file extensions.	4 / 5
Distinctiveness Conflict Risk	Targets a named niche service with service-specific triggers ('nudocs' appears in every trigger phrase), giving minimal overlap risk with any other skill.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: bap-jorkim/agent-skills-fork-feb-25
Path: skills/nudocs/SKILL.md
Commit: f4ed46f

Reviewed: 4 days 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.