Menu

Individual skill

contract-playbook-review

0upvotes

Methodology for clause-by-clause review of a contract against a structured deviation policy ("playbook"). Covers how to walk a playbook, locate the matching provision in the contract, apply rule types (max-value, must-be-present, must-be-absent, acceptable-set, must-have-feature), classify the result (ok / risk / reject), choose the prescribed action, and ground each finding in a verbatim excerpt. Use whenever reviewing any contract — NDA, MSA, vendor DD questionnaire, lease, DPA — against a structured rules-based playbook.

tasks-extra/nda-playbook-review/environment/skills/contract-playbook-review/SKILL.md

Read pinned source

Source commit f860ecf02ef53412a030f8661c83d644b739ff01

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,911
Repository last updated
Nov 4, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Contract playbook review

How a contract reviewer applies a structured deviation policy to a contract, clause by clause, and emits a structured review.

## The general workflow

A playbook is a list of clause rules. Each rule names a clause, describes the policy in prose, and encodes the policy as machine-checkable fields (e.g. `max_years`, `acceptable_jurisdictions`, `must_be_present`). Review is a four-step loop, repeated once per clause:

1. **Locate** the corresponding provision in the contract (it may not be present at all).
2. **Apply** the rule — check the contract's position against the policy fields.
3. **Classify** the outcome as `ok`, `risk`, or `reject`.
4. **Record** the finding: a verbatim excerpt that grounds it, a rationale, and the playbook's prescribed action.

Walk the playbook in order. Don't skip clauses just because the contract is silent on them — silence is itself a finding (`found = false`) and may trigger an action (e.g. "request_addition").
Back to top