nudocs
tessl i github:jdrhyne/agent-skills --skill nudocsUpload, 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".
Validation
75%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
Implementation
88%This is a well-crafted skill that efficiently teaches Claude how to interact with Nudocs. The content is concise, actionable with executable commands, and well-organized with appropriate references to detailed documentation. The main weakness is the lack of explicit validation steps in workflows - there's no guidance on verifying upload success or handling partial failures.
Suggestions
Add validation checkpoints to workflows, e.g., 'After upload, verify the returned ULID is valid before sharing the link' or 'Check exit code after pull to confirm download succeeded'
Include a brief troubleshooting step in the example session showing how to recover if a command fails mid-workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient throughout. No unnecessary explanations of what Nudocs is or how CLIs work. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides complete, copy-paste ready commands for all operations. Setup instructions are specific with exact paths and commands. The command reference and example session show exactly what to run. | 3 / 3 |
Workflow Clarity | Upload and pull flows are clearly sequenced, but lack validation checkpoints. No verification step after upload to confirm success, no error checking between steps. The example session shows the happy path but doesn't address what to do if commands fail. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections. Appropriately references external files (references/formats.md, references/document-design.md) for detailed content. Main skill stays focused on core usage patterns. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific actions, comprehensive trigger terms that users would naturally say, explicit guidance on both what the skill does and when to use it, and clear distinctiveness through the Nudocs branding. The description follows best practices by using third person voice and including both a 'Use when' clause and explicit trigger phrases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Upload, edit, and export documents' with clear outcomes like 'creating shareable document links', 'uploading markdown/docs', and 'pulling back edited content'. | 3 / 3 |
Completeness | Clearly answers both what (upload, edit, export documents via Nudocs.ai) and when (explicit 'Use when...' clause with scenarios plus explicit 'Triggers on' section with specific phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'send to nudocs', 'upload to nudocs', 'edit in nudocs', 'pull from nudocs', 'get the nudocs link', 'show my nudocs documents' - all realistic user commands. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Nudocs' branding throughout all triggers - unlikely to conflict with generic document skills since every trigger explicitly mentions 'nudocs'. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
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.