{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/vendor-check",
  "version": "1.0.0",
  "name": "vendor-check",
  "description": "Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.",
  "system_prompt_fragment": "# /vendor-check -- Vendor Agreement Status\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).\n\nCheck the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship.\n\n**Important**: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals.\n\n## Invocation\n\n```\n/vendor-check [vendor name]\n```\n\nIf no vendor name is provided, prompt the user to specify which vendor to check.\n\n## Workflow\n\n### Step 1: Identify the Vendor\n\nAccept the vendor name from the user. Handle common variations:\n- Full legal name vs. trade name (e.g., \"Alphabet Inc.\" vs. \"Google\")\n- Abbreviations (e.g., \"AWS\" vs. \"Amazon Web Services\")\n- Parent/subsidiary relationships\n\nAsk the user to clarify if the vendor name is ambiguous.\n\n### Step 2: Search Connected Systems\n\nSearch for the vendor across all available connected systems, in priority order:\n\n#### CLM (Contract Lifecycle Management) -- If Connected\nSearch for all contracts involving the vendor:\n- Active agreements\n- Expired agreements (last 3 years)\n- Agreements in negotiation or pending signature\n- Amendments and addenda\n\n#### CRM -- If Connected\nSearch for the vendor/account record:\n- Account status and relationship type\n- Associated opportunities or deals\n- Contact information for vendor's legal/contracts team\n\n#### Email -- If Connected\nSearch for recent relevant correspondence:\n- Contract-related emails (last 6 months)\n- NDA or agreement attachments\n- Negotiation threads\n\n#### Documents (e.g., Box, Egnyte, SharePoint) -- If Connected\nSearch for:\n- Executed agreements\n- Redlines and drafts\n- Due diligence materials\n\n#### Chat (e.g., Slack, Teams) -- If Connected\nSearch for recent mentions:\n- Contract requests involving this vendor\n- Legal questions about the vendor\n- Relevant team discussions (last 3 months)\n\n### Step 3: Compile Agreement Status\n\nFor each agreement found, report:\n\n| Field | Details |\n|-------|---------|\n| **Agreement Type** | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. |\n| **Status** | Active, Expired, In Negotiation, Pending Signature |\n| **Effective Date** | When the agreement started |\n| **Expiration Date** | When it expires or renews |\n| **Auto-Renewal** | Yes/No, with renewal term and notice period |\n| **Key Terms** | Liability cap, governing law, termination provisions |\n| **Amendments** | Any amendments or addenda on file |\n\n### Step 4: Gap Analysis\n\nIdentify what agreements exist and what might be missing:\n\n```\n## Agreement Coverage\n\n[CHECK] NDA -- [status]\n[CHECK/MISSING] MSA -- [status or \"Not found\"]\n[CHECK/MISSING] DPA -- [status or \"Not found\"]\n[CHECK/MISSING] SOW(s) -- [status or \"Not found\"]\n[CHECK/MISSING] SLA -- [status or \"Not found\"]\n[CHECK/MISSING] Insurance Certificate -- [status or \"Not found\"]\n```\n\nFlag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data).\n\n### Step 5: Generate Report\n\nOutput a consolidated report:\n\n```\n## Vendor Agreement Status: [Vendor Name]\n\n**Search Date**: [today's date]\n**Sources Checked**: [list of systems searched]\n**Sources Unavailable**: [list of systems not connected, if any]\n\n## Relationship Overview\n\n**Vendor**: [full legal name]\n**Relationship Type**: [vendor/partner/customer/etc.]\n**CRM Status**: [if available]\n\n## Agreement Summary\n\n### [Agreement Type 1] -- [Status]\n- **Effective**: [date]\n- **Expires**: [date] ([auto-renews / does not auto-renew])\n- **Key Terms**: [summary of material terms]\n- **Location**: [where the executed copy is stored]\n\n### [Agreement Type 2] -- [Status]\n[etc.]\n\n## Gap Analysis\n\n[What's in place vs. what may be needed]\n\n## Upcoming Actions\n\n- [Any approaching expirations or renewal deadlines]\n- [Required agreements not yet in place]\n- [Amendments or updates that may be needed]\n\n## Notes\n\n[Any relevant context from email/chat searches]\n```\n\n### Step 6: Handle Missing Sources\n\nIf key systems are not connected via MCP:\n\n- **No CLM**: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems.\n- **No CRM**: Skip CRM context. Note the gap.\n- **No Email**: Note that email was not searched. Suggest the user search their email for \"[vendor name] agreement\" or \"[vendor name] NDA\".\n- **No Documents**: Note that document storage was not searched.\n\nAlways clearly state which sources were checked and which were not, so the user knows the completeness of the report.\n\n## Notes\n\n- If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere\n- For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group\n- Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.)\n- If an agreement is approaching expiration (within 90 days), highlight this prominently",
  "applicable_domains": [
    "legal",
    "compliance"
  ],
  "invocation": [
    "/vendor-check",
    "/vendor-check [vendor name]"
  ],
  "tags": [
    "legal",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/legal/skills/vendor-check/SKILL.md",
  "lifecycle": "stable",
  "category": "legal",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/legal/skills/vendor-check/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}