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

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is highly actionable with executable TypeScript and useful reference tables, but it lacks validation/verification checkpoints for its destructive batch operations and fails to wire its bundled reference file into the navigation. Tightening the duplicated download logic and adding confirm-before-delete gates would lift the weaker dimensions.

Suggestions

Add explicit validation/feedback checkpoints to the retention and GDPR-erasure workflows (e.g., confirm document count, verify deletion succeeded, retry-with-backoff loop) before performing destructive batch operations.

Reference the bundled references/implementation-guide.md from the body (e.g., a 'See implementation-guide.md for the full client setup' link) so the progressive-disclosure structure is actually signaled.

De-duplicate the download-via-fetch logic used in Step 1 and Step 5 by extracting a shared helper, and trim explanatory comments to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code and useful classification/error tables, but the download-via-fetch block is duplicated across Step 1 and Step 5, and there is light explanatory padding that could be trimmed.	2 / 3
Actionability	Each step ships complete, executable TypeScript with real SDK calls, error checks, and copy-paste-ready snippets like the retention policy and S3 archive — fully concrete rather than descriptive.	3 / 3
Workflow Clarity	Steps are clearly sequenced, but destructive/batch operations (retention deletion in Step 3 and GDPR erasure in Step 4) lack explicit validation checkpoints or feedback loops, capping workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	Section organization is reasonable, but a bundled references/implementation-guide.md exists and is never signaled or linked from the body, and content that could be split (full code per step) stays inline.	2 / 3
	Total	9 / 12 Passed

Description

100%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, well-scoped description: it states concrete capabilities, gives explicit 'Use when' triggers plus natural keyword phrases, and is clearly distinguishable from generic document skills. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Handle document data, signatures, and PII', 'managing document lifecycle, handling signed PDFs', 'implementing data retention policies' — matching the top anchor.	3 / 3
Completeness	Clearly answers both what (handle document data, signatures, PII) and when ('Use when managing document lifecycle, handling signed PDFs, or implementing data retention policies') with explicit triggers.	3 / 3
Trigger Term Quality	Explicit natural phrases a user would say ('documenso data', 'signed document', 'document retention', 'documenso PII', 'download signed pdf') give good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear Documenso niche with product-specific triggers, making it unlikely to fire for unrelated document skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/saas-packs/documenso-pack/skills/documenso-data-handling/SKILL.md
Commit: 0540a62

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.