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

93%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

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 highly actionable with concrete commands and good progressive disclosure to real reference files, but it carries redundant trigger phrases and generic document-design advice that bloat the token budget, and its workflows lack explicit validation checkpoints for destructive and download operations.

Suggestions

Trim the 'Natural Language Triggers' section or fold it into the frontmatter description to avoid duplicating trigger phrases already stated there.

Add explicit validation checkpoints to the workflows — e.g., confirm the download succeeded before presenting pulled content, and verify a ULID resolves before 'nudocs delete'.

Move generic advice like heading hierarchy and spacing out of 'Document Best Practices' or shrink it to a pointer to document-design.md, since Claude already knows these basics.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and compact tables, but the lengthy 'Natural Language Triggers' section duplicates the frontmatter triggers and 'Document Best Practices' explains heading hierarchy and spacing that Claude already knows; not a 3 because these add unnecessary tokens, not a 1 because core content is lean and useful.	2 / 3
Actionability	Provides copy-paste-ready commands ('nudocs upload <file>', 'nudocs pull [ulid] --format <fmt>'), concrete config bash, and an error-to-cause-to-solution table; matches the anchor for fully executable, specific guidance.	3 / 3
Workflow Clarity	Upload and Pull flows are numbered and sequenced, but validation checkpoints are missing — the destructive 'delete' operation has no embedded verify step and the pull flow never confirms the download succeeded, capping at 2 per the rubric; not a 3 because no explicit validate→fix→retry loop exists.	2 / 3
Progressive Disclosure	The overview body signals one-level-deep references to 'formats.md' and 'document-design.md' in the references folder, both verified to exist, with appropriately split detail content; matches the anchor for clear, well-signaled single-level references.	3 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person, and clearly states both capabilities and trigger conditions with natural language phrases. It is concise while covering upload, edit, export, link-sharing, and pull-back use cases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Upload, edit, and export documents via Nudocs.ai' plus 'creating shareable document links' and 'pulling back edited content' — matching the anchor for listing several specific actions; not a 2 because coverage is comprehensive rather than partial.	3 / 3
Completeness	Answers both 'what' ('Upload, edit, and export documents via Nudocs.ai') and 'when' with an explicit 'Use when...' clause plus trigger phrases, satisfying the anchor for clearly answering both; not a 2 because the 'when' is explicit rather than implied.	3 / 3
Trigger Term Quality	Explicit 'Triggers on "send to nudocs", "upload to nudocs", "edit in nudocs", "pull from nudocs", "get the nudocs link", "show my nudocs documents"' provides good coverage of natural phrasings a user would say; not a 2 because common variations are well represented.	3 / 3
Distinctiveness Conflict Risk	Nudocs.ai is a specific named service with distinctive 'nudocs'-prefixed triggers, making it unlikely to fire for unrelated skills; not a 2 because the niche is clearly bounded and unlikely to overlap.	3 / 3
	Total	12 / 12 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: jdrhyne/agent-skills
Commit: a4d31ad

Reviewed: 11 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.