Vendor Contracts
v1.0.0Pragmatic review of software contracts: IP, liability, SLAs. Use when triaging vendor agreements (not legal advice).
⭐ 0· 63·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (vendor contract review) match the SKILL.md: the instructions provide a staged, pragmatic review process (clarify context, structure topics, draft red‑flags, verify). No unexpected binaries, env vars, or external services are required.
Instruction Scope
Instructions stay on-topic: they guide question gathering, checklists, risk flagging, and procedural handoffs. They explicitly avoid giving definitive legal advice. The doc may ask the user for contract context or excerpts — reasonable for the task, but any pasted contract text could contain sensitive info (user caution advised).
Install Mechanism
No install spec and no code files — lowest-risk model. Nothing is written to disk or downloaded by the skill.
Credentials
The skill declares no environment variables, credentials, or config paths. It does not request unrelated secrets or broad access; required capability is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill is user-invocable — normal settings. The skill does not request persistent system privileges or modifications to other skills or agent configuration.
Assessment
This skill appears coherent and low-risk: it provides a structured checklist-based workflow for reviewing vendor contracts and does not ask for credentials or install code. Before using it, remember: (1) the assistant is not a lawyer — treat outputs as triage guidance, not legal advice, and confirm critical items with counsel; (2) avoid pasting confidential secrets or corporate credentials into the chat — redact or summarize sensitive clauses where possible; (3) if you expect the review to require legal or security teams, plan the handoffs the skill recommends; and (4) if you want the model to act on real contract files, prefer sharing minimal necessary excerpts and explicitly note any confidentiality requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk97bmrhh0z0pt6ft9hkvc305x983pv26
License
MIT-0
Free to use, modify, and redistribute. No attribution required.