← Back to Skills Marketplace
golngod

胡田-OPC导师-合同风险审查

by golngod · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
33
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install opc-contract-risk
Description
基于19份HNB合同三审实战案例提炼的合同风险审查工具,采用三审机制(合规性→商业性→执行性)逐条扫描,100%复用率验证。专为OPC/中小企业设计,零法律背景也能用。
README (SKILL.md)

胡田-OPC导师-合同风险审查

技能描述

基于19份HNB合同三审实战案例提炼的合同风险审查工具,采用三审机制(合规性→商业性→执行性)逐条扫描,100%复用率验证。专为OPC/中小企业设计,零法律背景也能用。

触发条件

  • 用户需要审查合同风险
  • 用户签订商务/技术/投资合同前
  • 用户遇到合同纠纷需要复盘
  • 用户需要合同条款风险评估

核心能力

1. 合同三审机制(HNB实战验证)

审查层级 关注点 权重 典型风险
一审:合规性 法律效力、主体资格、权限范围 40% 无效条款、超授权签约
二审:商业性 权利义务平衡、价格条款、违约责任 35% 单方免责、隐性成本
三审:执行性 交付标准、验收流程、争议解决 25% 模糊标准、执行障碍

2. 六类高频风险识别

  1. 付款陷阱:预付比例过高/付款条件模糊/无退款机制
  2. 交付黑洞:验收标准模糊/无里程碑/变更无约束
  3. 违约失衡:单方违约金/赔偿上限过低/间接损失免责
  4. 知识产权:权属约定不清/竞业限制过宽/许可范围模糊
  5. 终止条款:单方解除权/终止后义务/过渡期安排
  6. 争议解决:管辖约定/仲裁vs诉讼/跨境执行

3. 风险评级体系

  • 🟢 低风险:条款平衡,可签署
  • 🟡 中风险:存在不对等条款,建议修改后签署
  • 🟠 高风险:重大风险条款,必须修改
  • 🔴 极高风险:存在致命缺陷,建议不签署

4. 修改建议模板

  • 原条款 → 风险点 → 修改建议 → 修改后条款
  • 谈判策略:哪些必须改/哪些可以谈/哪些可以接受

HNB实战案例(19份合同验证)

  • 合同类型分布:技术服务6份/采购4份/合作协议3份/投资协议2份/劳动合同2份/租赁2份
  • 三审机制识别风险项:合计87个,平均每份4.6个
  • 高风险项占比:23%(需修改后签署)
  • 复用率:100%(所有合同类型均适用)

OPC专属建议

  • 一人公司签合同前必做三审,1小时省10万纠纷
  • 重点关注:付款条款+知识产权+终止条款
  • 用AI初筛+人工复核,效率提升5-10倍
  • 免费合同模板≠安全合同,必须逐条审查

输出格式

  • 三审风险报告(合规→商业→执行逐条)
  • 风险评级总览(🟢🟡🟠🔴标记)
  • 修改建议清单(原条款→修改建议→修改后条款)
  • 谈判策略建议
Usage Guidance
Install this only if you want Chinese-language contract review assistance. Treat its output as preliminary risk-spotting, not legal advice, and avoid pasting contracts that contain confidential, regulated, or third-party-sensitive information unless you are permitted to process them in your agent environment.
Capability Assessment
Purpose & Capability
The described capability is contract risk review and clause analysis, which is coherent with the contract-focused purpose; no artifact-backed evidence shows unrelated authority or automatic legal/business actions.
Instruction Scope
SkillSpector’s broad-trigger concern is valid as usability guidance, but the reported scope still stays within contract-related review rather than hidden or purpose-mismatched behavior.
Install Mechanism
The supplied evidence only identifies SKILL.md concerns and does not show installer scripts, executable payloads, package installs, or obfuscated setup behavior.
Credentials
Contract review may involve sensitive legal or business text, so users should provide only documents they are allowed to share; no supplied evidence shows network transmission, credential use, or external account access.
Persistence & Privilege
No supplied artifact or scanner evidence indicates local persistence, background workers, privilege escalation, broad indexing, credential harvesting, or destructive actions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install opc-contract-risk
  3. After installation, invoke the skill by name or use /opc-contract-risk
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
opc-contract-risk 1.0.0 - 合同三审机制(合规性→商业性→执行性) - 六类高频风险识别(付款陷阱、交付黑洞、违约失衡等) - 风险评级体系(绿/黄/红) - 基于HNB 19份实战案例验证
Metadata
Slug opc-contract-risk
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is 胡田-OPC导师-合同风险审查?

基于19份HNB合同三审实战案例提炼的合同风险审查工具,采用三审机制(合规性→商业性→执行性)逐条扫描,100%复用率验证。专为OPC/中小企业设计,零法律背景也能用。 It is an AI Agent Skill for Claude Code / OpenClaw, with 33 downloads so far.

How do I install 胡田-OPC导师-合同风险审查?

Run "/install opc-contract-risk" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is 胡田-OPC导师-合同风险审查 free?

Yes, 胡田-OPC导师-合同风险审查 is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does 胡田-OPC导师-合同风险审查 support?

胡田-OPC导师-合同风险审查 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created 胡田-OPC导师-合同风险审查?

It is built and maintained by golngod (@golngod); the current version is v1.0.0.

💬 Comments