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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is actionable and well-structured with good progressive disclosure, but loses conciseness to duplicated triggers and generic best-practice padding, and lacks explicit in-workflow validation checkpoints for the destructive delete operation.

Suggestions

Remove or trim the Natural Language Triggers section since the same phrases already appear in the frontmatter description, to avoid duplicated token spend (conciseness).

Replace the generic Document Best Practices list with a pointer to document-design.md, keeping only Nudocs-specific guidance (conciseness).

Add an explicit confirmation/verification step inside the delete (and where relevant, pull) workflow steps rather than relying solely on the Safety Boundaries section (workflow_clarity).

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command tables and short workflows, but the Natural Language Triggers section duplicates phrases already in the frontmatter and Document Best Practices explains generic writing concepts Claude already knows, so it does not reach the lean score-3 bar.	2 / 3
Actionability	Provides copy-paste-ready executable commands (e.g., "nudocs upload <file>", "nudocs pull [ulid] --format <fmt>"), a format-selection table, an example session, and an error-cause/solution table, matching the score-3 anchor.	3 / 3
Workflow Clarity	Upload and Pull flows are clearly sequenced, but the destructive `nudocs delete` operation and confirmation expectations live only in Safety Boundaries, with no explicit in-workflow validation/confirmation checkpoint, capping clarity at 2.	2 / 3
Progressive Disclosure	The body is an overview that signals two real one-level-deep references (formats.md, document-design.md) at the relevant sections, with no nested references and clear organization, matching the score-3 anchor.	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, well-triggered, and complete, clearly stating both the capability and the conditions for use with natural-language triggers and a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("Upload, edit, and export documents", "creating shareable document links", "uploading markdown/docs", "pulling back edited content") with no vague fluff, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what ("Upload, edit, and export documents via Nudocs.ai") and when ("Use when creating shareable document links...") with an explicit "Use when" clause and trigger list.	3 / 3
Trigger Term Quality	Provides natural phrases users would actually say ("send to nudocs", "upload to nudocs", "edit in nudocs", "pull from nudocs", "get the nudocs link", "show my nudocs documents"), giving good coverage rather than only a few relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Nudocs.ai) with branded, distinct triggers unlikely to fire for other skills, matching the score-3 anchor.	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: 292843f

Reviewed: about 16 hours 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.