Contract Snapshot

What it does

When your agent uses it

• The user wants to compare the same handful of terms across N contracts side-by-side in a grid — what is the term
• Survival period
• Governing law in each of these 5 NDAs?

Example prompts

• “/contract-snapshot”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

1. 1Review the column queries — do they match the questions you actually want answered for this corpus?
2. 2Spot-check at least one cell per column against the source document — does the extraction faithfully represent the source?
3. 3Treat any not found cell as a signal to investigate, not as definitive evidence that the clause is absent.

What it can do on your machine

Read from SKILL.md and the folder at commit d185a62. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Contract Snapshot loads about 1.8k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 666 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~109

When it runs · the whole SKILL.md, loaded when a task matches

~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LegalQuants/lq-ai at commit d185a62, republished under its Apache-2.0 licence (© LegalQuants). 666 words, ~1,752 tokens.

name

contract-snapshot

description

Use when the user wants to compare the same handful of terms across N contracts side-by-side in a grid — what is the term, survival period, carveouts, and governing law in each of these 5 NDAs? Returns a row-per-document × column-per-question grid with citations per cell. Reference skill for the M3-C output_format - table mode; intended as a starting point for operators to fork and tune for their own contract types.

lq_ai.title

Contract Snapshot

lq_ai.version

1.0.0

lq_ai.author

LegalQuants

lq_ai.tags

contracts, due-diligence, tabular, snapshot

lq_ai.jurisdiction

agnostic

lq_ai.trigger_examples

compare the term length and governing law across these NDAs, show me a side-by-side of these 5 contracts on key terms, I want a grid of these contracts'…

lq_ai.output_format

table

lq_ai.ensemble_verification

false

lq_ai.minimum_inference_tier

2

# skills/my-org/msa-snapshot/SKILL.md (operator's fork)
output_format: table
columns:
  - name: Payment Terms
    query: What are the payment terms (frequency, days-to-pay, late-fee provisions)?
  - name: IP Ownership
    query: Who owns IP created during the engagement (work-for-hire, license-back, joint)?
  - name: Termination
    query: List each termination right (for cause, for convenience, notice periods).
  # ... more columns

© LegalQuants, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/contract-snapshot of LegalQuants/lq-ai.

Open the folder on GitHubat commit d185a62