Schedule
asgeirtj/system_prompts_leaks
Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule.
Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format.
OfficialApache-2.0Auto-check passed
Install Material Contract Schedule
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install anthropics/claude-for-legal material-contract-schedule --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .claude/skills/material-contract-schedule && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .claude/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-scheduleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install anthropics/claude-for-legal material-contract-schedule --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .agents/skills/material-contract-schedule && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .agents/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install anthropics/claude-for-legal material-contract-schedule --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .cursor/skills/material-contract-schedule && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .cursor/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/anthropics/claude-for-legal.git --path corporate-legal/skills/material-contract-schedule--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install anthropics/claude-for-legal material-contract-schedule --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .gemini/skills/material-contract-schedule && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .gemini/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install anthropics/claude-for-legal material-contract-scheduleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .github/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .github/skills/material-contract-schedule && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .github/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install anthropics/claude-for-legal material-contract-schedule --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/corporate-legal/skills/material-contract-schedule .opencode/skills/material-contract-schedule && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "material-contract-schedule" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/corporate-legal/skills/material-contract-schedule into .opencode/skills/material-contract-schedule/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "material-contract-schedule", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
material-contract-schedule- GitHub stars
- 9.6k
- Used in
- 2 other repos
- Token cost
- ~1.6k tokens
- SKILL.md length
- 743 words
- Files
- 1
- Skills in repo
- 147
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format.
- Works in 5 steps: Get the definition → Apply the definition to the findings → Gather schedule data → …
- User says build the contracts schedule
- SKILL.md covers Matter context, Purpose, Load context and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Material Contract Schedule is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format. Use when user says "build the contracts schedule", "disclosure schedule", "schedule 3.X", "material contracts list", or when drafting disclosure schedules.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.
When your agent uses it
- User says build the contracts schedule
- Disclosure schedule
- Material contracts list
- Drafting disclosure schedules
Example prompts
- “s Material Contract definition and formatting per the agreement”
- “build the contracts schedule”
- “disclosure schedule”
- “/material-contract-schedule”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a6c651. 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 markdown).
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
Material Contract Schedule loads about 1.6k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 743 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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 anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 743 words, ~1,633 tokens.
Download SKILL.mdSave it as
.claude/skills/material-contract-schedule/SKILL.md (or your agent's skills folder).- name
- material-contract-schedule
- description
- Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format. Use when user says "build the contracts schedule", "disclosure schedule", "schedule 3.X", "material contracts list", or when drafting disclosure schedules.
- argument-hint
- [purchase agreement path, or paste the Material Contract definition]
/material-contract-schedule
- Load purchase agreement → Material Contract definition + schedule format.
- Use the workflow below.
- Apply definition to diligence findings. Flag edge cases.
- Format per agreement. Consent overlay feeds closing checklist.
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
The purchase agreement has a rep: "Schedule 3.X lists all Material Contracts." This skill builds that schedule from the diligence findings — which contracts are material per the agreement's definition, in the format the agreement requires.
Load context
- Purchase agreement draft — for the definition of "Material Contract" and the schedule format
~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md→ materiality thresholds (may differ from the agreement definition — use the agreement's)- Diligence findings from diligence-issue-extraction — contract-level data
Workflow
Step 1: Get the definition
Pull the definition of "Material Contract" from the purchase agreement — the PA definition controls. Deal-structure differences (stock vs. asset vs. merger) can change how a prong is interpreted, and regulated-industry overlays (healthcare, defense, financial services, telecom, government contracting) can add consent requirements that live outside the PA. If the deal involves any of those overlays, research the applicable anti-assignment or novation rules (for example, federal contracts, government contracting novation, sector-specific consent statutes) and cite the controlling rule.
Common prong categories to look for in the PA definition — these are not a substitute for reading the PA, and the list the PA uses controls:
- Dollar-value threshold (annual or aggregate)
- Term length
- Change-of-control or anti-assignment provision
- Exclusivity or non-compete
- Top N customer or supplier contracts
- Real property leases
- IP licenses (in-bound and out-bound)
- Related-party agreements
- Government contracts
- Contracts outside the ordinary course
The PA's definition is the test. Apply it mechanically — every contract that meets any prong in the PA's definition goes on the schedule.
Step 2: Apply the definition to the findings
For each contract reviewed in diligence:
| Contract | Meets prong(s) | Include |
|---|---|---|
| [name] | [$X+ annual value; CoC provision] | Yes |
| [name] | [none] | No |
Edge cases to flag for human decision:
- Contract is $X-1 (just under threshold) but important to the business
- Contract meets a prong but is being terminated anyway
- Oral agreements or side letters that may or may not count
Show full SKILL.md (322 more words)Show less
Step 3: Gather schedule data
For each included contract, the schedule typically needs:
| Field | Source |
|---|---|
| Counterparty name | Contract |
| Contract title/type | Contract |
| Date | Contract |
| Term / expiration | Contract |
| Annual/total value | Contract or management data |
| Which materiality prong it meets | Step 2 analysis |
| Consent required for the deal | Diligence finding |
| VDR reference | Diligence inventory |
Pull from existing diligence extractions. If a field is missing, flag it — don't guess.
Step 4: Format per the agreement
Disclosure schedules have a format — usually a numbered list or a table, sometimes with sub-parts by contract type. Match the format of the other schedules in the draft agreement.
## Schedule 3.[X] — Material Contracts
The following are the Material Contracts as of the date hereof:
### (a) Customer Contracts
1. [Agreement Title], dated [date], between [Target] and [Counterparty].
[Brief description if the format calls for it.]
[VDR: path]
2. [...]
### (b) Supplier Contracts
[...]
### (c) Real Property
[...]
[etc. — sub-parts per the agreement's definition structure]Step 5: Consent tracking overlay
Separately (not in the schedule itself — this is internal), track which scheduled contracts require consent.
The consent overlay and any pre-delivery working draft of the schedule are derived from privileged diligence materials and inherit their privilege and confidentiality status — distribution beyond the privilege circle can waive privilege. The schedule itself, once delivered as an exhibit to the executed PA, is a deal document and is not privileged; strip any internal annotations before delivery.
| Schedule # | Counterparty | Consent required | Status | Owner | Due |
|---|---|---|---|---|---|
| 3.X(a)(1) | [name] | Yes — CoC §12.2 | Requested | [name] | [date] |
This feeds closing-checklist.
Cross-check
Before delivering:
- Every contract that met a prong is on the schedule (completeness)
- No contract is on the schedule that doesn't meet a prong (no over-disclosure — it's a rep, not a data dump)
- Schedule is consistent with the other reps (a contract on Schedule 3.X that creates a lien should also be on the liens schedule)
- Every entry has a VDR cite so buyer's counsel can find the underlying doc
Handoffs
- From diligence-issue-extraction: Contract-level findings are the input.
- To closing-checklist: Consent items go on the checklist.
What this skill does not do
- It doesn't decide the materiality definition — that's in the purchase agreement.
- It doesn't obtain consents — it tracks which ones are needed.
- It doesn't draft the rep — it populates the schedule the rep references.
© anthropics, 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 corporate-legal/skills/material-contract-schedule of anthropics/claude-for-legal.
Open the folder on GitHubat commit 4a6c651
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Material Contract Schedule next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Material Contract Schedule this skillanthropics/claude-for-legal | 9.6k | 2 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Scheduleasgeirtj/system_prompts_leaks | 69k | — | ~2.7k | Automated safety check: Pass | CC0-1.0 | |
| Scheduleasgeirtj/system_prompts_leaks | 69k | — | ~597 | Automated safety check: Pass | CC0-1.0 | |
| Schedulingasgeirtj/system_prompts_leaks | 69k | — | ~1.4k | Automated safety check: Pass | CC0-1.0 | |
| Cron Scheduleruvnet/ruflo | 74k | — | ~257 | Automated safety check: Pass | MIT | |
| Material Contract Schedulezhou210712/claude-for-legal-ZH | 224 | — | ~680 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Schedule
asgeirtj/system_prompts_leaks
Create or update a scheduled task that runs automatically. An agent skill from asgeirtj/system_prompts_leaks.
Scheduling
asgeirtj/system_prompts_leaks
Find meeting or appointment times, create private calendar holds or invitations, and reschedule or cancel events within the user's authorization.
Cron Schedule
ruvnet/ruflo
Schedule persistent background workers via CronCreate. An agent skill from ruvnet/ruflo.
Material Contract Schedule
zhou210712/claude-for-legal-ZH
从尽调发现构建重大合同披露清单，适用股权收购协议的重大合同定义，并按 协议清单格式排版。当用户说"建合同清单""披露清单""清单 3.X" "重大合同列表"或起草披露清单时使用。
Contract First
affaan-m/ECC
Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protocol Buffers, or JSON Schema), with generated consumer types and…
More from anthropics/claude-for-legal
All 147 skills in this repo- Official
Legal Clinic Client Intake
anthropics/claude-for-legal
Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.
- Official
Supervisor Review Queue
anthropics/claude-for-legal
Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.
- Official
Tabular Document Review
anthropics/claude-for-legal
Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.
- Official
Product Launch Legal Review
anthropics/claude-for-legal
Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.
- Official
Legal Skills Registry Browser
anthropics/claude-for-legal
Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.
- Official
Contract Renewal Tracker
anthropics/claude-for-legal
Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.
Questions about Material Contract Schedule
What does Material Contract Schedule do?
Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format. Material Contract Schedule is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format.
When should I use Material Contract Schedule?
Material Contract Schedule fits situations like: user says build the contracts schedule; disclosure schedule; material contracts list; drafting disclosure schedules.
How do I install Material Contract Schedule in Claude Code?
Run `npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a claude-code`. Or copy the skill folder (corporate-legal/skills/material-contract-schedule in anthropics/claude-for-legal) into .claude/skills/material-contract-schedule in your project. Claude Code loads it when a task matches its description.
How do I install Material Contract Schedule in Codex?
Run `npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a codex`. Or copy the skill folder (corporate-legal/skills/material-contract-schedule in anthropics/claude-for-legal) into .agents/skills/material-contract-schedule in your project. Codex loads it when a task matches its description.
Can I use Material Contract Schedule in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill material-contract-schedule -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/material-contract-schedule, .gemini/skills/material-contract-schedule, .github/skills/material-contract-schedule and .opencode/skills/material-contract-schedule in your project.
What does Material Contract Schedule need to run?
SKILL.md names no scripts, command-line tools or credentials: Material Contract Schedule is instructions for the agent only.
Does Material Contract Schedule access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Material Contract Schedule safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Material Contract Schedule use?
Material Contract Schedule is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Material Contract Schedule use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Material Contract Schedule?
Skills that share tags, products or a category with Material Contract Schedule: Schedule (asgeirtj/system_prompts_leaks, 69k stars), Schedule (asgeirtj/system_prompts_leaks, 69k stars), Scheduling (asgeirtj/system_prompts_leaks, 69k stars) and Cron Schedule (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Material Contract Schedule?
anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,617 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.
Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.