Automate DocuSign tasks via Rube MCP (Composio): templates, envelopes, signatures, document management. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill docusign-automation65
Quality
51%
Does it follow best practices?
Impact
88%
2.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/docusign-automation/SKILL.mdTemplate-based envelope creation workflow
RUBE_SEARCH_TOOLS first
0%
100%
Connection verification
0%
100%
Dynamic template ID resolution
50%
100%
Template role inspection
0%
100%
templateRoles required fields
50%
100%
Case-sensitive role names
100%
100%
Draft vs send status logic
100%
100%
No redundant send call
100%
100%
Response parsing via data key
0%
100%
All required roles assigned
40%
100%
Without context: $1.2106 · 4m 43s · 43 turns · 49 in / 13,508 out tokens
With context: $0.5705 · 2m 39s · 20 turns · 24 in / 9,371 out tokens
Envelope status monitoring and interpretation
Delivered != signed
100%
100%
Completed = all signed
100%
100%
Full status enumeration
100%
100%
One-way status transitions
37%
100%
No hardcoded GUIDs
0%
30%
RUBE_SEARCH_TOOLS first
0%
0%
Polling interval guidance
0%
100%
Nested data key handling
70%
100%
Recipient-level status
0%
100%
Connection verification
0%
0%
Without context: $0.8479 · 3m 20s · 33 turns · 38 in / 9,416 out tokens
With context: $0.6826 · 3m 20s · 23 turns · 28 in / 11,551 out tokens
Multi-document envelope assembly and lifecycle management
Get envelope before add
75%
100%
Draft-only modification rule
90%
100%
Sequential document IDs
16%
100%
Void notification warning
100%
100%
Send precondition
90%
100%
RUBE_SEARCH_TOOLS first
12%
0%
Connection verification
0%
100%
Dynamic template ID lookup
0%
100%
Sent cannot be unsent note
50%
100%
Response defensive parsing
50%
100%
Without context: $0.4914 · 2m 30s · 25 turns · 29 in / 8,818 out tokens
With context: $0.4860 · 2m 5s · 20 turns · 25 in / 7,477 out tokens
Table of Contents
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.