CtrlK
BlogDocsLog inGet started
Tessl Logo

documenso-data-handling

Handle document data, signatures, and PII in Documenso integrations. Use when managing document lifecycle, handling signed PDFs, or implementing data retention policies. Trigger with phrases like "documenso data", "signed document", "document retention", "documenso PII", "download signed pdf".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

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.

A strong, actionable, token-efficient skill body built around executable TypeScript examples. The gaps are a missing feedback loop around destructive batch deletions and a failure to surface the existing implementation-guide bundle file.

Suggestions

Add an explicit validate-then-retry loop for the destructive operations in Steps 3 and 4, e.g. confirm deletion candidates before calling deleteV0 and retry on API error with backoff.

Link references/implementation-guide.md from the body (e.g. a "## Implementation guide" section pointing to it) and move the detailed code there, keeping SKILL.md as a concise overview.

Add a brief verification step after archiving to S3 (e.g. confirm the object exists and its checksum matches) to close the loop on the storage workflow.

DimensionReasoningScore

Conciseness

The body is code-forward and lean, with no concept-explaining filler, an ASCII lifecycle diagram and tables doing double duty; it assumes Claude's competence and avoids padding.

3 / 3

Actionability

All five steps provide full, executable TypeScript using the real Documenso SDK and AWS SDK with concrete calls, environment variables, and copy-paste-ready functions.

3 / 3

Workflow Clarity

The five-step sequence is clear and Step 1 has a status checkpoint, but the destructive batch operations (draft deletion in retention, GDPR erasure) lack inline validate-fix-retry feedback loops, capping the score per the rubric.

2 / 3

Progressive Disclosure

Sections and tables give some structure, but the bundle file references/implementation-guide.md is never linked from the body and detailed implementation code that could live in the reference is kept entirely inline.

2 / 3

Total

10

/

12

Passed

Description

90%

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 well-structured description that clearly answers both what and when with strong, natural trigger terms and clear product distinctiveness. The main weakness is the generic verb "Handle," which understates the concrete capabilities described in the body.

Suggestions

Replace the abstract verb "Handle" with concrete actions from the body, e.g. "Download signed PDFs, sanitize PII in logs, enforce data retention, and process GDPR requests in Documenso integrations."

DimensionReasoningScore

Specificity

Names the domain and three data objects ("document data, signatures, and PII") but the verb "Handle" is abstract rather than listing concrete actions like download, sanitize, archive, or retain, so it does not reach the multiple-concrete-actions bar.

2 / 3

Completeness

Clearly states what ("Handle document data, signatures, and PII in Documenso integrations") and when ("Use when managing document lifecycle, handling signed PDFs, or implementing data retention policies") with an explicit trigger clause.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases ("documenso data", "signed document", "document retention", "documenso PII", "download signed pdf") give good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to the specific Documenso product with distinct, product-specific 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.