跳到正文
cccskills
免费在 GitHub 公开

lumen-clause-extraction

Extract contract terms into a structured review table covering parties, duration, termination, liability, and other commercial clauses. Standardize dates, amounts, and answers while distinguishing absent clauses from explicit negatives and recording confidence in each finding.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

How to answer review-table columns - formats, normalization, "not found" rules and the commercial preset columns.

实测评分 未实测

查看安装方法

适用场景

  • Build a review table of key commercial contract terms
  • Standardize dates, amounts, and party names
  • Distinguish absent clauses from explicit negative provisions
  • Separate termination without cause from event-triggered rights

包含的文件(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Clause extraction

Formats

formatvalueExample
texta string of at most 40 words, the answer first"3 years from 1 April 2026"
yes_notrue, falsetrue
dateISO YYYY-MM-DD, or an ISO duration P2Y, P90D"2026-04-01"
money{"amount": 2000000, "currency": "GBP"}
tagone of the column's options, exactly"England and Wales"
verbatimthe exact quote, nothing else
numbera JSON number, no unit24
percenta JSON number, the percentage (8 % is 8)8
listan array of short strings, one per item, at most 8["Breach", "Insolvency"]

Not found

  • If the document has no clause on the column's question, the cell is {"value": null, "not_found": true, "note": "No clause on X; checked clauses 1-14.", "confidence": "high", "citations": []}.
  • not_found means the document is silent. It is not "no": a lease with no renewal clause is not_found, not false.
  • Use false only when a clause says no ("Neither party may terminate for convenience").

Termination for convenience

  • true only for a right to end the agreement with no trigger: "for convenience", "for any reason", "without cause", a break clause on notice.
  • A right that arises only on an event is not convenience: breach, insolvency, force majeure, change of control, a condition precedent not met, a long-stop date ("if Completion has not occurred by 31 December 2026, either party may terminate"). Such a right alone is not_found, with the clause named in note.

Normalization

  • Durations as written plus a number: "seven (7) years" -> "7 years from each disclosure".
  • Parties: the legal names, comma separated, with their role: "Brightwater Example Holdings Ltd (Customer), Quillon Analytics Inc. (Supplier)".
  • Governing law: the jurisdiction only: "England and Wales", "State of New York".
  • Caps: the rule, then the amount: "Uncapped: neither party's liability is limited", "12 months' fees", "GBP 2,000,000 per year".

Confidence

  • high - one clause answers it directly.
  • medium - you combined clauses, or a defined term changes it.
  • low - the wording is ambiguous. Say why in note.

The commercial preset

keyquestion
partiesWho are the parties?
termHow long does the agreement, or its main obligation, last?
auto_renewalDoes the agreement renew automatically? (yes_no)
termination_convenienceCan a party terminate without cause, for convenience, or under a break clause? Event-triggered rights do not count. (yes_no)
liability_capIs liability capped, and at what amount?
governing_lawWhich law governs the agreement?
assignmentCan a party assign the agreement, and on what condition?
change_of_controlDoes the agreement contain a change-of-control provision: a consent requirement, condition or termination right triggered by a change of control of a party or of the target? (yes_no)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

中文简介正在准备中。当前显示英语简介。

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna2万2026年10月23日 更新

Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.

中文简介正在准备中。当前显示英语简介。

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna2万2026年10月23日 更新

Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.

中文简介正在准备中。当前显示英语简介。

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna2万2026年10月23日 更新

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

中文简介正在准备中。当前显示英语简介。

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna2万2026年10月23日 更新

Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.

中文简介正在准备中。当前显示英语简介。

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna2万2026年10月23日 更新

billing

免费

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

中文简介正在准备中。当前显示英语简介。

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna2万2026年10月23日 更新

查看 kortix-ai 的全部技能

报告此技能的问题