[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K408RRD9KX6XDN71ZYV7SA":3,"skill-same:01M6K408RRD9KX6XDN71ZYV7SA":66},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6K408RRD9KX6XDN71ZYV7SA","code-enforcement-case-summary",null,"Summarize a code enforcement or nuisance case for internal review or action routing with facts and process status.","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\u002Foperations\u002Fcode-enforcement-case-summary\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"code","enforcement","summary","case","code enforcement case summary","review","summarize","status","routing","process","id","with","action","facts","for","2026-11-10 10:12:30",false,"---\nname: code-enforcement-case-summary\ndescription: Summarize a code enforcement or nuisance case for internal review or action routing with facts and process status.\nargument-hint: [case-id]\n---\n\n## Purpose\nCreate a neutral, fact-based case summary that shows where a code enforcement matter stands in the legal process and what the next lawful step is. It is a working draft for the officer, supervisor, and city attorney, not the evidentiary record.\n\n## Required inputs\n- Case file: complaint source and date, property address and parcel, owner and occupant (including registered agent), inspection reports with date\u002Ftime, photos and field notes, and officer identity.\n- Code sections alleged, notices issued (type, method of service, dates, proof of service), compliance deadlines, and responses from the owner.\n- Prior cases at the property, liens, taxes owed, vacant\u002Fabandoned registry status, and any pending permit.\n- Safety indicators: structural hazards, unsafe occupancy, fire or health risk, vulnerable occupants.\n- Applicable procedure: administrative hearing, citation, abatement, receivership, or court action.\n\n## Workflow\n1. Establish facts: observed violation, location, dates, and evidence source. Separate officer observations from complainant statements and from inferences.\n2. Verify jurisdictional basis: right code section, owner of record, proper notice (statutory method and time), and whether a warrant is required for entry beyond what is visible from public areas.\n3. Status in the process: complaint, first notice, reinspection, notice of violation, hearing, order, citation or fine, abatement, lien, or referral. State the next deadline and who acts.\n4. Risk triage: immediate danger (structural collapse, fire, gas, unsafe occupancy) is handled through emergency abatement or unsafe-building procedures and may bypass normal steps; routine conditions follow the standard cycle. Consider the vulnerability of occupants (displacement, tenant rights, relocation obligations).\n5. Fairness and consistency: compare to similar cases, check for selective enforcement, accessibility needs, language access, hardship or compliance-assistance programs, and any retaliation concerns.\n6. Cost and remedies: abatement costs, fine schedule, lien priority, collection method, and limits on fines under state law. Confirm that cost recovery is lawful before the city performs work.\n7. Recommended routing: continue, issue notice, schedule hearing, send to city attorney, emergency abatement, close as compliant, or refer to services (rehab or repair assistance).\n8. Evidence handling: tie each claim to a photo, report, or document with a date; keep the officer's original notes.\n\n## Output structure\n| Date | Event | Source\u002Fevidence | Code section | Status\u002Fnext deadline |\nAdd: summary paragraph, violation list, notice-service check, risk level, recommended action, and open questions for the officer.\n\n## Red flags \u002F escalate\n- Life-safety hazard or vulnerable occupants: escalate same day to building official, fire, and the city attorney.\n- Defective notice or service; deadlines near expiration.\n- AI used to pick properties or people for inspection: the selection criteria and data must be documented and reviewed by the city attorney before operational use; \"the AI flagged it\" is not an answer on challenge.\n- AI-generated summary offered as evidence: it is a draft only. The inspecting officer must verify against personal observations before it enters the file or any hearing.\n- Possible discrimination or retaliation claim; owner hardship or disability; criminal activity (route to police).\n- Demolition, lien foreclosure, or receivership: attorney-led.\n\n## Common mistakes\n- Treating the complaint as proof.\n- Skipping reinspection before escalation.\n- Mixing opinion and observation.\n- Applying a code section not adopted or in force at the time.\n- Ignoring owner contact attempts in the record.\n\n## State-law variance\nNotice, warrant, lien, fine caps, and unsafe-building procedures vary by state and by city charter.\n","## Purpose\nCreate a neutral, fact-based case summary that shows where a code enforcement matter stands in the legal process and what the next lawful step is. It is a working draft for the officer, supervisor, and city attorney, not the evidentiary record.\n\n## Required inputs\n- Case file: complaint source and date, property address and parcel, owner and occupant (including registered agent), inspection reports with date\u002Ftime, photos and field notes, and officer identity.\n- Code sections alleged, notices issued (type, method of service, dates, proof of service), compliance deadlines, and responses from the owner.\n- Prior cases at the property, liens, taxes owed, vacant\u002Fabandoned registry status, and any pending permit.\n- Safety indicators: structural hazards, unsafe occupancy, fire or health risk, vulnerable occupants.\n- Applicable procedure: administrative hearing, citation, abatement, receivership, or court action.\n\n## Workflow\n1. Establish facts: observed violation, location, dates, and evidence source. Separate officer observations from complainant statements and from inferences.\n2. Verify jurisdictional basis: right code section, owner of record, proper notice (statutory method and time), and whether a warrant is required for entry beyond what is visible from public areas.\n3. Status in the process: complaint, first notice, reinspection, notice of violation, hearing, order, citation or fine, abatement, lien, or referral. State the next deadline and who acts.\n4. Risk triage: immediate danger (structural collapse, fire, gas, unsafe occupancy) is handled through emergency abatement or unsafe-building procedures and may bypass normal steps; routine conditions follow the standard cycle. Consider the vulnerability of occupants (displacement, tenant rights, relocation obligations).\n5. Fairness and consistency: compare to similar cases, check for selective enforcement, accessibility needs, language access, hardship or compliance-assistance programs, and any retaliation concerns.\n6. Cost and remedies: abatement costs, fine schedule, lien priority, collection method, and limits on fines under state law. Confirm that cost recovery is lawful before the city performs work.\n7. Recommended routing: continue, issue notice, schedule hearing, send to city attorney, emergency abatement, close as compliant, or refer to services (rehab or repair assistance).\n8. Evidence handling: tie each claim to a photo, report, or document with a date; keep the officer's original notes.\n\n## Output structure\n| Date | Event | Source\u002Fevidence | Code section | Status\u002Fnext deadline |\nAdd: summary paragraph, violation list, notice-service check, risk level, recommended action, and open questions for the officer.\n\n## Red flags \u002F escalate\n- Life-safety hazard or vulnerable occupants: escalate same day to building official, fire, and the city attorney.\n- Defective notice or service; deadlines near expiration.\n- AI used to pick properties or people for inspection: the selection criteria and data must be documented and reviewed by the city attorney before operational use; \"the AI flagged it\" is not an answer on challenge.\n- AI-generated summary offered as evidence: it is a draft only. The inspecting officer must verify against personal observations before it enters the file or any hearing.\n- Possible discrimination or retaliation claim; owner hardship or disability; criminal activity (route to police).\n- Demolition, lien foreclosure, or receivership: attorney-led.\n\n## Common mistakes\n- Treating the complaint as proof.\n- Skipping reinspection before escalation.\n- Mixing opinion and observation.\n- Applying a code section not adopted or in force at the time.\n- Ignoring owner contact attempts in the record.\n\n## State-law variance\nNotice, warrant, lien, fine caps, and unsafe-building procedures vary by state and by city charter.\n",{"name":5,"description":7,"argument-hint":43},[44],"case-id","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Foperations\u002Fcode-enforcement-case-summary",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill code-enforcement-case-summary",{"tool":58,"command":59},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill code-enforcement-case-summary",{"tool":61,"command":62},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill code-enforcement-case-summary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Foperations\u002Fcode-enforcement-case-summary\u002FSKILL.md",true,[],[67,85,98,128,147,160],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":38},"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",[],[74,75,76,77,34,78,79,80,81,82,83,84],"town hall kit","kit","follow-up","questions","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":38},"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",[],[87,92,93,94,95,96,78,97,37],"draft","council","voice","but","head","manager",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":112,"publishedAt":38},"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",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000035","市场营销",[113,114,115,116,117,118,119,34,120,121,122,123,124,125,126,127],"social post","series","post","social","social post series","fit","multi","social media","control","accessibility","generate","Media","channel","campaign","tone",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":38},"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",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000034","行政与办公人员",[138,139,140,141,142,143,144,77,145,146],"public","public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":38},"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",[],[154,155,156,157,28,158,159,34],"press release writer","press release","writer","release","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":38},"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":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},[168,146,169,170,83,138,171,92,172,173,37,93],"meeting notice drafter","notice","content","board","posting","type"]