agentleFS
Sign inStart free
iblaiiblai/financial-services-agents/skills/docusign/SKILL.md

docusign

Skill15 starsChanged 5 months agoMITView on GitHub

DocuSign electronic signature platform; lets an agent send, track, and retrieve signed documents for client onboarding agreements, advisory contracts, and regulatory disclosures.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the JWT Grant (service-account) OAuth2 flow for automated agent workflows.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DocuSign

What it is

DocuSign is the industry-standard electronic signature and agreement cloud. In financial services, it is used to collect binding client signatures on new account agreements, advisory contracts, Form CRS disclosures, FATCA certifications, and other required documents. DocuSign's audit trail and completion certificates satisfy most regulators' electronic signature requirements.

When to use this skill

  • Send a signature request envelope for a new account agreement or advisory agreement
  • Track envelope status — sent, delivered, completed, declined, or expired
  • Retrieve the signed document and completion certificate for recordkeeping
  • Trigger FATCA re-certification reminders when a W-8 document approaches expiry
  • Confirm Form CRS delivery timestamp and client acknowledgment for examination readiness
  • Void or correct an envelope that was sent with errors

Credentials

This skill authenticates using env vars declared in metadata above. Set them in ~/.openclaw/.env (see .env.example at the config root). Required variables:

  • DOCUSIGN_INTEGRATION_KEY - DocuSign app integration key (client ID)
  • DOCUSIGN_SECRET_KEY - OAuth2 client secret for the integration key
  • DOCUSIGN_ACCOUNT_ID - DocuSign account ID (GUID)
  • DOCUSIGN_BASE_URL - REST API base URL (e.g. https://na3.docusign.net/restapi)
  • DOCUSIGN_IMPERSONATED_USER_ID - User GUID for JWT impersonation (service account)

Key operations

  • POST /v2.1/accounts/{accountId}/envelopes — create and send a new signature envelope
  • GET /v2.1/accounts/{accountId}/envelopes/{envelopeId} — retrieve envelope status and metadata
  • GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents — list documents in an envelope
  • GET /v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId} — download a signed document
  • PUT /v2.1/accounts/{accountId}/envelopes/{envelopeId} — void or resend an existing envelope
  • GET /v2.1/accounts/{accountId}/envelopes?status=completed&from_date=... — list completed envelopes by date range

Notes

  • Use the JWT Grant (service-account) OAuth2 flow for automated agent workflows; avoid password-based auth
  • Demo/sandbox environment uses https://demo.docusign.net/restapi; production and demo credentials are separate
  • Envelope creation counts against monthly plan limits; monitor usage to avoid overage charges
  • Completed documents and audit trails are available for 10 years by default; confirm retention policy with your DocuSign admin
  • ESIGN Act and eIDAS compliance is satisfied out of the box; verify local requirements for international signatories

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free