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

86%

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

85%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 operational contract for the Nudocs CLI: concise, with concrete commands, explicit validation checkpoints on destructive workflows, and a properly scoped single reference. Minor gains are available in reducing repeated emphasis and making pull format arguments more directly runnable.

Suggestions

Consolidate the repeated 'exact document ID' and 'action-time approval' guidance into one authoritative section to reduce token padding without losing the safety emphasis.

Add one fully-resolved example pull command (e.g. `nudocs pull 01ABC123XYZ --format pdf --output report.pdf`) inline so the common case is copy-paste ready rather than deferring all formats to the reference.

Trim or fold the 'Common failures' list so each item maps to a concrete corrective command rather than restating policy already covered above.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no CLI/secret-manager explanations), but the 'exact document ID' and 'action-time approval' themes recur across several sections, which is mild emphasis padding rather than anchor-5 efficiency.	4 / 5
Actionability	Concrete executable commands are given (`nudocs link <document-id>`, `nudocs pull <document-id> --format <format> --output <exact-output-path>`, `nudocs delete <document-id>`), but they rely on placeholders whose values are deferred to references/formats.md, so they are not fully copy-paste ready as the anchor-5 example requires.	4 / 5
Workflow Clarity	The delete and upload workflows are explicitly numbered with validation checkpoints — resolve ID, state recovery availability, show command semantics, obtain action-time approval, execute once, then verify removal — satisfying the anchor-5 sequence with feedback loops for the destructive operation.	5 / 5
Progressive Disclosure	The body is an overview that points to a single one-level-deep reference (references/formats.md, verified present) with clear load/skip guidance ('Do not load that reference for listing, link lookup, or deletion'), matching the well-signaled anchor-5 structure.	5 / 5
	Total	18 / 20 Passed

Description

87%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, third-person description that states concrete capabilities and pairs them with explicit, natural trigger phrases. It is clearly distinct and complete, with only minor gaps in action specificity and trigger-term breadth.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Upload, edit, and export documents', 'creating shareable document links', 'pulling back edited content'), but 'edit' is somewhat generic, leaving minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ('Upload, edit, and export documents via Nudocs.ai') and when ('Use when...', 'Triggers on...') with concrete trigger phrases, matching the anchor-5 example.	5 / 5
Trigger Term Quality	Six natural trigger phrases ('send to nudocs', 'upload to nudocs', 'edit in nudocs', 'pull from nudocs', 'get the nudocs link', 'show my nudocs documents') give good keyword coverage, but file extensions and synonyms are absent so it stops short of the anchor-5 example.	4 / 5
Distinctiveness Conflict Risk	Nudocs-branded triggers and a clearly scoped niche (hosted document editing/sharing) make it distinct with minimal conflict risk against unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

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

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