CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-performance-tuning

Optimize Documenso integration performance with caching, batching, and efficient patterns. Use when improving response times, reducing API calls, or optimizing bulk document operations. Trigger with phrases like "documenso performance", "optimize documenso", "documenso caching", "documenso batch operations".

67

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

65%

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

Actionable and code-rich with useful performance-target and error-handling tables, but verbose in places and undermined by an orphaned implementation-guide.md that the body never references. Could not reach 3 on workflow_clarity or progressive_disclosure due to missing validation checkpoints and un-signaled bundle navigation.

Suggestions

Link the bundled guide from the body (e.g., 'For full caching/batching implementations, see [implementation-guide.md](references/implementation-guide.md)') and move the redundant detailed code there to fix the orphaned reference.

Add explicit validation checkpoints to batch operations: after batchCreateDocuments, verify success count, log/retry failures, and confirm totals before proceeding.

Remove or compress the WITHOUT-templates code block to one line; the WITH block plus the '5+ calls → 2 calls' comment already conveys the optimization.

DimensionReasoningScore

Conciseness

Mostly lean code with no basic-concept padding, but the WITHOUT-templates contrast block and overall length could be tightened; matches 'mostly efficient but could be tightened' rather than the lean level-3 anchor.

2 / 3

Actionability

Fully executable TypeScript with real SDK methods (createV0, sendV0), concrete URLs, and specific config values (concurrency: 5, intervalCap: 10); copy-paste ready.

3 / 3

Workflow Clarity

Five steps are clearly sequenced and error handling exists (Promise.allSettled, queue retry/backoff), but batch and async operations lack explicit validate-then-proceed checkpoints, so it sits at level 2 rather than 3.

2 / 3

Progressive Disclosure

Sections are well-organized, but the bundled references/implementation-guide.md is never linked from the body and detailed implementations are inline, fitting 'references present but not clearly signaled'.

2 / 3

Total

9

/

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.

A strong description: concrete capabilities, explicit 'Use when' clause, and natural trigger phrases in third-person voice. Not below 3 on any dimension because all four anchors for the top level are met without vagueness or padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'caching, batching, and efficient patterns', 'reducing API calls', 'optimizing bulk document operations' — in third-person voice, matching the level-3 example of multiple specific actions.

3 / 3

Completeness

Clearly answers what ('Optimize Documenso integration performance with caching, batching...') and when ('Use when improving response times, reducing API calls...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Explicitly enumerates natural user phrases ('documenso performance', 'optimize documenso', 'documenso caching', 'documenso batch operations') that a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to Documenso performance with niche-specific 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.