ClawHub

Contract Signing Workflow Assistant

v1.0.0

Design a practical contract-signing workflow with Nota Sign. Use this skill when the user needs steps for approvals, signer roles, signing order, recipient v...

⭐ 0· 113·0 current·0 all-time
by@notasign

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for notasign/contract-signing.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Contract Signing Workflow Assistant" (notasign/contract-signing) from ClawHub.
Skill page: https://clawhub.ai/notasign/contract-signing
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install contract-signing

ClawHub CLI

Package manager switcher

npx clawhub@latest install contract-signing
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description ask for contract-signing workflows and the SKILL.md contains only workflow design steps, templates, checklists, and role definitions — all consistent with the stated purpose.
✓
Instruction Scope
Runtime instructions are limited to asking the assistant to identify parties, roles, signing order, verification needs, templates, and recordkeeping; there are no directives to read local files, access environment variables, call external endpoints, or transmit data.
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing is written to disk or downloaded during install.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no requests for secrets or unrelated service tokens.
✓
Persistence & Privilege
always is false and the skill does not request persistent presence or elevated privileges. Autonomous model invocation is allowed by default but this skill's instructions do not leverage it to access extra system resources.
Assessment
This is an instruction-only helper for designing contract-signing workflows and appears coherent and low-risk: it does not install software or ask for credentials. Before installing or using it, remember: (1) it is not legal advice — have a lawyer review contracts; (2) do not paste sensitive credentials or full confidential documents into the chat; (3) the skill's source is listed as "unknown" in the metadata — if provenance matters for your organization, verify the publisher or prefer a skill from a known vendor; (4) because the platform allows autonomous invocation by default, review what prompts you allow the agent to run automatically, but in this case there are no broad permissions requested.

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

Runtime requirements

📄 Clawdis
latestvk978drzkth4384vbnw9ynzwsd1844m6c
113downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0
@notasign
latest
Download

Contract Signing Workflow Assistant

Use this skill when the user wants a clear contract-signing workflow rather than a generic explanation of eSignature.

Core Job

Help the user:

  • design a contract-signing workflow
  • define who approves and who signs
  • decide whether sequential signing is required
  • decide whether recipient verification is needed
  • recommend templates for repeated agreements
  • add recordkeeping through audit trail and document history

When to Use

Use this skill when the user asks for:

  • a sales contract signing process
  • an NDA or vendor agreement workflow
  • an offer letter or HR agreement signing flow
  • approval before signature
  • signer and approver role design
  • a checklist before sending a contract

How to Respond

  1. Identify the contract type and business owner.
  2. List all parties involved: sender, approver, signer, observer, or admin.
  3. Decide whether the process is parallel or sequential.
  4. Recommend recipient verification only when the document risk justifies it.
  5. Suggest templates if the agreement is repeated often.
  6. Keep the answer actionable and organized.

Recommended Output Formats

  • step-by-step workflow
  • approver/signer role table
  • pre-send checklist
  • workflow summary for internal teams
  • risk and assurance recommendation

Contract Workflow Template

Use this structure unless the user asks for another format:

  1. Document type
  2. Business owner
  3. Approver roles
  4. Signer roles
  5. Signing order
  6. Verification requirement
  7. Template recommendation
  8. Recordkeeping plan
  9. Sending checklist

Usage Examples

Example 1

User: I need a signing workflow for a sales contract that needs manager approval first.

Assistant:

  1. Document type: sales contract
  2. Business owner: sales operations
  3. Approver role: sales manager
  4. Signer roles: customer signer and internal authorized signer if required
  5. Signing order: manager approval first, then customer signature
  6. Verification: add only if customer identity assurance is required
  7. Template: yes if the contract is reused frequently
  8. Recordkeeping: keep audit trail and signed document history
  9. Sending checklist: verify names, emails, sign fields, and deadlines

Example 2

User: Build a workflow for procurement agreements with multiple signers.

Assistant:

  • Define internal approver roles first
  • List each supplier-side signer
  • Decide whether signers can act in parallel or must follow an order
  • Reuse a template for repeated agreement structures
  • Track completion through audit trail and envelope management

Boundaries

This skill designs workflows and checklists. It does not provide legal advice or execute contracts automatically.

Comments

Loading comments...