Docusign

CommunityPopular

Anil-matcha

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.

Overview

Publisher	Anil-matcha
Repository	`awesome-muse-connectors`
Skill name	`docusign`
Stars	1.4K
Forks	309
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Anil-matcha on GitHub. Read the source before you install it.

Installation

Install the Docusign AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/docusign
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Anil-matcha/awesome-muse-connectors.git /tmp/awesome-muse-connectors
mkdir -p .claude/skills
cp -r /tmp/awesome-muse-connectors/connectors/docusign .claude/skills/docusign

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Docusign in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Docusign on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Docusign is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

bash
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

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.
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.
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.
Show the exact confirmation string to the user before they run a send, so there is no ambiguity about what they are approving.
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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

bin/docusign.py12 KB

Frequently asked questions

What does the Docusign AI skill do?

Why use Docusign on TypingMind?

Because you install it once and use it with any model. Docusign is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Docusign in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Anil-matcha/awesome-muse-connectors/tree/main/connectors/docusign. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Docusign?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Docusign?

As many as you like. As long as a model supports skills, you can use Docusign with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Docusign AI skill free?

Yes. It is published on GitHub by Anil-matcha under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Cloud Image Bake

openclaw

OrganizationPopular

Bake, select, prove, and safely retire a Cloud Worker image with crabbox and config one-liners.

Acp Router

Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw…

Diffs

Use the diffs tool to produce real, shareable diffs (viewer URL, file artifact, or both) instead of manual edit summaries.

Feishu Doc

Feishu document read/write workflows. Activate when the user mentions Feishu docs, cloud docs, or docx links.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

DocuSign

Purpose

Tooling

Auth

Operating Rules

Files

Maturity

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now