contract-obligation-extraction
Extract obligations from contract documents including deadlines, deliverables, payment terms, SLA commitments, and termination conditions with compliance tracking
Extract obligations from contract documents including deadlines, deliverables, payment terms, SLA commitments, and termination conditions with compliance tracking
Enhance contract search queries with contextual understanding, mapping natural language to contract fields, obligation types, clause categories, and CLM-specific terminology
Generate change request risk explanations analyzing change scope, affected CIs, historical change failure rates, and deployment window risks
Analyze contracts for key terms, obligations, risks, renewal dates, and compliance requirements with metadata extraction and clause flagging
Summarize Third-Party Risk Management issues including vendor risk exposure, assessment gaps, remediation status, and compliance impact across the TPRM lifecycle
Validate GRC issues for completeness, accuracy, and compliance. Check required fields, risk ratings, control mappings, and remediation plan adequacy
Extract metadata from contracts including parties, effective dates, value, auto-renewal terms, governing law, key contacts, and obligation summaries for portfolio management
Review a patent application draft for Section 101 eligibility and Section 112 issues before filing. Use when the user wants to review a patent draft.
Review a patent draft for Section 112 issues including written description, enablement, indefiniteness, and antecedent basis problems. Use when the user wants a focused 112 analysis.
Route code reviews to appropriate council members. Use when reviewing PRs, architecture decisions, or significant code changes that need expert perspective.
WHEN setting working agreements/TDD rules for this codebase; clarifies boundaries and documentation expectations.
Review Red Hat documentation for SSG legal and support compliance — no cost/pricing references, no future release promises, Developer Preview requirements (IMPORTANT admonition, no "supported"), and Technology Preview requirements (IMPORTANT admonition, never "Tech Preview" or "Technical Preview", no "supported as a Technology Preview"). Use this skill when checking Red Hat docs for Technology Preview, Developer Preview, TP/DP admonitions, cost language, future release statements, or support scope compliance. Takes precedence over ibm-sg-legal-information for Red Hat content.
Review documentation for IBM Style Guide legal issues — unsubstantiated claims, superlatives, trademarks (™/® usage), copyright notices, personal information (PII in examples), and republishing/attribution of external content. Use this skill when checking for legal risks, trademark compliance, PII exposure in examples, unsupported marketing claims, or content attribution issues. For Red Hat docs, the rh-ssg-legal-and-support skill takes precedence on Technology Preview and Developer Preview.
Dispute resolution and auto-liquidation system for the Bro app. Use when modifying dispute flows, auto-liquidation timers, AI dispute agent, evidence handling, collateral/escrow, or any code in dispute_service.dart, dispute_detail_screen.dart, disputeAgentService.js, agent.js, or escrow.js. Prevents data loss from encrypted evidence, incorrect timer thresholds, and agent misconfiguration.
Summarize software product compliance status including license counts, entitlement gaps, compliance violations, and recommended remediation actions
Domain context for Multi-layer output validation system — contract enforcement with six validator types (json_schema, typescript_interface, test_suite, markdown_spec, format, non_empty_file), progressive JSON recovery with three aggressiveness tiers, adaptive retry with failure classification and repair prompts, error wrapper detection for AI-generated envelopes, input artifact schema validation, preflight dependency checks with auto-install, and pipeline-level phase/concurrency/staleness validation.
Summarize approval requests with context including what is being requested, who is requesting, business justification, and similar past approvals
HIPAA establishes national standards for protecting patient health information (PHI). Enforced by HHS Office for Civil Rights.
Payment card security, SOC2 compliance, and financial services regulatory requirements
Delaware C-Corp and US startup formation—entity choice, equity, 83(b), compliance, foreign qualification.
Guide for Rust ownership, borrowing, and lifetimes. Use when working with ownership rules, move semantics, borrowing, slices, or lifetime annotations.
Review contracts, MSAs, SOWs, and NDAs. Verifies terms against internal context and delivers risk assessment.