documenso-core-workflow-b
Implement Documenso template-based workflows and direct signing links. Use when creating reusable templates, generating documents from templates, or implementing direct signing experiences. Trigger with phrases like "documenso template", "signing link", "direct template", "reusable document", "template workflow".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-core-workflow-b/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly identifies its niche (Documenso template workflows), provides explicit trigger guidance with natural phrases, and answers both what and when. Its main weakness is that the capability descriptions could be more concrete—listing specific actions like configuring template fields, setting recipients, or managing signing order would strengthen specificity.
Suggestions
Add more concrete actions to improve specificity, e.g., 'configure template fields, set signing recipients, manage signing order, generate pre-filled documents from templates'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso templates) and some actions ('template-based workflows', 'direct signing links', 'creating reusable templates', 'generating documents from templates'), but the actions are somewhat high-level and not deeply concrete (e.g., doesn't specify field configuration, recipient management, API calls, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (implement template-based workflows and direct signing links) and 'when' (explicit 'Use when...' clause with specific scenarios, plus a 'Trigger with phrases like...' section). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'documenso template', 'signing link', 'direct template', 'reusable document', 'template workflow'. These are terms users would naturally use when requesting this functionality, providing good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Documenso' and the niche focus on template-based signing workflows. Very unlikely to conflict with other skills given the specific domain terminology. | 3 / 3 |
Total | 11 / 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 multiple Documenso integration patterns. Its main weaknesses are the lack of validation/error-handling in batch workflows and the somewhat monolithic structure that could benefit from splitting advanced topics into separate files. The content is generally well-organized but could be tightened by removing UI-focused instructions that Claude cannot execute.
Suggestions
Add error checking and retry logic to the batch generation pattern in Step 3 (e.g., check res.ok before proceeding, handle failures gracefully) to provide proper feedback loops for batch operations.
Move the v2 Envelope API (Step 7) and Embedded Authoring (Step 6) into separate referenced files to reduce the main skill's length and improve progressive disclosure.
Remove or condense Step 1 (dashboard UI instructions) since Claude cannot interact with a UI — instead, just note that template IDs come from the dashboard URL.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary context like the Prerequisites section (Claude doesn't need to be told about prerequisites), the Overview paragraph restating what templates are, and the comparison table which, while useful, adds bulk. Some sections like Step 1 (dashboard UI instructions) are not API-actionable by Claude. | 2 / 3 |
Actionability | Provides fully executable TypeScript code for template document creation, batch generation, embedded signing with React components, and v2 envelope API usage. Code examples are copy-paste ready with realistic parameters, proper headers, and complete fetch calls. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced from template creation through document generation to signing. However, the batch generation pattern in Step 3 lacks validation — no error checking on API responses, no retry logic, and no verification that documents were successfully created before sending. For batch operations, this missing feedback loop caps the score at 2. | 2 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and links to external resources at the end. However, the content is quite long (~180 lines of substantive content) and could benefit from splitting the v2 Envelope API and embedded authoring sections into separate reference files rather than inlining everything. The reference to `documenso-core-workflow-a` and `documenso-common-errors` shows awareness of skill linking. | 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
3e83543
- 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.