Nda

Draft and fill NDA templates — mutual NDA, one-way NDA, confidentiality agreement. Produces signable DOCX files from Common Paper and Bonterms standard forms...

This skill appears coherent for creating NDAs, but pay attention to two practical risks before using it: (1) Remote MCP will send the NDA content to openagreements.ai — only use that path after explicitly telling the user and obtaining informed consent, and avoid sending highly sensitive secrets. (2) If you use the Local CLI path, ensure the agent (or the human operator) strictly enforces the documented sanitization rules: only allow output filenames matching ^[A-Za-z0-9_-]{1,64}\.docx$, reject shell metacharacters and control characters in field values, create a per-run temp file with mktemp + chmod 600, use quoted heredocs when writing values, set a trap to remove temp files, and pin the CLI version (e.g., npm install -g [email protected]). Always preview and manually review the generated document before signing. If you cannot verify that the agent will enforce these safeguards, prefer the preview-only path or perform fills locally yourself with the pinned CLI.

Type: OpenClaw Skill Name: nda Version: 0.2.2 The skill facilitates NDA generation by either transmitting sensitive business data to a third-party endpoint (openagreements.ai) or executing local shell commands via the 'open-agreements' CLI. While SKILL.md and template-filling-execution.md provide detailed defensive instructions for the agent—including mandatory user consent, shell parameter sanitization, and secure temporary file handling—the inherent risks of shell execution and remote processing of confidential legal data meet the threshold for a suspicious classification.