[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K3ZP9NSSRPB95YMJ8W507N":3,"skill-same:01M6K3ZP9NSSRPB95YMJ8W507N":57},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6K3ZP9NSSRPB95YMJ8W507N","ordinance-enforceability-check",null,"Review a draft ordinance for vague language, missing definitions, due-process issues, and enforcement practicality.","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\u002Fordinance-enforceability-check\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28],"check","ordinance enforceability check","review","issues","process","enforcement","language","draft","missing","for","vague","2026-11-10 10:12:30",false,"---\nname: ordinance-enforceability-check\ndescription: Review a draft ordinance for vague language, missing definitions, due-process issues, and enforcement practicality.\nargument-hint: [ordinance-topic]\n---\n\n# Ordinance Enforceability Check\n\n**Purpose:** Stress-test a draft ordinance before adoption: can it be understood, enforced fairly, and defended? Complements `ordinance-drafter`.\n\n## Required inputs\n- Draft text (clean and redline), the existing code context, and stated policy goal\n- Enforcing department, staffing, complaint vs. proactive enforcement model\n- Intended penalties and appeal path; relevant state law caps\n\n## Workflow\n1. **Clarity and vagueness:** a law that fails to give fair notice or invites arbitrary enforcement may be void for vagueness, especially when it carries penalties or touches speech. Flag undefined terms such as \"nuisance,\" \"excessive,\" \"suspicious,\" or \"unreasonable,\" and require objective measures (decibels, distances, hours, quantities).\n2. **Definitions:** every operative term defined once; cross-references accurate; consistent with state definitions.\n3. **Scope and overbreadth:** does it sweep in lawful conduct? Check exemptions (emergency, utility work, protected activity), and whether it applies to the city.\n4. **Constitutional hot spots:** speech and assembly (content-neutral time\u002Fplace\u002Fmanner vs. content-based, where strict scrutiny may apply), religious exercise, equal protection, takings, search and seizure for inspections (warrants), fines and forfeiture limits, and rules touching homelessness or camping (current case law is evolving; route to attorney).\n5. **Due process:** notice, opportunity to cure, hearing before an impartial officer, written decision, appeal, and burden of proof. Civil vs. criminal vs. administrative penalty path and jury or hearing rights.\n6. **Penalty structure:** state caps, graduated fines, daily violations, liens, abatement costs, and fee recovery; proportionality.\n7. **Enforcement practicality:** who can issue citations, evidence needed, complaint volume, language access, budget, training, and data for equity review. An unenforceable law harms credibility and may be applied selectively.\n8. **Preemption and consistency:** state or federal limits and conflict with other code provisions.\n9. **Sunset and review:** metrics, reporting, and review date.\n\n## Output structure\n- Summary rating: Ready \u002F Needs revision \u002F Do not advance\n- Issue table: section | problem | consequence | suggested fix\n- Enforcement workflow diagram in text steps\n- Questions for sponsor and department\n\n## Red flags \u002F escalate to the city attorney\n- Anything touching speech, protest, religion, housing, or property\n- Warrantless entry or inspection powers\n- Criminal penalties for status-based conduct\n- Delegation of broad discretion to staff without standards\n\n## Common mistakes\n- Relying on \"reasonable person\" language without criteria\n- Fines without a collection or appeal process\n- Selective enforcement through complaint-driven design without safeguards\n\n*Not legal advice.*\n","# Ordinance Enforceability Check\n\n**Purpose:** Stress-test a draft ordinance before adoption: can it be understood, enforced fairly, and defended? Complements `ordinance-drafter`.\n\n## Required inputs\n- Draft text (clean and redline), the existing code context, and stated policy goal\n- Enforcing department, staffing, complaint vs. proactive enforcement model\n- Intended penalties and appeal path; relevant state law caps\n\n## Workflow\n1. **Clarity and vagueness:** a law that fails to give fair notice or invites arbitrary enforcement may be void for vagueness, especially when it carries penalties or touches speech. Flag undefined terms such as \"nuisance,\" \"excessive,\" \"suspicious,\" or \"unreasonable,\" and require objective measures (decibels, distances, hours, quantities).\n2. **Definitions:** every operative term defined once; cross-references accurate; consistent with state definitions.\n3. **Scope and overbreadth:** does it sweep in lawful conduct? Check exemptions (emergency, utility work, protected activity), and whether it applies to the city.\n4. **Constitutional hot spots:** speech and assembly (content-neutral time\u002Fplace\u002Fmanner vs. content-based, where strict scrutiny may apply), religious exercise, equal protection, takings, search and seizure for inspections (warrants), fines and forfeiture limits, and rules touching homelessness or camping (current case law is evolving; route to attorney).\n5. **Due process:** notice, opportunity to cure, hearing before an impartial officer, written decision, appeal, and burden of proof. Civil vs. criminal vs. administrative penalty path and jury or hearing rights.\n6. **Penalty structure:** state caps, graduated fines, daily violations, liens, abatement costs, and fee recovery; proportionality.\n7. **Enforcement practicality:** who can issue citations, evidence needed, complaint volume, language access, budget, training, and data for equity review. An unenforceable law harms credibility and may be applied selectively.\n8. **Preemption and consistency:** state or federal limits and conflict with other code provisions.\n9. **Sunset and review:** metrics, reporting, and review date.\n\n## Output structure\n- Summary rating: Ready \u002F Needs revision \u002F Do not advance\n- Issue table: section | problem | consequence | suggested fix\n- Enforcement workflow diagram in text steps\n- Questions for sponsor and department\n\n## Red flags \u002F escalate to the city attorney\n- Anything touching speech, protest, religion, housing, or property\n- Warrantless entry or inspection powers\n- Criminal penalties for status-based conduct\n- Delegation of broad discretion to staff without standards\n\n## Common mistakes\n- Relying on \"reasonable person\" language without criteria\n- Fines without a collection or appeal process\n- Selective enforcement through complaint-driven design without safeguards\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":34},[35],"ordinance-topic","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Flegal-risk\u002Fordinance-enforceability-check",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill ordinance-enforceability-check",{"tool":49,"command":50},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill ordinance-enforceability-check",{"tool":52,"command":53},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill ordinance-enforceability-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Flegal-risk\u002Fordinance-enforceability-check\u002FSKILL.md",true,[],[58,77,89,121,140,153],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":29},"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",[],[65,66,67,68,69,70,71,72,73,74,75,76],"town hall kit","kit","follow-up","questions","with","event","agenda","prepare","priorities","message","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":29},"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,25,84,85,86,87,70,88,27],"council","voice","but","head","manager",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":105,"publishedAt":29},"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",[95,100],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[106,107,108,109,110,111,112,69,113,114,115,116,117,118,119,120],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":29},"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",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000034","行政与办公人员",[131,132,133,134,135,136,137,68,138,139],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":29},"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",[],[147,148,149,150,20,151,152,69],"press release writer","press release","writer","release","write","legal",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":29},"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",[159],{"categoryNo":128,"categoryName":129,"taxonomyType":103,"taxonomyTypeDesc":104},[161,139,162,163,75,131,164,25,165,166,27,84],"meeting notice drafter","notice","content","board","posting","type"]