Mova Contract Writer

Translate a pre-contract (output of mova-intent-calibration) into a complete, valid MOVA contract — envelope, data schema references, instruction profile, an...

This skill appears to perform the advertised translation work, but the SKILL.md explicitly expects a local MOVA spec at /home/mova/.openclaw/workspace/mova-spec/ for validation while the published metadata lists no required config paths. Before installing or using the skill: (1) confirm where the MOVA spec is expected to live and whether the agent will be allowed to read that path; (2) if you don't want the agent to access host files, ask the author to make schema validation optional or allow providing the spec as an uploaded artifact; (3) avoid pasting any sensitive secrets into the pre-contract you provide, and inspect the remainder of SKILL.md (it was truncated here) to ensure it doesn't later instruct network submissions or other file reads; (4) request that the author update the metadata to declare the required config path (or remove the hardcoded path) so the skill's declared requirements match its runtime behavior. Providing the full SKILL.md or clarification from the author would raise confidence and could change this assessment to benign.

Type: OpenClaw Skill Name: mova-contract-writer Version: 1.0.0 The skill is a template-based generator for 'MOVA contracts' (structured JSON) based on user-provided 'pre-contracts'. It follows a well-defined mapping logic, includes mandatory human-in-the-loop review steps for each artifact, and restricts its filesystem access to a specific workspace directory (/home/mova/.openclaw/workspace/mova-spec/) for schema validation, showing no signs of malicious intent or data exfiltration.