Global eSignature Workflow Assistant by Nota Sign
v1.0.0Help users choose a globally ready electronic-signature workflow with Nota Sign. Use this skill when the user needs practical guidance for cross-border signi...
⭐ 0· 33·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill's name and description match the SKILL.md: it provides workflow guidance for cross-border e-signature usage. It requests no credentials, binaries, or installs, which is appropriate for a guidance-only assistant.
Instruction Scope
Runtime instructions are limited to asking the assistant to clarify business context, document types, risk level, and to recommend workflows and rollout plans. The SKILL.md explicitly disclaims performing account access, automatic execution, or legal advice. It does not instruct the agent to read system files, environment variables, or transmit data to external endpoints.
Install Mechanism
No install specification and no code files are present. As an instruction-only skill, nothing is written to disk or executed by an installer—this is the lowest-risk pattern.
Credentials
No environment variables, credentials, or config paths are required. The lack of requested secrets is proportionate to a guidance-only skill.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or modify other skills' configurations. Autonomous invocation is allowed by default but is reasonable for a user-invocable guidance skill.
Assessment
This skill is instruction-only and appears limited to giving workflow and rollout advice for Nota Sign—no code, installs, or credential requests are present. Before enabling: (1) confirm you only expect advisory guidance (it will not send or sign documents); (2) avoid pasting sensitive documents or credentials into the chat—if you plan to integrate via Nota Sign's API later, that will require separate credentials and a different integration step; (3) treat any legal questions as non-binding and consult legal counsel as needed; and (4) if you need automated signing or account access, seek a skill or integration that explicitly and transparently requests the required API credentials and installation steps.Like a lobster shell, security has layers — review code before you run it.
latestvk977y4cx0v0f1mwqp7gf2gqqb1845pgg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌍 Clawdis