CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-core-workflow-b

Implement Documenso template-based workflows and direct signing links. Use when creating reusable templates, generating documents from templates, or implementing direct signing experiences. Trigger with phrases like "documenso template", "signing link", "direct template", "reusable document", "template workflow".

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.

The body is action-dense with strong executable examples and a clear step sequence, but it is let down by missing validation checkpoints on its batch operation and by failing to surface its bundled reference file for progressive disclosure.

Suggestions

Add a validation/checkpoint step after the batch generateContracts loop (e.g., verify each document was created and sent, handle non-2xx responses with a retry) so the batch workflow has an explicit feedback loop.

Link to references/implementation-guide.md from the body (e.g., a 'Full implementation guide' pointer near the Overview or Resources section) so the bundled reference is clearly signaled and discoverable.

Trim opinionated framing such as 'perfect for public forms, walk-in signers, or embedded flows' and consider condensing the comparison table to keep token density high.

DimensionReasoningScore

Conciseness

Largely efficient with executable code and minimal over-explanation of known concepts, but some inline framing ('perfect for public forms, walk-in signers, or embedded flows') and the comparison table could be trimmed; not quite the leanest possible.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript/tsx/bash examples with concrete endpoints, env-var auth, and specific component props — matching the copy-paste-ready anchor.

3 / 3

Workflow Clarity

A clear 7-step sequence exists, but the batch generation loop in Step 3 and the send-after-create flow lack validation/verification checkpoints and error-recovery feedback, which caps workflow clarity at 2 for batch operations.

2 / 3

Progressive Disclosure

The body is an overview and a real one-level-deep reference bundle exists (references/implementation-guide.md), but the body never signals or links to that reference, so navigation is not clearly surfaced.

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 clear, well-scoped description that states concrete capabilities and an explicit 'Use when' trigger clause with natural keyword variants. It uses third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement Documenso template-based workflows and direct signing links' and 'creating reusable templates, generating documents from templates, or implementing direct signing experiences' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what ('Implement Documenso template-based workflows and direct signing links') and when ('Use when creating reusable templates... or implementing direct signing experiences').

3 / 3

Trigger Term Quality

Provides natural trigger phrases users would say ('documenso template', 'signing link', 'direct template', 'reusable document', 'template workflow'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Niche-specific to Documenso templates and direct signing with distinct, domain-locked 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.