SkillAgentSearch skills...

docusign

DocuSign eSignature: draft and send signature envelopes (demo env default), check envelope status, download signed documents. Trigger phrases: docusign, send for signature, signature envelope, envelope status, signed document.

Install / Use

npx skills add Anil-matcha/awesome-muse-connectors --skill docusign

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Tags

Our assessment of docusign

docusign scores 83/100 on our quality scale, 938th of 1,177 Content & Media skills we index.

Its SKILL.md is 4.2 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,321 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 7 days ago, so docusign is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

docusign compared with similar skills

All 4 of these similar skills score higher than docusign; compare them before choosing.

SkillScoreStarsUpdatedFormat
docusign (this skill)by Anil-matcha831.3k7d agoSKILL.md
siyuanby siyuan-note10046.7ktodayMCP Server
algorithmic-artby anthropics100177.9k20d agoSKILL.md
pptxby anthropics100177.9k20d agoSKILL.md
designby nextlevelbuilder100133.6k9d agoSKILL.md

Frequently asked questions

How do I install docusign?
Run npx skills add Anil-matcha/awesome-muse-connectors --skill docusign. The install tabs above show the steps for each supported agent.
Which AI agents does docusign work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is docusign safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is docusign still maintained?
The repository was last updated 7 days ago, so docusign is actively maintained.

name: "docusign" description: "DocuSign eSignature: draft and send signature envelopes (demo env default), check envelope status, download signed documents. Trigger phrases: docusign, send for signature, signature envelope, envelope status, signed document." metadata: { "includeInPrompt": true } tagline: "Draft and send signature envelopes (demo environment by default), check envelope status, and download signed documents." catalog_auth: "OAuth 2.0 Authorization Code Grant (per-user)" catalog_hosts: ["demo.docusign.net", "docusign.net"]

DocuSign

Purpose

Work with DocuSign's eSignature REST API v2.1: list envelopes, fetch envelope details and recipient status, prepare DRAFT envelopes (never sent automatically), send a draft envelope to signers, and download envelope documents. Every command runs against the demo environment unless you pass --env prod: demo.docusign.net sends no legally effective documents. Reach for this when the user needs to prepare, send, or track a DocuSign signature request.

Tooling

All commands go through bin/docusign.py. Demo is the default (--env demo); add --env prod for production:

bin/docusign.py auth                                  # verify OAuth; list accounts
bin/docusign.py envelopes --from-date 2026-09-01      # list envelopes
bin/docusign.py envelope-get --envelope-id ENV_ID     # envelope details
bin/docusign.py envelope-status --envelope-id ENV_ID  # status + recipient state
bin/docusign.py envelope-create --file envelope.json \
    --confirm "create DRAFT envelope from envelope.json"   # DRAFT only
bin/docusign.py envelope-send --envelope-id ENV_ID \
    --confirm "send envelope ENV_ID to signers (legally binding signature request)"
                                                      # HIGH: has legal effect
bin/docusign.py document-download --envelope-id ENV_ID \
    --document-id combined --out signed.pdf           # download documents

envelope-create takes a DocuSign envelope definition in JSON and forces "status": "created" so it always lands as a draft. --document-id combined downloads the full envelope as one file. --account-id overrides the default account from /oauth/userinfo on any command that needs one.

Auth

  • Provider id: docusign (credential is collected as custom.docusign)
  • Collection: OAuth 2.0 Authorization Code Grant via the secure credential flow (credentials.request_api_access); the integration key must be registered in the DocuSign Apps and Keys page. The runtime performs the token exchange/refresh and hands the CLI a fresh Bearer token.
  • Required scopes: signature, extended. Honesty flag: this scope list is taken from DocuSign's public OAuth docs and has not been verified in a live flow.
  • Allowed hosts: demo.docusign.net, docusign.net, account.docusign.com
  • Account discovery: the CLI resolves the account id and base URI from account.docusign.com/oauth/userinfo (the user's default account, or --account-id). Honesty flag: this discovery flow is taken from DocuSign's public docs and is provisional; if it fails, pass --account-id explicitly.
  • Status check: bin/docusign.py auth

Operating Rules

  1. Demo is the default and is mandatory for testing. Never run a first-time flow against --env prod. The CLI cross-checks --env against the account's base URI and refuses a demo/prod mismatch.
  2. Sending is HIGH and has legal effect. envelope-send requires --confirm with the exact string the CLI echoes, which names the legal effect, on every call, in demo and in production. The refusal text states it plainly: sending an envelope to signers creates a legally binding signature request.
  3. Creating is a DRAFT only. envelope-create needs --confirm on every call too, but it never notifies signers; nothing becomes legally effective until envelope-send.
  4. Show the exact confirmation string to the user before they run a send, so there is no ambiguity about what they are approving.
  5. Never exfiltrate the credential: the CLI only ever handles surrogates (see bin/docusign.py). Do not print, log, or transmit the token.

Files

  • SKILL.md
  • bin/docusign.py

Maturity

Draft: written from DocuSign's public eSignature REST API v2.1 docs; not yet live-tested end-to-end.

Related Skills

View on GitHub
GitHub Stars1.3k
CategoryContent
Updated7d ago
Forks305

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions