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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill documenso-sdk-patterns84
Quality
77%
Does it follow best practices?
Impact
100%
2.08xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-sdk-patterns/SKILL.mdDiscovery
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 excellent completeness and trigger term coverage. It clearly identifies when to use the skill and provides explicit trigger phrases. The main weakness is that the capabilities could be more specific about what concrete SDK operations it covers (e.g., document creation, signature workflows, template management).
Suggestions
Add specific concrete actions the skill covers, such as 'document creation', 'signature requests', 'template management', or 'webhook handling' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Documenso SDK) and mentions actions like 'implementing integrations', 'refactoring SDK usage', and 'establishing team coding standards', but doesn't list concrete specific actions like 'create documents', 'send for signature', or 'manage templates'. | 2 / 3 |
Completeness | Clearly answers both what ('Apply production-ready Documenso SDK patterns for TypeScript and Python') and when ('Use when implementing Documenso integrations, refactoring SDK usage, or establishing team coding standards') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'documenso SDK patterns', 'documenso best practices', 'documenso code patterns', 'idiomatic documenso'. Also mentions TypeScript and Python which are relevant keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Documenso SDK specifically. The combination of 'Documenso' + 'SDK patterns' + language-specific mentions creates a clear, distinct trigger that's 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, production-ready code patterns for Documenso SDK integration with excellent actionability. However, it's overly long for a SKILL.md file - the detailed implementations would be better as referenced files. The workflow lacks explicit validation checkpoints between multi-step operations like document creation.
Suggestions
Add validation checkpoints in the DocumentService.createDocument workflow (e.g., verify document creation succeeded before adding recipients)
Split detailed implementations into separate reference files (e.g., ERRORS.md, RETRY.md, SERVICE.md) and keep SKILL.md as a concise overview with links
Remove the Python section or move it to a separate file - it duplicates TypeScript concepts and adds length without proportional value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides substantial code examples but includes some unnecessary verbosity like the full service facade implementation that could be referenced externally. The Python section feels tacked on and duplicates concepts already shown in TypeScript. | 2 / 3 |
Actionability | Excellent executable code throughout - all TypeScript and Python examples are copy-paste ready with proper imports, types, and complete implementations. The singleton pattern, error handling, and retry logic are all fully functional. | 3 / 3 |
Workflow Clarity | The numbered steps (1-5) provide structure, but there are no explicit validation checkpoints or feedback loops. The DocumentService.createDocument method performs multiple operations without verification steps between them. | 2 / 3 |
Progressive Disclosure | The skill is quite long (~300 lines) with all code inline. The patterns could be split into separate reference files (errors.md, retry.md, etc.) with SKILL.md providing an overview. The 'Next Steps' reference to another skill is good but the main content is monolithic. | 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 | |
- 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.