ClawHub

Legal Guard

v1.2.0

Prevents autonomous signing of legal agreements or contracts. Use when an agent identifies a request or document related to signatures (DocuSign, HelloSign,...

⭐ 0· 88·0 current·0 all-time
by@echoofzion
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (preventing autonomous signing) align with the SKILL.md: there are no unrelated env vars, binaries, or installs requested and the actions described (intercept, summarize, require /approve) match the stated goal.
✓
Instruction Scope
Runtime instructions stay within the stated scope: stop before signing, extract a concise executive summary of contract terms, surface expiry timers, require a specific `/approve` command, and record approval IDs. The instructions assume the agent has document/web-interaction capabilities (expected for a skill of this type) but do not ask for unrelated files, system paths, or credentials.
✓
Install Mechanism
Instruction-only skill with no install spec or code files — nothing is downloaded or written to disk and no external packages are requested.
✓
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets or elevated access.
✓
Persistence & Privilege
Skill is not marked always:true and does not request persistent/system-wide configuration changes. It relies on the platform's normal approval flow (`/approve`), which is appropriate for its function.
Assessment
This skill appears coherent and aligned with its stated purpose. Before installing: (1) confirm you trust the skill source (owner/publisher) because the skill will instruct your agent to intercept and present potentially sensitive contract contents; (2) verify your OpenClaw deployment actually implements the `/approve <id>` workflow the skill expects; (3) review how and where the agent will present executive summaries (the README mentions Telegram as an example) to ensure summaries aren't leaked to external channels you don't control; and (4) test the skill in a safe environment to confirm it halts signing flows and waits for the formal `/approve` command as documented.

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

latestvk977s3562ks42e96bybbq48sw183kzz7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments