[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K450BS38ZF5ENXED55ATDH":3,"skill-same:01M6K450BS38ZF5ENXED55ATDH":59},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6K450BS38ZF5ENXED55ATDH","crisis-message-house",null,"Build a disciplined crisis message house with holding statement, key messages, and tough Q&A.","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\u002Fpublic-engagement\u002Fcrisis-message-house\u002FSKILL.md",[],[18,19,20,21,22,23,24,25],"message","crisis","crisis message house","messages","build","incident","with","q&a","2026-11-10 10:12:30",false,"---\nname: crisis-message-house\ndescription: Build a disciplined crisis message house with holding statement, key messages, and tough Q&A.\nargument-hint: [incident]\n---\n\n# Crisis Message House\n\n**Purpose:** Within the first hour of an incident, give leaders a disciplined set of verified messages. Use `holding-statement-template.md` for the first statement.\n\n## Required inputs\n- Verified facts only (what, where, when, who is affected), and what is not yet known\n- Source and time of each fact; who is the incident commander or lead agency\n- Public safety actions, resources, and instructions for residents\n- Legal constraints: pending investigation, privacy, victim notification, litigation risk\n\n## Workflow\n1. **Fact sheet:** list Confirmed \u002F Unconfirmed \u002F Unknown. Only confirmed items go public. Timestamp every version.\n2. **Roof (one sentence):** the city's core stance, e.g., safety first, accurate information, accountability.\n3. **Three pillars (key messages):** (a) what happened, factually; (b) what the city is doing; (c) what residents should do. Add proof points under each: actions, numbers, contact points.\n4. **Holding statement** (within 30-60 minutes): acknowledge the incident, express care, state what is known, the response underway, where to get updates, and when the next update will come. No speculation about cause, blame, or number of victims until confirmed.\n5. **Tough Q&A:** list the hardest questions (cause, fault, warnings, response time, cost, injuries, who knew), write short truthful answers, and identify those that must say \"we do not know yet, and we will tell you when we do\" or \"we cannot comment on an active investigation.\"\n6. **Spokespeople and channels:** one lead spokesperson, one subject-matter expert; website banner, social, emergency alerts, 311, press line; plan for accessible and multilingual alerts (see `language-access-plan`).\n7. **Notifications before public release:** affected families, employees, council, partner agencies, regulators; legal and insurance contacts.\n8. **Cadence and corrections:** schedule updates, correct errors quickly and visibly, and log every statement.\n9. **After-action:** retain statements and logs (public records; litigation hold likely).\n\n## Output structure\n- Fact sheet (confirmed\u002Funconfirmed)\n- Message house (roof, 3 pillars, proof points)\n- Holding statement and first social post\n- Tough Q&A table with approvers\n- Update schedule and approvals chain\n\n## Red flags \u002F escalate to the city attorney\n- Potential city fault or liability; death or serious injury\n- Employee misconduct, data breach, or criminal investigation\n- Request to release names, addresses, or video\n- Statements that could affect pending or future litigation\n\n## Common mistakes\n- Saying \"no risk\" or \"all clear\" too early\n- Posting before leadership and legal review when speed is not safety-critical\n- Letting different officials give inconsistent facts\n\n*Not legal advice.*\n","# Crisis Message House\n\n**Purpose:** Within the first hour of an incident, give leaders a disciplined set of verified messages. Use `holding-statement-template.md` for the first statement.\n\n## Required inputs\n- Verified facts only (what, where, when, who is affected), and what is not yet known\n- Source and time of each fact; who is the incident commander or lead agency\n- Public safety actions, resources, and instructions for residents\n- Legal constraints: pending investigation, privacy, victim notification, litigation risk\n\n## Workflow\n1. **Fact sheet:** list Confirmed \u002F Unconfirmed \u002F Unknown. Only confirmed items go public. Timestamp every version.\n2. **Roof (one sentence):** the city's core stance, e.g., safety first, accurate information, accountability.\n3. **Three pillars (key messages):** (a) what happened, factually; (b) what the city is doing; (c) what residents should do. Add proof points under each: actions, numbers, contact points.\n4. **Holding statement** (within 30-60 minutes): acknowledge the incident, express care, state what is known, the response underway, where to get updates, and when the next update will come. No speculation about cause, blame, or number of victims until confirmed.\n5. **Tough Q&A:** list the hardest questions (cause, fault, warnings, response time, cost, injuries, who knew), write short truthful answers, and identify those that must say \"we do not know yet, and we will tell you when we do\" or \"we cannot comment on an active investigation.\"\n6. **Spokespeople and channels:** one lead spokesperson, one subject-matter expert; website banner, social, emergency alerts, 311, press line; plan for accessible and multilingual alerts (see `language-access-plan`).\n7. **Notifications before public release:** affected families, employees, council, partner agencies, regulators; legal and insurance contacts.\n8. **Cadence and corrections:** schedule updates, correct errors quickly and visibly, and log every statement.\n9. **After-action:** retain statements and logs (public records; litigation hold likely).\n\n## Output structure\n- Fact sheet (confirmed\u002Funconfirmed)\n- Message house (roof, 3 pillars, proof points)\n- Holding statement and first social post\n- Tough Q&A table with approvers\n- Update schedule and approvals chain\n\n## Red flags \u002F escalate to the city attorney\n- Potential city fault or liability; death or serious injury\n- Employee misconduct, data breach, or criminal investigation\n- Request to release names, addresses, or video\n- Statements that could affect pending or future litigation\n\n## Common mistakes\n- Saying \"no risk\" or \"all clear\" too early\n- Posting before leadership and legal review when speed is not safety-critical\n- Letting different officials give inconsistent facts\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":31},[23],"master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Fcrisis-message-house",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill crisis-message-house",{"tool":45,"command":46},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill crisis-message-house",{"tool":48,"command":49},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill crisis-message-house","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fcrisis-message-house\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"holding-statement-template.md","REFERENCE","参考文档",796,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fcrisis-message-house\u002Fholding-statement-template.md",[60,77,91,123,142,156],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":26},"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",[],[67,68,69,70,24,71,72,73,74,18,75,76],"town hall kit","kit","follow-up","questions","event","agenda","prepare","priorities","Rules","up",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":26},"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",[],[79,84,85,86,87,88,71,89,90],"draft","council","voice","but","head","manager","for",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":107,"publishedAt":26},"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",[97,102],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[108,109,110,111,112,113,114,24,115,116,117,118,119,120,121,122],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":26},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000034","行政与办公人员",[133,134,135,136,137,138,139,70,140,141],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":26},"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",[],[149,150,151,152,153,154,155,24],"press release writer","press release","writer","release","review","write","legal",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":163,"publishedAt":26},"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",[162],{"categoryNo":130,"categoryName":131,"taxonomyType":105,"taxonomyTypeDesc":106},[164,141,165,166,75,133,167,84,168,169,90,85],"meeting notice drafter","notice","content","board","posting","type"]