[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3XQ83072B4DN9ECMMGJDB":3,"skill-same:01M6K3XQ83072B4DN9ECMMGJDB":64},{"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":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6K3XQ83072B4DN9ECMMGJDB","open-meeting-risk-check",null,"Review proposed meeting activity, messaging, workshops, emails, or serial conversations for meeting-law and transparency risk.","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\u002Fgovernance\u002Fopen-meeting-risk-check\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"risk","open","check","meeting","Risk Check","open meeting risk check","review","messaging","emails","scenario","transparency","activity","conversations","for","2026-11-10 10:12:30",false,"---\nname: open-meeting-risk-check\ndescription: Review proposed meeting activity, messaging, workshops, emails, or serial conversations for meeting-law and transparency risk.\nargument-hint: [scenario]\n---\n\n# Open Meeting Risk Check\n\n**Purpose:** Screen a scenario against open-meetings (sunshine) law before it happens. Rules vary by state; the Brown Act (California), Texas Open Meetings Act, Florida Sunshine Law, and others differ on definitions of \"meeting,\" quorum counting, and remedies. **Verify everything against your state statute and the city attorney's guidance.**\n\n## Required inputs\n- Scenario (who, how many members, medium, topic, purpose, planned date)\n- Body size and quorum; whether committees, advisory boards, and ad hoc groups are covered under your law\n- Whether the topic is within the body's jurisdiction\n\n## Workflow\n1. **Is a covered body involved?** Council, boards, commissions, standing committees, and often ad hoc committees with delegated authority. Check state definitions.\n2. **Is there a quorum, or a \"collective\" gathering?** Count members present or communicating. Some states reach below a majority (for example, committees of two members, or any gathering where deliberation occurs).\n3. **Is business within jurisdiction being discussed, deliberated, or decided?** Social events are typically fine if no business is discussed; verify.\n4. **Serial or walking-quorum risk:** A-to-B, B-to-C emails, texts, or staff-brokered \"hub and spoke\" conversations that together reach a majority can be a meeting. Reply-all on email threads and group chats are frequent triggers. Staff conveying positions between members is a classic pattern.\n5. **Notice, agenda, and access:** posting period, content of the agenda, location accessibility, remote participation rules, recording rules, and public-comment opportunity. Actions on items not described on the agenda are risky.\n6. **Exceptions:** closed sessions require a specific statutory ground and procedure (see `executive-session-checklist`); conferences and trainings, and \"emergency\" or \"urgent\" provisions have narrow criteria.\n7. **Records:** texts and emails on personal devices may be public records regardless of the open-meetings result.\n8. **Cure options:** cancel or restructure, reduce attendance below quorum, publish notice and agenda, move to a noticed session, or ask the attorney about cure and cease-and-desist procedures where your law has them.\n\n## Output structure\n- Risk rating: Low \u002F Medium \u002F High with the single main reason\n- Facts used and assumptions\n- Issue table: rule question | analysis | confidence (verify)\n- Recommended safe alternative (reworded plan)\n- Suggested guidance to members in two sentences\n\n## Example\n> Three of five members are in a group text \"just to align\" on a vote. Risk: High. A quorum is communicating about business within the body's jurisdiction. Move to staff memo plus public discussion.\n\n## Red flags \u002F escalate to the city attorney\n- Prior violation allegations or demand letters\n- Action taken at a possibly improper meeting (consider re-noticing and ratification; remedies vary)\n- Staff acting as intermediary for member positions\n- Any request to \"decide ahead of time\" a vote\n\n## Common mistakes\n- Assuming no-vote means no meeting\n- Treating social media comments among members as outside the law\n- Forgetting that advisory bodies are often covered\n\n*Not legal advice.*\n","# Open Meeting Risk Check\n\n**Purpose:** Screen a scenario against open-meetings (sunshine) law before it happens. Rules vary by state; the Brown Act (California), Texas Open Meetings Act, Florida Sunshine Law, and others differ on definitions of \"meeting,\" quorum counting, and remedies. **Verify everything against your state statute and the city attorney's guidance.**\n\n## Required inputs\n- Scenario (who, how many members, medium, topic, purpose, planned date)\n- Body size and quorum; whether committees, advisory boards, and ad hoc groups are covered under your law\n- Whether the topic is within the body's jurisdiction\n\n## Workflow\n1. **Is a covered body involved?** Council, boards, commissions, standing committees, and often ad hoc committees with delegated authority. Check state definitions.\n2. **Is there a quorum, or a \"collective\" gathering?** Count members present or communicating. Some states reach below a majority (for example, committees of two members, or any gathering where deliberation occurs).\n3. **Is business within jurisdiction being discussed, deliberated, or decided?** Social events are typically fine if no business is discussed; verify.\n4. **Serial or walking-quorum risk:** A-to-B, B-to-C emails, texts, or staff-brokered \"hub and spoke\" conversations that together reach a majority can be a meeting. Reply-all on email threads and group chats are frequent triggers. Staff conveying positions between members is a classic pattern.\n5. **Notice, agenda, and access:** posting period, content of the agenda, location accessibility, remote participation rules, recording rules, and public-comment opportunity. Actions on items not described on the agenda are risky.\n6. **Exceptions:** closed sessions require a specific statutory ground and procedure (see `executive-session-checklist`); conferences and trainings, and \"emergency\" or \"urgent\" provisions have narrow criteria.\n7. **Records:** texts and emails on personal devices may be public records regardless of the open-meetings result.\n8. **Cure options:** cancel or restructure, reduce attendance below quorum, publish notice and agenda, move to a noticed session, or ask the attorney about cure and cease-and-desist procedures where your law has them.\n\n## Output structure\n- Risk rating: Low \u002F Medium \u002F High with the single main reason\n- Facts used and assumptions\n- Issue table: rule question | analysis | confidence (verify)\n- Recommended safe alternative (reworded plan)\n- Suggested guidance to members in two sentences\n\n## Example\n> Three of five members are in a group text \"just to align\" on a vote. Risk: High. A quorum is communicating about business within the body's jurisdiction. Move to staff memo plus public discussion.\n\n## Red flags \u002F escalate to the city attorney\n- Prior violation allegations or demand letters\n- Action taken at a possibly improper meeting (consider re-noticing and ratification; remedies vary)\n- Staff acting as intermediary for member positions\n- Any request to \"decide ahead of time\" a vote\n\n## Common mistakes\n- Assuming no-vote means no meeting\n- Treating social media comments among members as outside the law\n- Forgetting that advisory bodies are often covered\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":42},[32],"master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fgovernance\u002Fopen-meeting-risk-check",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill open-meeting-risk-check",{"tool":56,"command":57},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill open-meeting-risk-check",{"tool":59,"command":60},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill open-meeting-risk-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fgovernance\u002Fopen-meeting-risk-check\u002FSKILL.md",true,[],[65,84,97,127,143,156],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":37},"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",[],[72,73,74,75,76,77,78,79,80,81,82,83],"town hall kit","kit","follow-up","questions","with","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":37},"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",[],[86,91,92,93,94,95,77,96,36],"draft","council","voice","but","head","manager",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":111,"publishedAt":37},"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",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000035","市场营销",[112,113,114,115,116,117,118,76,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":134,"publishedAt":37},"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":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[135,136,137,138,139,140,141,75,142,26],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":37},"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",[],[150,151,152,153,29,154,155,76],"press release writer","press release","writer","release","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":37},"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":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[164,26,165,166,82,135,167,91,168,169,36,92],"meeting notice drafter","notice","content","board","posting","type"]