From documenso-pack
Implement Documenso document creation and recipient management workflows. Use when creating documents, managing recipients, adding signature fields, or building signing workflows with Documenso. Trigger with phrases like "documenso document", "create document", "add recipient", "documenso signer", "signature field".
How this skill is triggered — by the user, by Claude, or both
Slash command
/documenso-pack:documenso-core-workflow-aThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Complete workflow for creating documents, managing recipients, and configuring signature fields in Documenso.
Complete workflow for creating documents, managing recipients, and configuring signature fields in Documenso.
documenso-install-auth setupdocumenso-sdk-patternsimport { Documenso } from "@documenso/sdk-typescript";
Implement recipient roles.
Implement field positioning tips.
For detailed implementation code and configurations, load the reference guide:
Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)
| Error | Cause | Solution |
|---|---|---|
| Document not found | Invalid ID | Verify document exists |
| Recipient exists | Duplicate email | Update existing recipient |
| Invalid field position | Off-page coordinates | Check page dimensions |
| Cannot modify sent doc | Document already sent | Create new version |
| File too large | PDF exceeds limit | Compress or split PDF |
For template-based workflows, see documenso-core-workflow-b.
Basic usage: Apply documenso core workflow a to a standard project setup with default configuration options.
Advanced scenario: Customize documenso core workflow a for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub bulozb/claude-code-plugins-plus-skills --plugin documenso-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026