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 well-structured skill description that clearly identifies its niche (Documenso template workflows and signing links), provides explicit trigger guidance, and answers both what and when. Its main weakness is that the capability descriptions could be slightly more concrete—listing specific actions like 'create templates with fields', 'send signing invitations', or 'track document status' would strengthen specificity.
Suggestions
Add more concrete action verbs to improve specificity, e.g., 'create templates with recipient fields, generate pre-filled documents from templates, produce direct signing URLs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso templates) and some actions ('template-based workflows', 'direct signing links', 'generating documents from templates'), but the actions are somewhat high-level and not fully concrete—e.g., it doesn't specify what 'implement' entails in detail. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement template-based workflows and direct signing links) and 'when' (explicit 'Use when...' clause and 'Trigger with phrases like...' clause providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'documenso template', 'signing link', 'direct template', 'reusable document', 'template workflow'. These are terms a user would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Documenso's template and signing link features. The combination of 'Documenso' branding with specific concepts like 'direct signing links' and 'template workflows' makes it very unlikely to conflict with other skills. | 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 code examples covering multiple Documenso integration patterns. Its main weaknesses are the lack of validation/error-checking in batch workflows and the monolithic structure that could benefit from splitting advanced topics into separate files. Some content (UI navigation steps, prerequisites) adds tokens without proportional value for Claude.
Suggestions
Add response validation and error handling to the batch generation pattern in Step 3 (check res.ok, handle failures, add retry logic) to properly support batch operations.
Split advanced topics (v2 Envelope API, Embedded Authoring, React embedding) into separate reference files and link from the main SKILL.md to reduce its length.
Remove or minimize UI-only instructions (Steps 1 and 4 dashboard setup) since Claude cannot interact with a browser UI — focus on API-driven workflows instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary content like the Prerequisites section (Claude doesn't need to be told it needs 'understanding of recipient roles'), and the comparison table, while useful, adds bulk. The step-by-step dashboard instructions (Step 1, Step 4 setup) describe UI navigation that Claude can't perform, adding tokens without actionability. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for API calls, complete React component examples with proper imports, HTML iframe embedding, and specific API endpoints with correct headers and body structures. Code is copy-paste ready with realistic field names and patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered from template creation through advanced embedding. However, the batch generation pattern in Step 3 lacks validation — no error checking on API responses, no verification that documents were created successfully, and no retry logic for failed operations. For batch/destructive operations, this caps the score at 2. | 2 / 3 |
Progressive Disclosure | The skill has good structure with clear sections and a helpful comparison table, plus external resource links. However, at ~180 lines it's quite long and could benefit from splitting detailed code examples (batch patterns, v2 envelope API, embedded authoring) into separate reference files. The error handling table and comparison table could also be externalized. No bundle files exist to support progressive disclosure. | 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.