Contract Review Skill

AI-powered contract review that identifies risky clauses, missing provisions, and compliance issues in legal documents for informed decision-making.

This package contains plausible local contract-review code, but exercise caution before installing or running it: - Do not run fix_json.py as-is. It writes to a hardcoded path (C:/Users/pc/.laosi/skills/contract-review-skill/...), which could overwrite files or create unexpected config in your home directory. If you need the functionality, inspect and modify the path to a safe location (or remove the script). - The batch_reviewer imports a SubAgentManager from a parent path; this dependency is not declared. Confirm you understand what your SubAgent system is and whether you want this skill to create/manage agents. - There are several incoherences/bugs (e.g., the score-to-level mapping appears inverted in batch_reviewer/contract_reviewer). Expect to review the code before trusting its outputs. - Source/homepage metadata is inconsistent (registry shows unknown source; SKILL.md references a GitHub URL). Prefer skills with a clear upstream repository and author identity. - Run the skill in an isolated environment (container or VM) and back up any .laosi or related config directories before first run. Review/grep the code for any other hardcoded paths or writes. If you want, I can point to the exact lines that write the hardcoded path and suggest a safer replacement, or produce a checklist for code review before installation.

Type: OpenClaw Skill Name: contract-review-skill Version: 1.0.4 The skill bundle provides a functional regex-based engine for analyzing legal contracts and identifying risk factors. While the bundle contains development artifacts like 'fix_json.py' and 'test_simple.py' which include hardcoded absolute Windows paths (e.g., 'C:/Users/pc/...'), these appear to be unintentional remnants of the author's local development environment rather than malicious indicators. The core logic in 'review_engine.py' and 'batch_reviewer.py' is strictly limited to file I/O and text processing aligned with the stated purpose, with no evidence of data exfiltration, unauthorized network activity, or command injection vulnerabilities.