clause-library-curate

slug	clause-library-curate
name	Clause Library Curate
description	Add a newly observed clause to the clause library with its classification, source, and the playbook position it relates to.
version	0.1.0
metadata	{"sources":[{"mode":"port-original","author":"ClaudeCoder","added_in":"0.1.0"}]}

Clause Library Curate

Port-original skill. Hand-authored for Legal & Contracts. Owned by clause-library-curator.

When to fire

A redline cycle surfaces a clause the firm has not classified yet, or a partner / GC asks to add a new clause variant to the library.

Inputs

Required: clause text, contract type, source (which counterparty paper, which matter), proposed classification (preferred / acceptable / non-negotiable / unacceptable). Optional: drafter / partner notes on why the classification, related-clauses cross-references.

Outputs

A clause-library diff entry:

clause:
  id: <slug>
  contract_type: <NDA / MSA / etc.>
  text: <verbatim>
  classification: preferred | acceptable | non-negotiable | unacceptable
  rationale: <one-line>
  source:
    matter: <ref>
    counterparty: <ref>
    date: <ISO>
    drafter: <agent or attorney>
  related: [<other-clause-ids>]
status: proposed   # always "proposed" — attorney approves before merge

How to curate

1. Read the clause and identify the contract type + clause type (term, indemnity, IP, etc.).
2. Compare against existing library entries for that contract-type + clause-type. If a similar entry exists, mark this as a variant rather than a new entry.
3. Classify per the rubric above. The agent proposes the classification; the attorney decides.
4. Cite the source. Provenance is non-negotiable — every entry must trace to a matter and a date.
5. Mark status: proposed. The agent never merges directly into the live library.

Boundaries

• The agent proposes; the attorney owner (or designated clause-library partner) approves.

• Counterparty-paper text is confidential. The library stores it as a reference clause; do not surface client identifiers outside the entry.

• Sensitive contexts (litigation, settlement, regulatory enforcement) escalate via escalation-routing before any clause from that context lands in the library.

• UPL line. This skill is designed against the unauthorized-practice-of-law line. Output may not be delivered to a recipient, and the agent may not be held out to anyone, until a licensed attorney admitted in the recipient's jurisdiction has reviewed and signed off. The agent does not hold itself out as a lawyer, does not form an attorney–client relationship, and refuses requests that would cross that line. UPL is determined by the recipient's jurisdiction, not the operator's — when in doubt, route to escalation-routing.

Output protocol

Append the proposed entry to clause-library/proposed/<id>.yaml. Post a one-line note on the work item naming the proposed entry and the attorney who needs to approve. Do not modify the live library.