Token导航 LogoToken导航

Agent Skill · 运维和基础设施

legal-risk-scoring(法律风险评分)

legal-risk-scoring 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

legal-risk-scoring 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 1,713。

总安装 423周安装 18GitHub Stars 55下载 148核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:legal-risk-scoring(法律风险评分)
来源仓库:https://github.com/vm0-ai/vm0-skills
仓库路径:skills/legal-risk-scoring
安装命令:
npx skills add https://github.com/vm0-ai/vm0-skills --skill legal-risk-scoring
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/vm0-ai/vm0-skills --skill legal-risk-scoring

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

评估法律风险并输出综合评分与处置建议矩阵。legal-risk-scoring 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。适用于 Codex、Claude 等宿主中处理基础设施类任务。通过 GitHub 安装,依赖本地配置与风险参数定义。使用前需初始化风险偏好阈值与责任人映射表。

维护状态未说明,评分模型可能随政策变化失效。

来源仓库内路径:skills/legal-risk-scoring

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/vm0-ai/vm0-skills --skill legal-risk-scoring;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

legal-risk-scoring 怎么安装?

在终端执行 npx skills add https://github.com/vm0-ai/vm0-skills --skill legal-risk-scoring。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

legal-risk-scoring 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

legal-risk-scoring 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

legal-risk-scoring 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

legal-risk-scoring 用的人多吗?

公开数据是累计安装 423 次,近一周安装 18 次,下载 148 次,GitHub 55 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

legal-risk-scoring 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
legal-risk-scoring

法律风险评分 · 本页

42355需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Scoring Model

Two-Axis Evaluation Grid

Every legal risk is measured across two independent axes:

Impact Magnitude (consequences if the risk becomes reality):

RatingDescriptorMeaning
1TrivialMinimal disruption; no meaningful financial, operational, or reputational consequence. Absorbed within day-to-day operations.
2MinorContained impact; financial exposure under 1% of the relevant contract or transaction value; brief operational hiccup; no public visibility.
3SubstantialTangible impact; financial exposure in the 1-5% range of relevant value; noticeable operational interference; possibility of limited external attention.
4SeriousMajor impact; financial exposure between 5-25% of relevant value; significant operational disruption; probable public scrutiny; potential for regulatory interest.
5SevereExistential-level impact; financial exposure exceeding 25% of relevant value; core business operations threatened; material reputational harm; regulatory action anticipated; potential personal exposure for directors and officers.

Occurrence Probability (how likely the risk is to materialize):

RatingDescriptorMeaning
1NegligibleEssentially theoretical; no known precedent in comparable situations; would demand extraordinary circumstances.
2LowConceivable but not anticipated; sparse precedent; requires specific precipitating events.
3ModeratePlausible; some analogous situations have materialized; precipitating conditions are foreseeable.
4ElevatedExpected to happen; clear precedent exists; precipitating conditions are commonplace in analogous contexts.
5Near CertainVirtually guaranteed; strong historical pattern; precipitating conditions are already present or imminent.

Computing the Score

Risk Score = Impact Magnitude x Occurrence Probability

Score BandCategoryIndicator
1-4Baseline RiskGREEN
5-9Intermediate RiskYELLOW
10-15Elevated RiskORANGE
16-25Acute RiskRED

Visual Grid

                     OCCURRENCE PROBABILITY
               Negligible  Low   Moderate  Elevated  Near Certain
                  (1)      (2)     (3)       (4)        (5)
IMPACT
Severe    (5) |   5    |   10   |   15   |   20   |     25     |
Serious   (4) |   4    |    8   |   12   |   16   |     20     |
Substantial(3)|   3    |    6   |    9   |   12   |     15     |
Minor     (2) |   2    |    4   |    6   |    8   |     10     |
Trivial   (1) |   1    |    2   |    3   |    4   |      5     |

Category Profiles and Response Protocols

GREEN -- Baseline Risk (Score 1-4)

Profile:

  • Low-consequence issues with negligible probability
  • Routine operational risks with well-established controls already in place
  • Familiar risk patterns that the organization regularly manages

Protocol:

  • Accept: Proceed with existing controls in place
  • Log: Enter into the risk register for ongoing visibility
  • Periodic check: Revisit during quarterly or annual review cycles
  • No escalation: The responsible team member manages independently

Typical scenarios:

  • Vendor agreement with a small deviation from preferred terms in a non-material area
  • Standard confidentiality agreement with a reputable counterparty in a familiar jurisdiction
  • Routine administrative compliance task with a clear owner and deadline

YELLOW -- Intermediate Risk (Score 5-9)

Profile:

  • Issues of moderate consequence that could arise under realistic conditions
  • Risks deserving active attention without requiring emergency response
  • Situations where precedent provides a management roadmap

Protocol:

  • Reduce exposure: Deploy targeted controls or negotiate improved terms
  • Active surveillance: Review monthly or upon occurrence of defined trigger events
  • Thorough documentation: Capture the risk, all mitigation steps, and decision rationale in the register
  • Designated owner: A specific individual holds accountability for tracking and mitigation
  • Stakeholder communication: Relevant business contacts are informed of the risk and the mitigation approach
  • Escalation triggers: Define specific conditions that would push this risk to a higher category

Typical scenarios:

  • Agreement with a liability ceiling below the preferred level but within a negotiable range
  • Vendor processing personal data in a territory with uncertain adequacy status
  • Regulatory development that may affect a business line over the medium term
  • IP provision that is broader than optimal but consistent with market practice

ORANGE -- Elevated Risk (Score 10-15)

Profile:

  • Weighty issues with a realistic chance of materializing
  • Risks capable of producing significant financial, operational, or public-facing harm
  • Situations demanding senior-level attention and structured mitigation

Protocol:

  • Senior counsel involvement: Brief the head of legal or designated senior attorney
  • Structured mitigation plan: Build a concrete, time-bound plan to reduce the risk
  • Leadership awareness: Ensure relevant business leaders understand the risk and the recommended path
  • Frequent review: Weekly check-ins or milestone-based reassessment
  • External counsel assessment: Engage outside specialists for domain-specific guidance as warranted
  • Detailed written analysis: Produce a full risk memorandum covering analysis, alternatives, and recommendations
  • Contingency planning: Define the response playbook if the risk materializes

Typical scenarios:

  • Agreement containing uncapped indemnification in a material obligation area
  • Data processing operation that may violate regulatory requirements without restructuring
  • Credible litigation threat from a significant counterparty
  • Intellectual property infringement allegation with a plausible basis
  • Formal regulatory inquiry or audit notification

RED -- Acute Risk (Score 16-25)

Profile:

  • The most consequential issues, with high or near-certain probability of materializing
  • Risks that threaten fundamental business viability, expose officers and directors, or endanger key stakeholders
  • Demands immediate executive engagement and rapid mobilization

Protocol:

  • Immediate executive briefing: Notify General Counsel, C-suite, and Board as the situation warrants
  • Outside counsel retention: Engage specialized external lawyers without delay
  • Dedicated response team: Stand up a cross-functional team with clearly defined roles and authority
  • Insurance notification: Alert carriers where coverage may apply
  • Crisis protocols: Activate crisis management procedures when reputational exposure exists
  • Evidence preservation: Institute a litigation hold if legal proceedings are a possibility
  • Continuous monitoring: Daily or more frequent status reviews until resolved or downgraded
  • Board-level reporting: Include in governance risk reporting as appropriate
  • Regulatory communication: File any mandatory regulatory notifications

Typical scenarios:

  • Pending litigation with substantial financial exposure
  • Personal data breach affecting regulated information
  • Active regulatory enforcement proceeding
  • Material breach of or against the organization under a significant contract
  • Government investigation
  • Infringement claim targeting a core product or revenue-generating service

Formal Documentation Standards

Risk Assessment Memorandum

Every formal evaluation should follow this structure:

## Legal Risk Evaluation

**Prepared**: [date]
**Analyst**: [name of person conducting the evaluation]
**Subject**: [description of the matter under review]
**Privilege designation**: [Yes/No -- mark as attorney-client privileged where applicable]

### 1. Risk Statement
[Precise, concise articulation of the legal risk]

### 2. Factual Background
[Relevant facts, chronology, and business context]

### 3. Scoring Analysis

#### Impact Magnitude: [1-5] - [Descriptor]
[Supporting rationale including potential financial exposure, operational consequences, and reputational dimensions]

#### Occurrence Probability: [1-5] - [Descriptor]
[Supporting rationale including precedent, triggering conditions, and current circumstances]

#### Composite Score: [Number] - [GREEN/YELLOW/ORANGE/RED]

### 4. Aggravating Factors
[Elements that amplify the risk]

### 5. Countervailing Factors
[Elements that dampen the risk or contain exposure]

### 6. Mitigation Alternatives

| Alternative | Effectiveness | Resource Demand | Recommended? |
|---|---|---|---|
| [Option A] | [High/Med/Low] | [High/Med/Low] | [Yes/No] |
| [Option B] | [High/Med/Low] | [High/Med/Low] | [Yes/No] |

### 7. Recommended Course of Action
[Specific recommendation with supporting rationale]

### 8. Post-Mitigation Risk Level
[Projected risk category after implementing recommended measures]

### 9. Ongoing Monitoring Plan
[Frequency and method of review; conditions that would trigger reassessment]

### 10. Immediate Next Steps
1. [Task - Responsible party - Due date]
2. [Task - Responsible party - Due date]

Risk Register Format

For entry into the team's centralized risk tracker:

FieldContent
IdentifierUnique tracking code
Discovery DateWhen the risk first came to light
SummaryBrief characterization
DomainContract / Regulatory / Litigation / IP / Data Privacy / Employment / Corporate / Other
Impact Rating1-5 with descriptor
Probability Rating1-5 with descriptor
Composite ScoreCalculated value
CategoryGREEN / YELLOW / ORANGE / RED
Accountable PersonIndividual responsible for monitoring
Active ControlsMitigations currently deployed
DispositionOpen / Mitigated / Accepted / Closed
Next ReviewScheduled reassessment date
RemarksSupplementary context

Criteria for Engaging Outside Counsel

Situations Requiring External Representation

  • Filed litigation: Any lawsuit brought by or against the organization
  • Government proceedings: Any inquiry from a regulatory agency, government body, or law enforcement
  • Criminal risk: Any scenario involving potential criminal liability for the entity or its people
  • Capital markets implications: Any matter that could affect securities disclosures or regulatory filings
  • Governance-level matters: Any issue necessitating board notification or board-level approval

Situations Strongly Favoring External Engagement

  • Uncharted legal territory: Questions lacking settled authority where the organization's position could establish precedent
  • Multi-jurisdictional complexity: Matters spanning unfamiliar or conflicting legal regimes
  • Outsized financial stakes: Exposure exceeding the organization's defined risk appetite thresholds
  • Specialist knowledge gaps: Subject areas not covered by in-house expertise (antitrust, anti-corruption, patent prosecution, etc.)
  • Major regulatory shifts: New legal frameworks that require compliance program construction or significant adaptation
  • Strategic transactions: Mergers, acquisitions, or major deals requiring diligence, structuring, and regulatory clearance

Situations Worth Evaluating for External Support

  • Significant contractual disputes: Substantial disagreements over interpretation with important business partners
  • Workforce claims: Actual or threatened claims involving discrimination, harassment, wrongful termination, or retaliation
  • Data security events: Incidents that may trigger mandatory notification duties
  • IP conflicts: Infringement allegations (inbound or outbound) involving material products or services
  • Coverage disagreements: Disputes with insurance carriers over claim coverage

Selecting the Right Firm

When recommending outside engagement, prompt the user to weigh:

  • Subject matter depth and track record
  • Familiarity with the relevant jurisdiction
  • Industry sector experience
  • Conflict clearance status
  • Fee structure expectations (hourly, flat, blended, contingency)
  • Firm diversity commitments
  • Pre-existing relationships (panel membership, prior engagements)

平台分布

Codex

33.43%
按下载量换算49

Claude

31.83%
按下载量换算47

Cursor

20.62%
按下载量换算31

Gemini CLI

8.93%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills