Token导航 LogoToken导航

Agent Skill · 开发

legal-risk-assessment(法律风险评估)

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

legal-risk-assessment 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为可写文件;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 16,891。

总安装 461周安装 19GitHub Stars 103下载 150核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill legal-risk-assessment

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

legal-risk-assessment 使用五乘五矩阵量化法律风险,生成评估报告与升级指引。适用于法务或合规团队进行决策支持,但不可替代专业法律意见。通过 npx skills add 从 GitHub 安装,具体工具与限制见仓库说明。安装前请确认权限范围与维护状态,注意实验性质与责任归属。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

legal-risk-assessment 怎么安装?

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

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

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

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

权限级别是可写文件。该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

legal-risk-assessment 是免费的吗?

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

legal-risk-assessment 用的人多吗?

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

legal-risk-assessment 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
legal-risk-assessment

法律风险评估 · 本页

461103可写文件未明确通过

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

SKILL.md 原文

⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

Legal Risk Assessment

Structured legal risk assessment using a quantitative 5x5 Severity x Likelihood matrix. Scores risks, maintains registers, generates assessment memos, and guides escalation decisions.


Table of Contents

- Risk Scorer - Risk Report Generator


Tools

Risk Scorer

Calculates risk scores from severity and likelihood inputs, assigns color-coded risk levels, and generates summary statistics.

# Score a single risk
python scripts/risk_scorer.py --severity 4 --likelihood 3 \
  --category "Contract" --description "Vendor SLA non-compliance"

# JSON output
python scripts/risk_scorer.py --severity 4 --likelihood 3 \
  --category "Contract" --description "Vendor SLA breach" --json

# Batch mode from risk register file
python scripts/risk_scorer.py --input risks.json --json

# Batch mode with human-readable output
python scripts/risk_scorer.py --input risks.json

Input JSON format (batch mode):

{
  "risks": [
    {"severity": 4, "likelihood": 3, "category": "Contract", "description": "Vendor SLA breach"},
    {"severity": 2, "likelihood": 2, "category": "Regulatory", "description": "Minor filing delay"}
  ]
}

Output includes:

  • Risk score (Severity x Likelihood)
  • Color-coded level (GREEN / YELLOW / ORANGE / RED)
  • Recommended action (Accept / Monitor / Mitigate / Escalate)
  • Batch summary statistics (count per level, average score)

Risk Report Generator

Generates a formatted risk assessment memo in markdown from a risk register JSON file.

# Generate memo from risk register
python scripts/risk_report_generator.py --input risk_register.json

# Save to file
python scripts/risk_report_generator.py --input risk_register.json --output memo.md

# JSON metadata output
python scripts/risk_report_generator.py --input risk_register.json --json

Report includes:

  • ASCII risk matrix visualization
  • Risk distribution summary (counts and percentages per level)
  • Top risks ranked by score
  • Recommended actions per risk with owner assignments
  • Monitoring plan suggestions
  • Escalation recommendations

Reference Guides

Risk Framework

references/risk_framework.md

Complete Severity x Likelihood matrix reference:

  • Severity levels 1-5 with financial exposure percentages
  • Likelihood levels 1-5 with probability ranges
  • Risk matrix visualization
  • Risk classification (GREEN/YELLOW/ORANGE/RED) with actions
  • Documentation standards for memos and register entries

Escalation Guide

references/escalation_guide.md

When to engage outside counsel:

  • Mandatory engagement triggers (litigation, investigation, criminal)
  • Strongly recommended scenarios (novel issues, material exposure)
  • Consider scenarios (complex disputes, employment, data incidents)
  • Risk category definitions and contributing/mitigating factors

Workflows

Workflow 1: New Risk Assessment

Step 1: Identify risk category and description
        → Use references/risk_framework.md category definitions

Step 2: Score severity (1-5) and likelihood (1-5)
        → python scripts/risk_scorer.py --severity N --likelihood N \
          --category "Category" --description "Description"

Step 3: Review risk level and recommended action
        → GREEN: Accept and document
        → YELLOW: Assign owner and monitor
        → ORANGE: Escalate to senior counsel
        → RED: Immediate escalation, crisis management

Step 4: Determine outside counsel need
        → Consult references/escalation_guide.md

Step 5: Document in risk register
        → Add entry to register JSON file

Workflow 2: Periodic Risk Register Review

Step 1: Load current risk register
        → python scripts/risk_scorer.py --input register.json

Step 2: Generate assessment memo
        → python scripts/risk_report_generator.py --input register.json --output memo.md

Step 3: Review top risks and distribution
        → Focus on ORANGE and RED risks first

Step 4: Update severity/likelihood for changed risks
        → Re-score and regenerate report

Step 5: Distribute memo to stakeholders

Workflow 3: Escalation Decision

Step 1: Score the risk
        → python scripts/risk_scorer.py --severity N --likelihood N \
          --category "Category" --description "Description"

Step 2: Check escalation triggers
        → Mandatory: active litigation, government investigation, criminal exposure
        → Strongly Recommended: novel issues, jurisdictional complexity, material exposure
        → Consider: complex disputes, employment matters, data incidents

Step 3: Document escalation rationale
        → Include risk score, level, and specific trigger in memo

Step 4: Select outside counsel if needed
        → See references/escalation_guide.md criteria

Troubleshooting

ProblemPossible CauseResolution
Risk score seems too low for a serious matterSeverity or likelihood underestimated; qualitative factors not capturedReview severity descriptions in risk_framework.md; consider worst-case financial exposure; add contributing factors to description
Multiple risks in same category but different scoresRisks have different severity/likelihood combinationsThis is expected; each risk is independent; review category-level trends in report
Batch mode fails on input fileMalformed JSON or missing required fieldsVerify JSON structure matches expected format; ensure each risk has severity, likelihood, category, description
Report generator produces empty matrixNo risks in input file or all risks have invalid scoresCheck that input JSON contains valid risks with severity 1-5 and likelihood 1-5
Escalation guide suggests outside counsel but budget is constrainedRisk score indicates material exposureDocument the budget constraint and residual risk acceptance; consider limited-scope engagement
Risk register grows unwieldyRisks not being closed or consolidatedArchive resolved risks; consolidate related risks; review register quarterly

Success Criteria

  • All identified legal risks scored and documented -- every risk has severity, likelihood, category, description, and recommended action in the register
  • Risk distribution reviewed quarterly -- memo generated and distributed to stakeholders with trend analysis
  • ORANGE and RED risks have assigned owners and mitigation plans -- no high-severity risk without accountability
  • Escalation decisions documented with rationale -- outside counsel engagement triggers clearly recorded
  • Risk register maintained as living document -- risks updated, resolved, or archived as status changes

Scope & Limitations

In Scope:

  • Quantitative risk scoring using 5x5 Severity x Likelihood matrix
  • Risk register management and batch processing
  • Risk assessment memo generation with matrix visualization
  • Escalation guidance for outside counsel engagement
  • Risk categorization (Contract, Regulatory, Litigation, IP, Data Privacy, Employment, Corporate)

Out of Scope:

  • Legal advice on specific risk mitigation strategies -- consult legal counsel
  • Insurance coverage analysis or actuarial calculations
  • Regulatory filing or submission preparation
  • Contract drafting or review
  • Litigation strategy or case management

Anti-Patterns

  • Scoring by committee consensus without criteria -- use the defined severity and likelihood scales consistently; do not negotiate scores to make stakeholders comfortable; a risk scored as 4 severity should match the framework definition
  • Treating the risk register as a one-time exercise -- risk registers are living documents; risks change as circumstances evolve; schedule quarterly reviews and update scores accordingly
  • Escalating everything to outside counsel -- the escalation guide defines specific triggers; not every YELLOW risk needs external counsel; over-escalation wastes budget and creates dependency
  • Ignoring GREEN risks entirely -- GREEN risks still require documentation and periodic monitoring; a GREEN risk can escalate to YELLOW or ORANGE if circumstances change
  • Using risk scores as the sole decision factor -- scores are inputs to judgment, not substitutes; qualitative factors like reputational impact or strategic importance may warrant action beyond what the score suggests

Tool Reference

risk_scorer.py

Calculates risk scores and assigns color-coded risk levels with recommended actions.

FlagRequiredDescription
--severity <1-5>Yes (single mode)Severity rating: 1=Negligible, 2=Minor, 3=Moderate, 4=Major, 5=Critical
--likelihood <1-5>Yes (single mode)Likelihood rating: 1=Remote, 2=Unlikely, 3=Possible, 4=Likely, 5=Almost Certain
--category <text>Yes (single mode)Risk category: Contract, Regulatory, Litigation, IP, Data Privacy, Employment, Corporate
--description <text>Yes (single mode)Risk description
--input <file>Yes (batch mode)Path to JSON file containing multiple risks
--jsonNoOutput results in JSON format

risk_report_generator.py

Generates formatted risk assessment memo from a risk register JSON file.

FlagRequiredDescription
--input <file>YesPath to risk register JSON file
--output <file>NoSave memo to specified file path (markdown format)
--jsonNoOutput report metadata in JSON format

平台分布

Codex

36.73%
按下载量换算55

Claude

30.39%
按下载量换算46

Cursor

21.38%
按下载量换算32

Gemini CLI

8.99%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

可写文件

该 Skill 可能写入或修改本地文件,使用前需要确认目标目录和修改范围。

安装前确认

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

继续浏览同类 Skills