← ClaudeAtlas

obligations-extractorlisted

Pulls every obligation, deadline, condition and notice requirement out of a contract into a structured ledger, without evaluating whether any of it is fair, onerous or negotiable. Use this whenever a user wants a list, table or calendar of what a contract actually requires — including phrasings like "list every obligation in this agreement", "what are our deadlines under this contract", "build a compliance calendar from this MSA", "pull out everything we have to deliver and by when", "extract the notice periods", "what do we owe them and what do they owe us", or "turn this contract into a checklist". Also use it as the narrower alternative when a user asks for obligations or dates specifically rather than a full risk review. Fires for any contract with ongoing performance duties — services, supply, licensing, loan, lease, employment, distribution, construction, joint venture.
Cancellationperiplocagraeca503/legal-ai-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill Cancellationperiplocagraeca503/legal-ai-skills
# Obligations Extractor ## What this does Reads a contract and produces a complete ledger of what each party is required to do, when, on what trigger, and what happens if they do not. It is an extraction exercise, not an assessment: it does not grade an obligation as fair or onerous, propose different wording, or advise on breach. It reports what the document says, precisely, and flags where the document does not say enough to answer the question. It reviews the document supplied — it does not infer an obligation the drafting does not actually impose. ## Before you start **The complete document set.** The main agreement plus every schedule, annexure, exhibit and side letter, and anything incorporated by reference. Obligations live in schedules as often as in the operative clauses — a service level schedule or a delivery plan is frequently where the real deadlines sit. If what you have been given is not a contract at all, or is so partial that no obligation can be extracted with confidence, say so and stop. Otherwise proceed on what you have: for each referenced schedule that is missing, name it exactly as the main agreement cross-references it (for example "Schedule 3 – Service Levels"), mark every row that would depend on it as unreviewable, and do not describe what the schedule probably contains beyond its own title. Not blocking, but ask once and proceed without it if unanswered: **what the ledger is for** — a compliance calendar, a diligence file, a handover to an op