Mova Contract Generation
v1.0.1Generate a legal document draft (NDA, service agreement, supply contract, SLA) from a structured template via MOVA HITL, with section-by-section human review...
⭐ 0· 96·0 current·0 all-time
bySergii Miasoiedov@mova-compact
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description, declared behavior, and tool calls all describe an HITL contract drafting workflow that uses a MOVA plugin and MOVA APIs — the requested capabilities line up with the stated purpose.
Instruction Scope
Instructions are limited to: collecting contract parameters, invoking mova_hitl_start_contract_gen and mova_hitl_decide tooling, presenting AI-drafted sections for human review, and storing results. They explicitly send contract data to MOVA services, which is appropriate for this skill's function.
Install Mechanism
Instruction-only skill with no install spec or code files; lower risk. The SKILL.md notes the openclaw-mova plugin is required (install via openclaw plugins install openclaw-mova), which is a reasonable external dependency.
Credentials
The skill itself declares no env vars or local file access, which is proportionate. Note: the skill sends party and contract data to api.mova-lab.eu and other connectors; authentication and credentials are likely managed by the separate openclaw-mova plugin (not declared here). Verify the plugin’s credential requirements and storage policies before use.
Persistence & Privilege
always:false and user-invocable:true; the skill does not request permanent presence or modify other skills. It describes storing finalized documents in a repository and an audit trail, which is consistent with its purpose.
Assessment
This skill appears coherent for MOVA HITL contract drafting, but before installing: 1) Confirm and inspect the openclaw-mova plugin (install command is provided) — verify its source, permissions, and how it authenticates to MOVA. 2) Understand data flows: party names, contract content, and reviewer metadata will be sent to api.mova-lab.eu and stored in configured repositories; ensure this complies with your privacy/retention policies and any jurisdictional rules. 3) Confirm where finalized documents and audit journals are stored, who can access them, and whether data-at-rest is encrypted. 4) Require that human legal reviewers complete sign-off (the skill notes this) before treating any draft as final. If you need higher assurance, request the plugin’s code or documentation and the MOVA service’s privacy/security documentation before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97a34yqwbh0z8c7xxdv1fxaa9842d40
License
MIT-0
Free to use, modify, and redistribute. No attribution required.