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 solid skill description that clearly identifies its niche (Documenso integrations) and provides explicit trigger guidance with natural user phrases. The main weakness is that the capability descriptions are somewhat high-level—listing more concrete actions (e.g., 'download signed PDFs', 'delete PII fields', 'configure retention schedules') would strengthen specificity. Overall, it performs well on completeness and distinctiveness.
Suggestions
Replace high-level phrases like 'handle document data' and 'managing document lifecycle' with more concrete actions such as 'download signed PDFs', 'redact PII fields', 'configure data retention schedules', or 'retrieve signature status'.
| 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, delete, download, encrypt, 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 for managing document lifecycle, handling signed PDFs, implementing data retention policies, plus explicit trigger phrases). | 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 for destructive operations (draft deletion, GDPR erasure) and the monolithic structure that packs substantial code into a single file. The data classification and error handling tables are useful reference material.
Suggestions
Add explicit validation/confirmation steps before destructive operations (e.g., dry-run mode for retention cleanup, confirmation logging before GDPR erasure)
Handle pagination in the retention and GDPR functions — the code only processes page 1 of results, which the error table acknowledges but doesn't fix
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., the Prerequisites section mentioning 'Understanding of data protection regulations', the Overview paragraph explaining what PostgreSQL is used for). The data classification table and error handling table add value but the overall content is somewhat lengthy for what could be more tightly expressed. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for every step — downloading signed PDFs, sanitizing PII, enforcing retention policies, handling GDPR requests, and archiving to S3. Code is copy-paste ready with proper imports, error handling, and realistic patterns. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the document lifecycle diagram is helpful, but there are no explicit validation checkpoints or feedback loops. For operations involving destructive actions (deleting drafts, GDPR erasure), there's no verify-before-proceeding pattern or dry-run option. The retention enforcement doesn't handle pagination (acknowledged in the error table but not fixed in code). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and tables, but it's a monolithic file with ~200 lines of code that could benefit from splitting (e.g., retention policy, GDPR handling, and S3 archival into separate reference files). The single reference to 'documenso-enterprise-rbac' and external links are appropriate but the main content is heavy for a single SKILL.md. | 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
3a2d27d
- 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.