[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K466QB0Q2EVZRJ5X1XY21C":3,"skill-same:01M6K466QB0Q2EVZRJ5X1XY21C":58},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6K466QB0Q2EVZRJ5X1XY21C","town-hall-kit",null,"Prepare a town hall kit with agenda, ground rules, likely questions, follow-up method, and message priorities.","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\u002Ftown-hall-kit\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29],"kit","town hall kit","prepare","Rules","up","message","priorities","agenda","event","with","questions","follow-up","2026-11-10 10:12:30",false,"---\nname: town-hall-kit\ndescription: Prepare a town hall kit with agenda, ground rules, likely questions, follow-up method, and message priorities.\nargument-hint: [event-topic]\n---\n\n# Town Hall Kit\n\n**Purpose:** Plan a town hall that is orderly, inclusive, legally safe, and produces usable input. Decide first whether it is a **noticed public meeting** of a body or an informational event; this affects open-meetings obligations.\n\n## Required inputs\n- Topic, goals (inform, hear, decide), and decisions still open\n- Hosts and attendees; whether a quorum of any public body will attend (if so, meeting-law notice and no-deliberation rules may apply; see `open-meeting-risk-check`)\n- Venue, date, accessibility, language needs, budget, security plan\n- Staff and subject experts; moderator\n\n## Workflow\n1. **Purpose and format.** Choose structure: presentation plus Q&A, stations\u002Fopen house, small-group tables, or listening session. Q&A-only formats get dominated by the loudest voices; add written cards, tables, or online submission.\n2. **Notice and outreach:** announce at least two weeks ahead through multiple channels (mail, social, schools, community groups, language media); notice requirements if a quorum attends (see `meeting-notice-drafter`).\n3. **Logistics:** ADA access, interpretation and translation, childcare, transit, time of day, livestream or recording, closed captions, microphones, signage.\n4. **Agenda (90-120 min):** welcome and ground rules (5), context and facts (15), what is decided and when (5), structured input (45-60), summary and next steps (10).\n5. **Ground rules:** equal time per speaker, one question at a time, respect for people, no signs blocking views, what happens with disruptions. Rules apply to everyone and avoid viewpoint judgments (see `first-amendment-comment-limits`).\n6. **Message priorities:** three messages, facts sheet, and what the city can and cannot commit to at the event.\n7. **Q&A prep:** top 15 likely and hardest questions with approved answers, owner for each, and \"park\" process for unknowns. Track unanswered questions publicly.\n8. **Capture input:** note-takers, comment cards, sticky-dot boards, online form; capture demographics optionally to see who was heard.\n9. **Security and safety:** coordination with police, de-escalation plan, emergency exits, and handling of threats.\n10. **Follow-up:** thank-you message, summary of what was heard (see `public-comment-summarizer`), answers to parked questions within a stated timeframe, and next steps.\n\n## Output structure\n- Run-of-show with timings and roles\n- Ground rules script and moderator cues\n- Q&A bank and fact sheet\n- Logistics and accessibility checklist\n- Follow-up plan with owners and dates\n\n## Red flags \u002F escalate to the city attorney\n- A council quorum attending without notice\n- Discussion of pending litigation, personnel, or quasi-judicial cases\n- Threats, protest, or removal of a speaker\n- Candidate or ballot-measure advocacy\n\n## Common mistakes\n- Using the event to announce decisions not yet made\n- Letting officials deliberate with each other\n- No visible follow-up, which erodes trust\n\n*Not legal advice.*\n","# Town Hall Kit\n\n**Purpose:** Plan a town hall that is orderly, inclusive, legally safe, and produces usable input. Decide first whether it is a **noticed public meeting** of a body or an informational event; this affects open-meetings obligations.\n\n## Required inputs\n- Topic, goals (inform, hear, decide), and decisions still open\n- Hosts and attendees; whether a quorum of any public body will attend (if so, meeting-law notice and no-deliberation rules may apply; see `open-meeting-risk-check`)\n- Venue, date, accessibility, language needs, budget, security plan\n- Staff and subject experts; moderator\n\n## Workflow\n1. **Purpose and format.** Choose structure: presentation plus Q&A, stations\u002Fopen house, small-group tables, or listening session. Q&A-only formats get dominated by the loudest voices; add written cards, tables, or online submission.\n2. **Notice and outreach:** announce at least two weeks ahead through multiple channels (mail, social, schools, community groups, language media); notice requirements if a quorum attends (see `meeting-notice-drafter`).\n3. **Logistics:** ADA access, interpretation and translation, childcare, transit, time of day, livestream or recording, closed captions, microphones, signage.\n4. **Agenda (90-120 min):** welcome and ground rules (5), context and facts (15), what is decided and when (5), structured input (45-60), summary and next steps (10).\n5. **Ground rules:** equal time per speaker, one question at a time, respect for people, no signs blocking views, what happens with disruptions. Rules apply to everyone and avoid viewpoint judgments (see `first-amendment-comment-limits`).\n6. **Message priorities:** three messages, facts sheet, and what the city can and cannot commit to at the event.\n7. **Q&A prep:** top 15 likely and hardest questions with approved answers, owner for each, and \"park\" process for unknowns. Track unanswered questions publicly.\n8. **Capture input:** note-takers, comment cards, sticky-dot boards, online form; capture demographics optionally to see who was heard.\n9. **Security and safety:** coordination with police, de-escalation plan, emergency exits, and handling of threats.\n10. **Follow-up:** thank-you message, summary of what was heard (see `public-comment-summarizer`), answers to parked questions within a stated timeframe, and next steps.\n\n## Output structure\n- Run-of-show with timings and roles\n- Ground rules script and moderator cues\n- Q&A bank and fact sheet\n- Logistics and accessibility checklist\n- Follow-up plan with owners and dates\n\n## Red flags \u002F escalate to the city attorney\n- A council quorum attending without notice\n- Discussion of pending litigation, personnel, or quasi-judicial cases\n- Threats, protest, or removal of a speaker\n- Candidate or ballot-measure advocacy\n\n## Common mistakes\n- Using the event to announce decisions not yet made\n- Letting officials deliberate with each other\n- No visible follow-up, which erodes trust\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":35},[36],"event-topic","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Ftown-hall-kit",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill town-hall-kit",{"tool":50,"command":51},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill town-hall-kit",{"tool":53,"command":54},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill town-hall-kit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Ftown-hall-kit\u002FSKILL.md",true,[],[59,73,105,124,138,152],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":30},"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",[],[61,66,67,68,69,70,26,71,72],"council","voice","but","draft","head","manager","for",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":89,"publishedAt":30},"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",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,27,104],"social","series","social post","post","social post series","multi","generate","Media","social media","channel","campaign","tone","control","fit","accessibility",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":30},"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",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000034","行政与办公人员",[115,116,117,118,119,120,121,28,122,123],"summarizer","public","public comment","public comment summarizer","options","synthesize","themes","comments","meeting",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":30},"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",[],[131,132,133,134,135,136,137,27],"release","writer","press release","press release writer","review","write","legal",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":30},"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",[144],{"categoryNo":112,"categoryName":113,"taxonomyType":87,"taxonomyTypeDesc":88},[146,123,147,69,148,149,116,21,72,150,66,151],"notice","meeting notice drafter","posting","type","content","board",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":30},"01M6K45DQ2DZEQFE01X1YG38Y0","language-access-plan","Build a practical language-access and accessibility plan for a notice, hearing, program, or outreach campaign serving limited-English-proficient and disabled residents.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Flanguage-access-plan\u002FSKILL.md",[],[159,160,161,162,163,164,100,165,104,72,166,26,146,167],"plan","language","access","language access plan","practical","build","outreach","serving","english"]