{"id":15614,"plugin_id":"plugin_asdk_app_6aa303b3560881919d1904bc32b0890e","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:11:42.640Z","digest":"eb24d074006aeb53d212d7979dd4714be3d334e3cd595008ba1734df28661b41","against":null,"payload":{"description":"Turn an in-house legal request into a grounded Sandstone context by finding the related matter, people, companies, conversations, and documents. Use for an unstructured request or ambiguous record lookup.","included_files":[],"name":"find-legal-context","skill_md_contents":"---\nname: find-legal-context\ndescription: Turn an in-house legal request into a grounded Sandstone context by finding the related matter, people, companies, conversations, and documents. Use for an unstructured request or ambiguous record lookup.\n---\n\nTurn the user's request into a grounded legal-work context using read-only GraphQL operations.\n\n1. Extract the request, urgency, requested outcome, named people, companies, matter names, and document references.\n2. Use schema search or introspection only to discover the fields needed, then execute read-only GraphQL queries. Try exact names first, then narrower combinations; do not guess when multiple records match.\n3. Present the best matching matter and relationship context with links or record identifiers and a short reason for each match.\n4. List relevant documents and their dates. Distinguish directly matching records from nearby context.\n5. Ask only for the smallest clarification needed when confidence is low. Never claim that a record exists when the search returned no match.\n\nDo not make legal conclusions or execute mutations. Do not expose unrelated records.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}