contract obligation mapper
Extracts traceable contract obligations, deadlines, and dependencies into a structured evidence register.
$5
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentscontract obligation mapper
Example session with this skill installed
Analyze the 'Notices' and 'Payment Terms' sections of the attached Services Agreement. Create an obligation register and flag any missing triggers or dependencies.
- Read your context and instructions
- Compiled the contract obligation mapper
The analysis of the 'Notices' and 'Payment Terms' sections is complete. I identified 3 explicit obligations and 1 instance of missing information regarding payment triggers.
Contract Obligation Map
Source Scope
Document: Services Agreement (Draft_v2.4)
Sections: Section 4 (Payment) and Section 12 (Notices)
Status: Appears complete for the specified sections. Referenced 'Exhibit A' was not supplied.
Executive Summary
- Explicit Obligations: 3
- Inferred Items: 0
- Missing Information: 1
- Ambiguity/Conflict Flags: 1
Evidence Register
| ID | Status | Responsible party | Required action or restriction | Deadline / trigger | Conditions / dependencies | Exceptions | Source |
|---|---|---|---|---|---|---|---|
| OBL-01 | Explicit | Client | Pay undisputed Invoice amounts | Within 30 days of receipt | Receipt of valid invoice | Disputed amounts | Sec 4.1 |
| OBL-02 | Explicit | Provider | Submit monthly progress report | 5th business day of month | Completion of month | Not stated | Sec 4.2 |
| OBL-03 | Explicit | Either Party | Provide notice of address change | 10 days prior to change | None | Emergency moves | Sec 12.3 |
Evidence Detail
OBL-01 — Payment of Invoices
- Classification: Explicit
- Responsible party: Client
- Affected party: Provider
- Required action: Remit payment for all undisputed fees.
- Deliverable: Electronic funds transfer or check.
- Deadline / trigger: 30 days following receipt of an invoice.
- Conditions / dependencies: Invoice must be "valid" as per Section 4.3 (Requirements not supplied).
- Source wording: "Client shall pay all undisputed amounts within thirty (30) days of receipt of a valid invoice."
- Source location: Page 4, Section 4.1, Paragraph 1.
Ambiguities and Potential Conflicts
| Issue ID | Relevant provisions | Problem | What is clear | What remains unresolved |
|---|---|---|---|---|
| AMB-01 | Section 4.1 vs 4.2 | Inconsistent 'receipt' definition | Payment is due 30 days from receipt. | Whether 'receipt' is defined by the date of email sent or date of physical delivery. |
Missing Information and Follow-Up
- Exhibit A: Referenced in Section 4.1 for fee schedules; not provided in source.
- Section 4.3: Contains "valid invoice" requirements; not included in the supplied page range.
Next steps
- Provide Section 4.3 to clarify invoice validation requirements.
- Supply Exhibit A to confirm the specific fee amounts and currency.
- Review Section 12.1 to confirm if email constitutes "receipt" for payment triggers.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Manual contract review is slow and prone to oversight. Missing a single notice period, payment trigger, or carve-out creates immediate operational and financial risk.
What it does
- Extracts specific actions, deliverables, and restrictions into a structured traceability matrix.
- Differentiates between explicit mandatory language and context-based inferences.
- Maps every obligation to its exact source wording and document location.
- Flags undefined terms, conflicting clauses, and missing exhibits or schedules.
- Identifies triggers, conditions, and dependencies for every contractual commitment.
Why this beats prompting it yourself
General LLMs tend to hallucinate deadlines or provide vague summaries that lose the technical nuance of legal drafting. This skill enforces strict grounding, ensuring every entry is backed by a quote and preventing the AI from inventing dates, parties, or legal conclusions not present in the text.
Use cases
- Building a post-signature obligation tracker for project management teams.
- Performing rapid gap analysis during due diligence or vendor onboarding.
- Auditing complex MSAs to identify conflicting notice requirements or payment terms.
- Generating a checklist of conditions precedent before a contract effective date.
Known limitations
This tool does not provide legal advice or determine enforceability. It requires legible source text and cannot resolve ambiguities where the contract itself is contradictory.
Does not provide legal advice or risk assessments. Requires legible text (OCR quality matters). Cannot resolve contradictions; it only flags them for review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
No special permissions declared or detected