CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/documenso-pack/skills/documenso-sdk-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, executable code with lean prose, but it underuses progressive disclosure: two reference files sit orphaned while ~290 lines of patterns are inlined, and the lone multi-step workflow lacks validation checkpoints.

Suggestions

Link the existing reference files from the body (e.g., a '## Full implementation guide — see [implementation-guide.md](references/implementation-guide.md)') and trim duplicated inline code so SKILL.md stays a lean overview.

Add an explicit validation/verification checkpoint to the create-and-send workflow (e.g., confirm the document and recipients were created before calling sendV0) to lift workflow_clarity to 3.

Reconcile the orphaned references with the inline content so they are clearly signaled and one level deep rather than duplicative.

DimensionReasoningScore

Conciseness

The prose is lean and assumes competence, but ~290 lines of six full inline code patterns — largely duplicated by the two reference files — could be tightened by offloading detail to those references rather than repeating it inline.

2 / 3

Actionability

Six complete, executable TypeScript and Python patterns with imports, types, and real logic, plus a concrete error-cause table — copy-paste ready as the score-3 anchor requires.

3 / 3

Workflow Clarity

Pattern 2 has a clear create→upload→add-recipients→send sequence, but there are no validation checkpoints or validate→fix→retry feedback loops, so it sits at the score-2 anchor.

2 / 3

Progressive Disclosure

Two reference files exist (implementation-guide.md, implementation.md) but the body never links to them, and detailed implementations are inlined rather than split out — 'references present but not clearly signaled; content that should be separate is inline'.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description with an explicit 'Use when' clause and good trigger-term coverage for a well-scoped niche. Its only weakness is specificity: it states a single generic action rather than listing the concrete patterns the skill covers.

Suggestions

Enumerate the concrete capabilities in the description (e.g., 'singleton clients, typed wrappers, error handling, retry with backoff, and test mocks') to lift specificity from 2 to 3.

Consider adding 'TypeScript and Python SDK' as explicit trigger keywords so language-specific queries match more reliably.

DimensionReasoningScore

Specificity

Names the domain ('Documenso SDK patterns for TypeScript and Python') and the action 'Apply', but does not enumerate multiple specific concrete actions (e.g., singleton clients, retry, error handling) as the score-3 anchor requires.

2 / 3

Completeness

Explicitly answers both what ('Apply production-ready Documenso SDK patterns...') and when via an explicit 'Use when...' clause with concrete triggers, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Provides several natural phrases users would say — 'documenso SDK patterns', 'documenso best practices', 'documenso code patterns', 'idiomatic documenso' — plus 'integrations' and 'refactoring SDK usage', giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear, product-specific niche (Documenso SDK) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.