documenso-sdk-patterns
Apply production-ready Documenso SDK patterns for TypeScript and Python. Use when implementing Documenso integrations, refactoring SDK usage, or establishing team coding standards for Documenso. Trigger with phrases like "documenso SDK patterns", "documenso best practices", "documenso code patterns", "idiomatic documenso".
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-sdk-patterns/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 with strong completeness and distinctiveness due to the specific product focus (Documenso). The explicit trigger phrases and 'Use when' clause are well done. The main weakness is that the specific capabilities could be more concrete—listing actual SDK operations rather than general activities like 'implementing integrations' and 'establishing coding standards'.
Suggestions
Add more concrete actions describing what the skill actually does with the Documenso SDK, e.g., 'create and send documents for signing, manage templates, configure webhooks, handle recipient workflows'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Documenso SDK patterns for TypeScript and Python) and mentions some actions (implementing integrations, refactoring SDK usage, establishing coding standards), but these are somewhat generic and don't list concrete specific actions like 'create documents', 'manage templates', 'handle signing workflows'. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Documenso SDK patterns for TypeScript and Python) and 'when' (implementing integrations, refactoring SDK usage, establishing team coding standards) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'documenso SDK patterns', 'documenso best practices', 'documenso code patterns', 'idiomatic documenso', plus natural terms like 'Documenso integrations' and 'TypeScript and Python'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Documenso is a specific product/SDK, making this highly distinctive. The combination of 'Documenso' with 'SDK patterns' creates a clear niche that is 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 skill provides high-quality, actionable code patterns for Documenso SDK integration across TypeScript and Python, with good coverage of singleton clients, error handling, retry logic, and testing. Its main weaknesses are the monolithic structure (all patterns inline rather than split into referenced files) and the lack of explicit validation checkpoints in the multi-step document creation workflow before irreversible send operations.
Suggestions
Add a validation/confirmation step before `sendV0` in the document creation workflow (e.g., verify recipients and fields are correctly attached) to prevent sending incomplete documents.
Split individual patterns into separate referenced files (e.g., `patterns/singleton-client.md`, `patterns/error-handling.md`) and keep SKILL.md as a concise overview with links to each pattern.
Remove the Prerequisites section — Claude already understands async/await, TypeScript generics, and error handling best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary elements like the Prerequisites section (Claude knows async/await and error handling), and the patterns are quite lengthy. The Python pattern largely duplicates the TypeScript pattern's logic, and some inline comments are redundant. | 2 / 3 |
Actionability | All six patterns provide fully executable, copy-paste ready code with proper imports, type definitions, and file paths. The code is concrete, complete, and immediately usable — not pseudocode or abstract descriptions. | 3 / 3 |
Workflow Clarity | The patterns are presented as independent modules with clear sequencing within each (e.g., create → upload → add recipients → send), but there's no explicit validation checkpoint or feedback loop for the multi-step document creation process. Given that sending a document is a potentially destructive/irreversible operation, a validation step before sendV0 would be appropriate. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic file (~250 lines of code patterns) that could benefit from splitting patterns into separate files with the SKILL.md serving as an overview. References to external resources and next steps exist but the main body contains everything inline rather than using progressive disclosure effectively. | 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.