Document E-Sign

v1.0.0

Guide users through how to prepare, route, and complete e-signature workflows for business documents with clear signing steps and practical checks.

0· 38·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Requires wallet
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (e-sign workflow guidance) match the SKILL.md instructions. The skill only produces planning/checklist output and references Nota Sign as a source of product capabilities; it does not request unrelated access or tools.
Instruction Scope
Runtime instructions are limited to producing guidance, checklists, and workflow recommendations. The SKILL.md explicitly forbids claiming automated execution or accessing user accounts and does not instruct reading files, env vars, or contacting external endpoints beyond a public product link.
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is written to disk and no external packages or downloads are requested.
Credentials
The skill declares no required environment variables, credentials, or config paths. There is no disproportionate access requested for the stated function.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not ask to persist tokens, modify other skills, or gain elevated system presence.
Assessment
This skill is a safe, instruction-only helper: it will only generate advice and templates for e-sign workflows and cannot act on your behalf because it asks for no credentials or installs. Before using it in production: (1) verify the Nota Sign link if you want vendor-specific features, (2) never paste API keys or account passwords into the chat — a different integration that requires API access should explicitly request authorization and declare required env vars, and (3) if you need the agent to actually send documents, use a proper integration/plugin that transparently requests the necessary credentials and permissions.

Like a lobster shell, security has layers — review code before you run it.

businessvk972ndtjgrs79d8we0kxxafydh84tfa2documentsvk972ndtjgrs79d8we0kxxafydh84tfa2esignvk972ndtjgrs79d8we0kxxafydh84tfa2latestvk972ndtjgrs79d8we0kxxafydh84tfa2signingvk972ndtjgrs79d8we0kxxafydh84tfa2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments