How to use the Material Contracts Disclosure Schedule agent skill

What the skill makes the agent do

The purchase agreement contains a representation along the lines of "Schedule 3.X lists all Material Contracts." This skill builds that schedule. It reads the agreement's definition of "Material Contract," checks each contract reviewed in diligence against the tests in that definition, and flags borderline cases for a human decision.

The agent then formats the included contracts as a numbered schedule that matches the other schedules in the draft agreement. It also prepares an internal consent-tracking table, which is kept separate from the schedule and feeds a closing checklist.

• Loads the Material Contract definition and schedule format from the purchase agreement
• Applies each prong of the definition to the diligence findings
• Flags edge cases, such as contracts just under a threshold or contracts being terminated anyway
• Collects schedule fields (counterparty, date, term, value, prong met, consent required, VDR reference)
• Runs a cross-check for completeness, over-disclosure and VDR citations

Install the skill from a ZIP file or the Claude apps

You can install the skill in one of three ways. The first two use the ZIP file downloaded from this page. Unzip it into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill available only in that project.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Download the ZIP from this page
• Personal use: unzip into ~/.claude/skills/
• Project use: unzip into the project's .claude/skills/ folder
• Claude apps: upload under Settings → Capabilities → Skills

Prerequisites: what you need before you start

The skill depends on inputs you must supply. Without a purchase agreement draft it cannot work, because it relies on the agreement's definition and format and does not decide materiality on its own.

A practice-level CLAUDE.md configuration file for the matter workspace and materiality settings is optional and depends on your setup. The skill also needs access to the claude-for-legal corporate-legal plugin folder structure.

• A purchase agreement draft containing the Material Contract definition and schedule format (required)
• Diligence findings from the diligence-issue-extraction skill (required)
• A practice-level CLAUDE.md configuration file for matter workspace and materiality settings (optional)
• Access to the claude-for-legal corporate-legal plugin folder structure

Trigger the skill with natural requests

You do not need to type a command. The skill is designed to start when you use phrases such as "build the contracts schedule," "disclosure schedule," "schedule 3.X," "material contracts list," or when you are drafting disclosure schedules. The skill also accepts an argument: a path to the purchase agreement, or the Material Contract definition pasted into the chat.

Give the agent the agreement and the diligence findings in the same request so it can apply the definition to the contracts.

• "Build the contracts schedule from the attached purchase agreement and diligence findings."
• "Draft Schedule 3.X material contracts list using the Material Contract definition in section 1.1."
• "Create the disclosure schedule and a consent tracker for the closing checklist."

Review the output: edge cases and the consent overlay

The agent does not simply output a list. It produces a table showing, for each contract reviewed, which prong or prongs it meets and whether it is included. Contracts that are borderline go into a separate list for a human decision. Examples include a contract just under a dollar threshold but important to the business, and oral agreements or side letters whose status is unclear.

The consent tracker is internal. It records which scheduled contracts need consent, their status, an owner and a due date. The skill notes that this overlay and any pre-delivery working draft are derived from privileged diligence materials. Strip internal annotations before the schedule is delivered as an exhibit to the executed purchase agreement.

• Inclusion table: contract, prongs met, include yes or no
• Edge-case list for lawyer decision
• Consent tracker: schedule number, counterparty, consent required, status, owner, due date
• Strip internal annotations before delivery

Safety notes: scripts and network access

This skill runs no scripts and uses no network access, according to its listed details. It works from the documents you provide and the folder structure of the plugin. Because it handles privileged deal materials, keep working drafts within the privilege circle and do not forward the consent overlay outside it.

For regulated-industry or non-US deals, the skill says to research applicable anti-assignment or consent rules, but the file gives no sources. You must verify those rules independently.

• No scripts are run
• No network use
• Working drafts and the consent overlay may be privileged; limit distribution
• Non-US or sector-regulated consent rules must be verified independently

Tips for better results

Give the agent the complete purchase agreement definition and schedule format, not a summary. The skill applies the agreement's definition mechanically, so a summary can change the result.

Check the CLAUDE.md materiality thresholds against the agreement. The skill uses the agreement's definition when the two differ.

Make sure every included entry has a VDR reference so buyer's counsel can find the underlying document. Fill in missing fields rather than letting the agent guess them.

• Paste the full Material Contract definition and schedule format
• Treat the agreement's definition as controlling over CLAUDE.md thresholds
• Require a VDR reference for every entry
• Ask the agent to flag any missing field instead of guessing