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".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/documenso-pack/skills/documenso-data-handling/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description that clearly identifies its niche (Documenso integrations) and provides explicit trigger guidance with natural user phrases. Its main weakness is that the capability descriptions are somewhat high-level—listing more concrete actions (e.g., 'download signed PDFs', 'redact PII fields', 'configure retention schedules') would strengthen specificity.
Suggestions
Replace high-level phrases like 'handle document data' and 'managing document lifecycle' with more concrete actions such as 'download signed PDFs', 'redact PII from completed documents', or 'configure data retention schedules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Documenso integrations) and mentions some actions like 'managing document lifecycle', 'handling signed PDFs', and 'implementing data retention policies', but these are somewhat high-level rather than listing multiple concrete specific actions (e.g., it doesn't specify extract, download, delete, redact, etc.). | 2 / 3 |
Completeness | The description clearly answers both 'what' (handle document data, signatures, and PII in Documenso integrations) and 'when' (explicit 'Use when' clause with triggers and a 'Trigger with phrases like' section providing concrete activation terms). | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases like 'documenso data', 'signed document', 'document retention', 'documenso PII', and 'download signed pdf'. These are terms users would naturally use and cover multiple variations relevant to the skill's domain. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Documenso-specific integrations with distinct triggers like 'documenso data' and 'documenso PII', making it unlikely to conflict with generic document handling or PDF skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable TypeScript examples covering the full document data handling lifecycle. Its main weaknesses are the lack of validation checkpoints in multi-step workflows (especially around destructive operations like deletion) and the monolithic structure that could benefit from splitting detailed implementations into separate files. The data classification and error handling tables are useful additions.
Suggestions
Add explicit validation/verification steps after critical operations: verify PDF integrity after download (check file size, validate PDF header), confirm S3 upload success, and add retry logic with backoff for retention cleanup deletions.
Split detailed implementations (GDPR handler, S3 archival, retention policy) into separate referenced files, keeping only concise summaries and the lifecycle overview in the main SKILL.md.
Remove the Prerequisites section and obvious PII classification comments (e.g., '// PII — must be protected') — Claude already understands these concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary elements like the Prerequisites section (Claude knows what GDPR is), interface definitions that explain obvious PII classifications via comments, and the overview paragraph restating things Claude would already know. Could be tightened by ~20%. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, real SDK method calls, and concrete patterns. The download, PII sanitization, retention, GDPR handling, and S3 archival examples are all copy-paste ready with specific API endpoints and SDK methods. | 3 / 3 |
Workflow Clarity | The document lifecycle diagram is helpful and steps are sequenced logically. However, there are no explicit validation checkpoints or feedback loops — for example, after downloading a PDF there's no verification of the file integrity, the retention job has no retry logic shown, and the archiveToS3 function doesn't verify upload success. For operations involving deletion (retention cleanup, GDPR erasure), missing validation/verification caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's quite long (~200 lines of code) and could benefit from splitting detailed implementations (GDPR handling, S3 archival) into separate reference files. The references to external resources and next steps are good, but the main file tries to contain everything inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3e83543
- 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.