{"id":15615,"plugin_id":"plugin_asdk_app_6aa303b3560881919d1904bc32b0890e","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:11:42.658Z","digest":"cffdfa081851c41350c49fe59215b51e500b9d7cf94ab927b681a4e210964111","against":null,"payload":{"name":"review-matter","description":"Build a concise, source-linked briefing for an in-house legal matter from Sandstone's people, company, conversation, and document context. Use when a legal user needs background before responding or deciding.","included_files":[],"skill_md_contents":"---\nname: review-matter\ndescription: Build a concise, source-linked briefing for an in-house legal matter from Sandstone's people, company, conversation, and document context. Use when a legal user needs background before responding or deciding.\n---\n\nCreate a factual briefing from connected Sandstone records using read-only GraphQL operations.\n\n1. Confirm the matter or identify the strongest match; state ambiguity instead of silently choosing between similar matters.\n2. Use schema introspection to confirm field names, then gather the matter description, status, owners, related people and companies, recent conversations, and relevant documents.\n3. Prefer current records and label dates so stale context is visible.\n4. Organize the result as: matter, stakeholders, timeline, documents, open questions, and sources.\n5. Keep summaries faithful to the records. Mark synthesis as inference and quote only short excerpts when needed to disambiguate.\n\nDo not provide legal advice, invent missing facts, expose unrelated records, or execute mutations while preparing the briefing.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}