Agent skill

Docusign Automation

Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management.

MITAuto-check passedProductivity & Automation

Install Docusign Automation

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .claude/skills/docusign-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .claude/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .agents/skills/docusign-automation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .agents/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .cursor/skills/docusign-automation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .cursor/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/davepoon/buildwithclaude.git --path plugins/all-skills/skills/docusign-automation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .gemini/skills/docusign-automation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .gemini/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .github/skills/docusign-automation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .github/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add davepoon/buildwithclaude --skill docusign-automation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install davepoon/buildwithclaude docusign-automation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/all-skills/skills/docusign-automation .opencode/skills/docusign-automation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "docusign-automation" agent skill from https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/docusign-automation into .opencode/skills/docusign-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docusign-automation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: docusign-automation
GitHub stars: 3.6k
Used in: 7 other repos
Token cost: ~2k tokens
SKILL.md length: 825 words
Files: 1
Skills in repo: 246
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management.

Works in 5 steps: Browse and Select Templates → Create and Send Envelopes from Templates → Monitor Envelope Status → …
Tasks that involve App automation through connectors
SKILL.md covers Prerequisites, Setup, Core Workflows and Common Patterns, plus 2 more sections
Reaches rube.app

What it does

Docusign Automation is an agent skill from davepoon/buildwithclaude. Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering App automation through connectors. It works with Composio. The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

When your agent uses it

Tasks that involve App automation through connectors

Example prompts

“/docusign-automation”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Browse and Select Templates
Create and Send Envelopes from Templates
Monitor Envelope Status
Add Templates to Existing Envelopes
Manage Envelope Lifecycle

What it can do on your machine

Read from SKILL.md and the folder at commit 616deb5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- rube.app
Also links to:
- composio.dev
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Docusign Automation loads about 2k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 825 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davepoon/buildwithclaude at commit 616deb5, republished under its MIT licence (© davepoon). 825 words, ~1,984 tokens.

Download SKILL.mdSave it as .claude/skills/docusign-automation/SKILL.md (or your agent's skills folder).

name: docusign-automation
description: Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.
requires.mcp: rube
category: business-productivity

DocuSign Automation via Rube MCP

Automate DocuSign e-signature workflows through Composio's DocuSign toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/docusign

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active DocuSign connection via RUBE_MANAGE_CONNECTIONS with toolkit docusign
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit docusign
If connection is not ACTIVE, follow the returned auth link to complete DocuSign OAuth
Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Browse and Select Templates

When to use: User wants to find available document templates for sending

Tool sequence:

DOCUSIGN_LIST_ALL_TEMPLATES - List all available templates [Required]
DOCUSIGN_GET_TEMPLATE - Get detailed template information [Optional]

Key parameters:

For listing: Optional search/filter parameters
For details: templateId (from list results)
Response includes template templateId, name, description, roles, and fields

Pitfalls:

Template IDs are GUIDs (e.g., '12345678-abcd-1234-efgh-123456789012')
Templates define recipient roles with signing tabs; understand roles before creating envelopes
Large template libraries require pagination; check for continuation tokens
Template access depends on account permissions

2. Create and Send Envelopes from Templates

When to use: User wants to send documents for signature using a pre-built template

Tool sequence:

DOCUSIGN_LIST_ALL_TEMPLATES - Find the template to use [Prerequisite]
DOCUSIGN_GET_TEMPLATE - Review template roles and fields [Optional]
DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE - Create the envelope [Required]
DOCUSIGN_SEND_ENVELOPE - Send the envelope for signing [Required]

Key parameters:

For CREATE_ENVELOPE_FROM_TEMPLATE:
- templateId: Template to use
- templateRoles: Array of role assignments with roleName, name, email
- status: 'created' (draft) or 'sent' (send immediately)
- emailSubject: Custom subject line for the signing email
- emailBlurb: Custom message in the signing email
For SEND_ENVELOPE:
- envelopeId: Envelope ID from creation response

Pitfalls:

templateRoles must match the role names defined in the template exactly (case-sensitive)
Setting status to 'sent' during creation sends immediately; use 'created' for drafts
If status is 'sent' at creation, no need to call SEND_ENVELOPE separately
Each role requires at minimum roleName, name, and email
emailSubject overrides the template's default email subject

3. Monitor Envelope Status

When to use: User wants to check the status of sent envelopes or track signing progress

Tool sequence:

DOCUSIGN_GET_ENVELOPE - Get envelope details and status [Required]

Key parameters:

envelopeId: Envelope identifier (GUID)
Response includes status, recipients, sentDateTime, completedDateTime

Pitfalls:

Envelope statuses: 'created', 'sent', 'delivered', 'signed', 'completed', 'declined', 'voided'
'delivered' means the email was opened, not that the document was signed
'completed' means all recipients have signed
Recipients array shows individual signing status per recipient
Envelope IDs are GUIDs; always resolve from creation or search results

4. Add Templates to Existing Envelopes

When to use: User wants to add additional documents or templates to an existing envelope

Tool sequence:

DOCUSIGN_GET_ENVELOPE - Verify envelope exists and is in draft state [Prerequisite]
DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE - Add template to envelope [Required]

Key parameters:

envelopeId: Target envelope ID
documentId: Document ID within the envelope
templateId: Template to add

Pitfalls:

Envelope must be in 'created' (draft) status to add templates
Cannot add templates to already-sent envelopes
Document IDs are sequential within an envelope (starting from '1')
Adding a template merges its fields and roles into the existing envelope

Show full SKILL.md (286 more words)Show less

5. Manage Envelope Lifecycle

When to use: User wants to send, void, or manage draft envelopes

Tool sequence:

DOCUSIGN_GET_ENVELOPE - Check current envelope status [Prerequisite]
DOCUSIGN_SEND_ENVELOPE - Send a draft envelope [Optional]

Key parameters:

envelopeId: Envelope to manage
For sending: envelope must be in 'created' status with all required recipients

Pitfalls:

Only 'created' (draft) envelopes can be sent
Sent envelopes cannot be unsent; they can only be voided
Voiding an envelope notifies all recipients
All required recipients must have valid email addresses before sending

Common Patterns

ID Resolution

Template name -> Template ID:

1. Call DOCUSIGN_LIST_ALL_TEMPLATES
2. Find template by name in results
3. Extract templateId (GUID format)

Envelope tracking:

1. Store envelopeId from CREATE_ENVELOPE_FROM_TEMPLATE response
2. Call DOCUSIGN_GET_ENVELOPE periodically to check status
3. Check recipient-level status for individual signing progress

Template Role Mapping

When creating an envelope from a template:

1. Call DOCUSIGN_GET_TEMPLATE to see defined roles
2. Map each role to actual recipients:
   {
     "roleName": "Signer 1",     // Must match template role name exactly
     "name": "John Smith",
     "email": "john@example.com"
   }
3. Include ALL required roles in templateRoles array

Envelope Status Flow

created (draft) -> sent -> delivered -> signed -> completed
                       \-> declined
                       \-> voided (by sender)

Known Pitfalls

Template Roles:

Role names are case-sensitive; must match template definition exactly
All required roles must be assigned when creating an envelope
Missing role assignments cause envelope creation to fail

Envelope Status:

'delivered' means email opened, NOT document signed
'completed' is the final successful state (all parties signed)
Status transitions are one-way; cannot revert to previous states

GUIDs:

All DocuSign IDs (templates, envelopes) are GUID format
Always resolve names to GUIDs via list/search endpoints
Do not hardcode GUIDs; they are unique per account

Rate Limits:

DocuSign API has per-account rate limits
Bulk envelope creation should be throttled
Polling envelope status should use reasonable intervals (30-60 seconds)

Response Parsing:

Response data may be nested under data key
Recipient information is nested within envelope response
Date fields use ISO 8601 format
Parse defensively with fallbacks for optional fields

Quick Reference

Task	Tool Slug	Key Params
List templates	DOCUSIGN_LIST_ALL_TEMPLATES	(optional filters)
Get template	DOCUSIGN_GET_TEMPLATE	templateId
Create envelope	DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE	templateId, templateRoles, status
Send envelope	DOCUSIGN_SEND_ENVELOPE	envelopeId
Get envelope status	DOCUSIGN_GET_ENVELOPE	envelopeId
Add template to envelope	DOCUSIGN_ADD_TEMPLATES_TO_DOCUMENT_IN_ENVELOPE	envelopeId, documentId, templateId

Powered by Composio

Files

Just SKILL.md in plugins/all-skills/skills/docusign-automation of davepoon/buildwithclaude.

Open the folder on GitHubat commit 616deb5

Used in 7 other repositories

We found 17 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in davepoon/buildwithclaude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Docusign Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docusign Automation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Docusign Automation this skilldavepoon/buildwithclaude	3.6k	7 repos	~2k	Automated safety check: Pass	MIT	today
Composioyc-software/qm	15k	—	~1.6k	Automated safety check: Pass	MIT	today
Connect Apps with ComposioComposioHQ/awesome-claude-skills	77k	3 repos	~557	Automated safety check: Pass	None	21 days ago
Abuselpdb AutomationComposioHQ/awesome-claude-skills	77k	3 repos	~738	Automated safety check: Pass	None	21 days ago
Accredible Certificates AutomationComposioHQ/awesome-claude-skills	77k	3 repos	~790	Automated safety check: Pass	None	21 days ago
Composio Cloud Toolsquarqlabs/argus	279	—	~543	Automated safety check: Pass	Apache-2.0	4 mo ago

Similar skills

Composio
yc-software/qm
Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet.
15k GitHub stars~1.6k tokensUpdated today
Productivity & AutomationAuto-check passed
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
77k GitHub starsUsed in 3 repos~557 tokens
Productivity & AutomationAuto-check passed
Abuselpdb Automation
ComposioHQ/awesome-claude-skills
Automate Abuselpdb tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
77k GitHub starsUsed in 3 repos~738 tokens
Productivity & AutomationAuto-check passed
Accredible Certificates Automation
ComposioHQ/awesome-claude-skills
Automate Accredible Certificates tasks via Rube MCP (Composio).
77k GitHub starsUsed in 3 repos~790 tokens
Productivity & AutomationAuto-check passed
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
279 GitHub stars~543 tokensUpdated 4 mo ago
Productivity & AutomationAuto-check passed
Active Campaign Automation
ComposioHQ/awesome-claude-skills
Automate ActiveCampaign tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
77k GitHub starsUsed in 3 repos~758 tokens
Productivity & AutomationAuto-check passed

Questions about Docusign Automation

What does Docusign Automation do?

Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Docusign Automation is an agent skill from davepoon/buildwithclaude. Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management.

When should I use Docusign Automation?

Docusign Automation fits situations like: tasks that involve App automation through connectors.

How do I install Docusign Automation in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill docusign-automation -a claude-code`. Or copy the skill folder (plugins/all-skills/skills/docusign-automation in davepoon/buildwithclaude) into .claude/skills/docusign-automation in your project. Claude Code loads it when a task matches its description.

How do I install Docusign Automation in Codex?

Run `npx skills add davepoon/buildwithclaude --skill docusign-automation -a codex`. Or copy the skill folder (plugins/all-skills/skills/docusign-automation in davepoon/buildwithclaude) into .agents/skills/docusign-automation in your project. Codex loads it when a task matches its description.

Can I use Docusign Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill docusign-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docusign-automation, .gemini/skills/docusign-automation, .github/skills/docusign-automation and .opencode/skills/docusign-automation in your project.

What does Docusign Automation need to run?

SKILL.md names no scripts, command-line tools or credentials: Docusign Automation is instructions for the agent only.

Does Docusign Automation access the network?

SKILL.md names 2 domains. In commands or code: rube.app; the agent is likely to contact it when it follows the instructions. As links in the text: composio.dev. This is read from the text; nothing was executed.

Is Docusign Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docusign Automation use?

Docusign Automation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docusign Automation use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Docusign Automation?

Skills that share tags, products or a category with Docusign Automation: Composio (yc-software/qm, 15k stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Abuselpdb Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Accredible Certificates Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docusign Automation?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,605 GitHub stars. The repository holds 246 skills in this directory. The repository was last updated on October 9, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Docusign Automation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DocuSign Automation via Rube MCP

Prerequisites

Setup

Core Workflows

1. Browse and Select Templates

2. Create and Send Envelopes from Templates

3. Monitor Envelope Status

4. Add Templates to Existing Envelopes

5. Manage Envelope Lifecycle

Common Patterns

ID Resolution

Template Role Mapping

Envelope Status Flow

Known Pitfalls

Quick Reference

Files

Used in 7 other repositories

Compare with similar skills

Similar skills

More from davepoon/buildwithclaude

Related

Questions about Docusign Automation