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

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is highly actionable and token-efficient, delivering six complete executable patterns without padding. Its weak spots are the absence of validation checkpoints in the document-creation/send workflow and the failure to signal the existing reference bundle files, leaving content inline that could be split out.

Suggestions

Add an explicit validation step (e.g. verify the document and recipients exist before calling sendV0) and a retry/error-recovery loop in the createAndSendDocument pattern to add a feedback checkpoint around the consequential send operation.

Link the local bundle files from the body — e.g. under Resources add "**Full implementation guide**: See [references/implementation-guide.md](references/implementation-guide.md)" — so the existing references are discoverable rather than orphaned.

Move the longer pattern implementations (e.g. the full createAndSendDocument and retry patterns) into references/ and keep SKILL.md as a concise overview with one-level-deep pointers, reducing inline duplication with implementation-guide.md.

DimensionReasoningScore

Conciseness

The body is code-forward with lean prose (a one-sentence overview, three prerequisite bullets) and never explains concepts Claude already knows; every code block is a distinct production pattern that earns its place.

3 / 3

Actionability

All six patterns are complete, executable TypeScript/Python with real imports, types, and signatures — e.g. the singleton client and createAndSendDocument are copy-paste ready, not pseudocode.

3 / 3

Workflow Clarity

The createAndSendDocument pattern has an implicit sequence (create → upload → add recipients → add fields → send) but no validation checkpoints before the consequential send step, which caps workflow clarity at 2 for a batch/consequential operation.

2 / 3

Progressive Disclosure

The body is organized into clear sections but keeps six full code patterns inline, and the bundle files in references/ (implementation.md, implementation-guide.md) are present yet never linked or signaled from the body — the Resources section only points to external URLs.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is specific, complete, and distinctive: it names the domain and several concrete actions, includes an explicit "Use when" clause with natural trigger phrases, and occupies a clear product-specific niche. Third-person voice is maintained throughout with no first/second-person slippage.

DimensionReasoningScore

Specificity

It lists multiple concrete actions — "implementing Documenso integrations, refactoring SDK usage, or establishing team coding standards for Documenso" — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

It explicitly answers both what ("Apply production-ready Documenso SDK patterns for TypeScript and Python") and when ("Use when implementing...") with an explicit "Use when" trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Trigger phrases like "documenso SDK patterns", "documenso best practices", "documenso code patterns", and "idiomatic documenso" are natural terms a user would actually say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

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

3 / 3

Total

12

/

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.