[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3ZHRGP8RYDWDMFV11MM5D":3,"skill-same:01M6K3ZHRGP8RYDWDMFV11MM5D":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6K3ZHRGP8RYDWDMFV11MM5D","litigation-hold-checklist",null,"Create a defensible litigation-hold plan with custodians, systems, retention steps, and communication notes.","BrianPillmore\u002FMayorGPT","BrianPillmore","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89977304?v=4","01M6K3S5PAA7GX17DJCHR5QFZ2","01M6K3S5TAA6HKGD1BY6VTV0QB",1,"MIT","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Flegal-risk\u002Flitigation-hold-checklist\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27],"checklist","litigation hold checklist","notes","create","communication","plan","systems","name","retention","with","2026-11-10 10:12:30",false,"---\nname: litigation-hold-checklist\ndescription: Create a defensible litigation-hold plan with custodians, systems, retention steps, and communication notes.\nargument-hint: [matter-name]\n---\n\n# Litigation Hold Checklist\n\n**Purpose:** Issue a hold so potentially relevant records are preserved once litigation is pending or reasonably anticipated. Failure to preserve can lead to sanctions or adverse-inference instructions under court rules; standards vary by jurisdiction. The city attorney issues and owns the hold. See `litigation-hold-notice-template.md`.\n\n## Required inputs\n- Matter description: claim, parties, time period, key events, and what triggered anticipation (notice of claim, demand letter, subpoena, complaint, agency charge, internal incident)\n- Staff and officials likely to have relevant information\n- Systems list: email, chat and text, cloud drives, case-management systems, body-worn and CCTV video, phone records, paper files, personal devices used for city business\n\n## Workflow\n1. **Trigger and date:** record when the duty to preserve arose. It may precede a lawsuit (for example a tort claim notice or a written threat).\n2. **Scope:** define subject matter, date range, and record types. Err toward broader scope; narrow later with attorney approval.\n3. **Custodians:** list individuals, departments, and officials (including elected officials), plus former employees whose accounts remain, and third parties holding city data (vendors, cloud hosts, consultants).\n4. **Suspend routine destruction:** auto-delete on email, chat, voicemail, and video overwrite cycles; records-retention schedule disposals; device wipes and replacement; departing-employee account closure.\n5. **Issue notice:** written, plain language, from the attorney; requires acknowledgment; explains what to keep, what not to do (no deleting, editing, or \"cleaning up\"), and whom to ask. Do not describe the facts or opinions about the case.\n6. **Collect where needed:** forensic copy of mobile devices or key accounts, vendor preservation letters, copies of video before overwrite.\n7. **Follow-up:** reminders at set intervals, new custodians, systems changes, and a log of notices and acknowledgments.\n8. **Release:** written release by the attorney when the matter ends and retention periods otherwise permit disposal.\n9. **Coordinate with records requests:** a hold does not exempt records from disclosure; separately handle public records requests (see `public-records-response`).\n\n## Output structure\n- Trigger, scope, and date range\n- Custodian and system table: name\u002Fsystem | owner | action | acknowledgment date\n- Suspension list (what auto-deletes and who stops it)\n- Draft hold notice and tracking log\n\n## Red flags \u002F escalate to the city attorney\n- Evidence already deleted; overwrite cycles about to run\n- Personal devices or messaging apps in use by officials\n- Parties include elected officials or the manager\n- Insurance carrier or risk pool must be notified (policy deadlines)\n\n## Common mistakes\n- Waiting for a filed lawsuit\n- Relying on custodians to self-select what is relevant\n- Forgetting vendors and cloud systems\n\n*Not legal advice.*\n","# Litigation Hold Checklist\n\n**Purpose:** Issue a hold so potentially relevant records are preserved once litigation is pending or reasonably anticipated. Failure to preserve can lead to sanctions or adverse-inference instructions under court rules; standards vary by jurisdiction. The city attorney issues and owns the hold. See `litigation-hold-notice-template.md`.\n\n## Required inputs\n- Matter description: claim, parties, time period, key events, and what triggered anticipation (notice of claim, demand letter, subpoena, complaint, agency charge, internal incident)\n- Staff and officials likely to have relevant information\n- Systems list: email, chat and text, cloud drives, case-management systems, body-worn and CCTV video, phone records, paper files, personal devices used for city business\n\n## Workflow\n1. **Trigger and date:** record when the duty to preserve arose. It may precede a lawsuit (for example a tort claim notice or a written threat).\n2. **Scope:** define subject matter, date range, and record types. Err toward broader scope; narrow later with attorney approval.\n3. **Custodians:** list individuals, departments, and officials (including elected officials), plus former employees whose accounts remain, and third parties holding city data (vendors, cloud hosts, consultants).\n4. **Suspend routine destruction:** auto-delete on email, chat, voicemail, and video overwrite cycles; records-retention schedule disposals; device wipes and replacement; departing-employee account closure.\n5. **Issue notice:** written, plain language, from the attorney; requires acknowledgment; explains what to keep, what not to do (no deleting, editing, or \"cleaning up\"), and whom to ask. Do not describe the facts or opinions about the case.\n6. **Collect where needed:** forensic copy of mobile devices or key accounts, vendor preservation letters, copies of video before overwrite.\n7. **Follow-up:** reminders at set intervals, new custodians, systems changes, and a log of notices and acknowledgments.\n8. **Release:** written release by the attorney when the matter ends and retention periods otherwise permit disposal.\n9. **Coordinate with records requests:** a hold does not exempt records from disclosure; separately handle public records requests (see `public-records-response`).\n\n## Output structure\n- Trigger, scope, and date range\n- Custodian and system table: name\u002Fsystem | owner | action | acknowledgment date\n- Suspension list (what auto-deletes and who stops it)\n- Draft hold notice and tracking log\n\n## Red flags \u002F escalate to the city attorney\n- Evidence already deleted; overwrite cycles about to run\n- Personal devices or messaging apps in use by officials\n- Parties include elected officials or the manager\n- Insurance carrier or risk pool must be notified (policy deadlines)\n\n## Common mistakes\n- Waiting for a filed lawsuit\n- Relying on custodians to self-select what is relevant\n- Forgetting vendors and cloud systems\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":33},[34],"matter-name","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Flegal-risk\u002Flitigation-hold-checklist",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill litigation-hold-checklist",{"tool":48,"command":49},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill litigation-hold-checklist",{"tool":51,"command":52},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill litigation-hold-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Flegal-risk\u002Flitigation-hold-checklist\u002FSKILL.md",true,[56],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"litigation-hold-notice-template.md","REFERENCE","参考文档",1230,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Flegal-risk\u002Flitigation-hold-checklist\u002Flitigation-hold-notice-template.md",[63,81,95,127,146,160],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":28},"01M6K466QB0Q2EVZRJ5X1XY21C","town-hall-kit","Prepare a town hall kit with agenda, ground rules, likely questions, follow-up method, and message priorities.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Ftown-hall-kit\u002FSKILL.md",[],[70,71,72,73,27,74,75,76,77,78,79,80],"town hall kit","kit","follow-up","questions","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":28},"01M6K462B8XJ2FFYH8BAXR0ZM5","speechwriter","Draft remarks for the mayor, council, manager, or department head in a strong but grounded municipal voice.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fspeechwriter\u002FSKILL.md",[],[83,88,89,90,91,92,74,93,94],"draft","council","voice","but","head","manager","for",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":111,"publishedAt":28},"01M6K45Z8MYT7FVMV48WE0MACS","social-post-series","Generate a multi-post city social media series with tone control, accessibility, and channel fit.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fsocial-post-series\u002FSKILL.md",[101,106],{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[112,113,114,115,116,117,118,27,119,120,121,122,123,124,125,126],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":28},"01M6K45W3AWHA1GMZV2PRDYJBS","public-comment-summarizer","Synthesize hearing or meeting comments into themes, misconceptions, unanswered questions, and response options.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpublic-comment-summarizer\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000034","行政与办公人员",[137,138,139,140,141,142,143,73,144,145],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":28},"01M6K45QWBXSDMGQTA1E9NC43M","press-release-writer","Write a city press release that is accurate, readable, and aligned with legal and operational review needs.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fpress-release-writer\u002FSKILL.md",[],[153,154,155,156,157,158,159,27],"press release writer","press release","writer","release","review","write","legal",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":167,"publishedAt":28},"01M6K45JXZRSW4XXH78FTRBB2A","meeting-notice-drafter","Draft a legally sufficient public notice for any city council, board, commission, or committee meeting — covering required content, posting deadlines, and special-meeting or emergency-meeting rules.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fmeeting-notice-drafter\u002FSKILL.md",[166],{"categoryNo":134,"categoryName":135,"taxonomyType":109,"taxonomyTypeDesc":110},[168,145,169,170,79,137,171,88,172,173,94,89],"meeting notice drafter","notice","content","board","posting","type"]