documenso-core-workflow-a
Implement Documenso document creation and recipient management workflows. Use when creating documents, managing recipients, adding signature fields, or building signing workflows with Documenso. Trigger with phrases like "documenso document", "create document", "add recipient", "documenso signer", "signature field".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that clearly identifies the platform (Documenso), lists specific capabilities, provides explicit 'Use when' guidance, and includes natural trigger phrases. It follows best practices by using third person voice and covering both what the skill does and when to use it. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: document creation, recipient management, adding signature fields, and building signing workflows. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement document creation and recipient management workflows) and 'when' (explicit 'Use when' clause and 'Trigger with phrases like' section providing concrete trigger guidance). | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'documenso document', 'create document', 'add recipient', 'documenso signer', 'signature field'. Good coverage of both platform-specific and general action terms. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Documenso' platform name creates a clear niche. Combined with specific terms like 'signature field', 'signing workflows', and 'documenso signer', this is highly unlikely to conflict with generic document or file management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable code examples covering the full document creation workflow. Its main weaknesses are the lack of validation checkpoints before the send operation (which is effectively irreversible) and some redundancy in later steps that could be trimmed or split into separate files. The error handling table and status flow diagram are strong additions.
Suggestions
Add an explicit validation checkpoint before `client.documents.sendV0()` — e.g., retrieve the document, verify recipient count and field assignments, and confirm status is DRAFT before sending.
Consider moving the multi-signer helper function (Step 5) and the v1 REST API alternative (Step 6) into a separate reference file to reduce the main skill's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary verbosity—like the multi-signer helper function (Step 5) which largely repeats patterns from earlier steps, and the v1 REST API example in Step 6 that adds a second approach without clear justification. The role table and error table are useful and compact. | 2 / 3 |
Actionability | Every step includes fully executable TypeScript code with concrete values, specific field types, percentage-based positioning explanations, and copy-paste ready examples. The error handling table maps specific HTTP codes to causes and solutions. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create → upload → recipients → fields → send) and the document status flow diagram is helpful. However, there are no explicit validation checkpoints—no step verifies the document was created successfully, that the PDF uploaded correctly, or that fields were positioned properly before sending. For a workflow involving document creation and sending, verification steps before the irreversible send() call would be important. | 2 / 3 |
Progressive Disclosure | The skill references prerequisite skills (documenso-install-auth, documenso-sdk-patterns) and a follow-up skill (documenso-core-workflow-b), and links to external SDK docs. However, the content is quite long (~200 lines of code examples) with Steps 5 and 6 containing material that could be split into separate reference files. No bundle files exist to offload advanced patterns. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.