[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K41A3TRVHH040ASK8ESP7F":3,"skill-same:01M6K41A3TRVHH040ASK8ESP7F":56},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6K41A3TRVHH040ASK8ESP7F","storm-recovery-action-plan",null,"Turn a storm or tornado damage snapshot into immediate, near-term, and long-term recovery work with owners.","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\u002Fstorm-recovery-action-plan\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28],"recovery","plan","action","storm recovery action plan","owners","work","snapshot","incident","long","with","near","2026-11-10 10:12:30",false,"---\nname: storm-recovery-action-plan\ndescription: Turn a storm or tornado damage snapshot into immediate, near-term, and long-term recovery work with owners.\nargument-hint: [incident]\n---\n\n## Purpose\nOrganize post-storm response into phased work with owners, resources, and documentation aligned to NIMS\u002FICS and the National Disaster Recovery Framework concepts. The plan serves the Incident Commander\u002FEOC and the recovery lead; it supplements, not replaces, the incident action plan.\n\n## Required inputs\n- Damage snapshot: rapid damage assessment results (housing, public buildings, roads, utilities, trees\u002Fdebris), initial cost estimates, and unmet needs.\n- Declarations: local, state, and federal status; thresholds and deadlines.\n- Resources: public works crews, mutual aid, contractors with pre-positioned contracts, debris sites, volunteers.\n- Utility restoration status (electric, gas, communications, water, sewer) and critical facility needs.\n- Insurance coverage, FEMA\u002Fstate programs, and prior mitigation plans.\n\n## Workflow\n1. Phase 0 (0 to 72 hours, response): life safety, search and rescue, road clearance for emergency routes, shelter and mass care, utilities safety, hazard isolation, situational awareness, and public alerts. Priority sequence for debris: emergency routes, critical facilities, then residential streets.\n2. Phase 1 (3 days to 3 weeks, stabilization): damage assessments (local, then joint preliminary damage assessment if requested), debris management plan with monitoring, temporary power\u002Fwater, temporary facilities, disaster declaration requests, donation and volunteer management, and resident information.\n3. Phase 2 (weeks to months, restoration): permanent repairs, permitting surge, contractor registration, rental inspection, business support, unemployment and housing assistance referrals, and infrastructure repairs.\n4. Phase 3 (months to years, recovery and mitigation): rebuilding, hazard mitigation grant projects, plan updates, zoning or building code changes, and long-term community recovery committee.\n5. Reimbursement protection: track force-account labor, equipment hours, and contracts by site (project worksheets); follow federal procurement rules for FEMA-funded work, noting emergency procurement flexibility is limited and documentation-intensive; separate insurance proceeds; keep photos and time logs; confirm deadlines. Verify current FEMA PA policy.\n6. Debris: separate categories (vegetative, construction, hazardous, white goods, vehicles), temporary storage sites with environmental precautions, haul-out contracts with pre-event or competitively procured vendors, and monitor hauling with load tickets.\n7. Permitting and code: emergency permit processes, substantial-damage determinations (50 percent rule in floodplains), temporary housing zoning allowances, and contractor licensing\u002Ffraud warnings.\n8. Equity and vulnerable populations: language access, disabled residents, renters, and unhoused people.\n9. Assign each action an owner by position, due date, resources, and a status check cadence.\n\n## Output structure\n| Phase | Action | Owner | Due | Resource\u002Ffunding | Documentation | Status |\nAdd: priority roads\u002Ffacilities list, debris plan summary, cost tracker, regulatory deadlines (declaration, requests for public assistance), and communications calendar.\n\n## Red flags \u002F escalate\n- Deadlines for declarations, FEMA applicant briefings, and request for public assistance.\n- Procurement without documented competition or rate reasonableness.\n- Hazardous materials, unstable structures, or gas leaks.\n- Substantial damage determinations in floodplains.\n- Contractor fraud complaints.\n- Staff fatigue and safety.\n\n## Common mistakes\n- Starting recovery without cost documentation.\n- Leaving mutual-aid paperwork unsigned.\n- Clearing debris from private property without legal authority.\n- Not planning for longer-term housing needs.\n\n## State-law variance\nDeclaration authority, private-property debris removal rules, and state recovery programs vary by state.\n","## Purpose\nOrganize post-storm response into phased work with owners, resources, and documentation aligned to NIMS\u002FICS and the National Disaster Recovery Framework concepts. The plan serves the Incident Commander\u002FEOC and the recovery lead; it supplements, not replaces, the incident action plan.\n\n## Required inputs\n- Damage snapshot: rapid damage assessment results (housing, public buildings, roads, utilities, trees\u002Fdebris), initial cost estimates, and unmet needs.\n- Declarations: local, state, and federal status; thresholds and deadlines.\n- Resources: public works crews, mutual aid, contractors with pre-positioned contracts, debris sites, volunteers.\n- Utility restoration status (electric, gas, communications, water, sewer) and critical facility needs.\n- Insurance coverage, FEMA\u002Fstate programs, and prior mitigation plans.\n\n## Workflow\n1. Phase 0 (0 to 72 hours, response): life safety, search and rescue, road clearance for emergency routes, shelter and mass care, utilities safety, hazard isolation, situational awareness, and public alerts. Priority sequence for debris: emergency routes, critical facilities, then residential streets.\n2. Phase 1 (3 days to 3 weeks, stabilization): damage assessments (local, then joint preliminary damage assessment if requested), debris management plan with monitoring, temporary power\u002Fwater, temporary facilities, disaster declaration requests, donation and volunteer management, and resident information.\n3. Phase 2 (weeks to months, restoration): permanent repairs, permitting surge, contractor registration, rental inspection, business support, unemployment and housing assistance referrals, and infrastructure repairs.\n4. Phase 3 (months to years, recovery and mitigation): rebuilding, hazard mitigation grant projects, plan updates, zoning or building code changes, and long-term community recovery committee.\n5. Reimbursement protection: track force-account labor, equipment hours, and contracts by site (project worksheets); follow federal procurement rules for FEMA-funded work, noting emergency procurement flexibility is limited and documentation-intensive; separate insurance proceeds; keep photos and time logs; confirm deadlines. Verify current FEMA PA policy.\n6. Debris: separate categories (vegetative, construction, hazardous, white goods, vehicles), temporary storage sites with environmental precautions, haul-out contracts with pre-event or competitively procured vendors, and monitor hauling with load tickets.\n7. Permitting and code: emergency permit processes, substantial-damage determinations (50 percent rule in floodplains), temporary housing zoning allowances, and contractor licensing\u002Ffraud warnings.\n8. Equity and vulnerable populations: language access, disabled residents, renters, and unhoused people.\n9. Assign each action an owner by position, due date, resources, and a status check cadence.\n\n## Output structure\n| Phase | Action | Owner | Due | Resource\u002Ffunding | Documentation | Status |\nAdd: priority roads\u002Ffacilities list, debris plan summary, cost tracker, regulatory deadlines (declaration, requests for public assistance), and communications calendar.\n\n## Red flags \u002F escalate\n- Deadlines for declarations, FEMA applicant briefings, and request for public assistance.\n- Procurement without documented competition or rate reasonableness.\n- Hazardous materials, unstable structures, or gas leaks.\n- Substantial damage determinations in floodplains.\n- Contractor fraud complaints.\n- Staff fatigue and safety.\n\n## Common mistakes\n- Starting recovery without cost documentation.\n- Leaving mutual-aid paperwork unsigned.\n- Clearing debris from private property without legal authority.\n- Not planning for longer-term housing needs.\n\n## State-law variance\nDeclaration authority, private-property debris removal rules, and state recovery programs vary by state.\n",{"name":5,"description":7,"argument-hint":34},[25],"master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Foperations\u002Fstorm-recovery-action-plan",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill storm-recovery-action-plan",{"tool":48,"command":49},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill storm-recovery-action-plan",{"tool":51,"command":52},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill storm-recovery-action-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Foperations\u002Fstorm-recovery-action-plan\u002FSKILL.md",true,[],[57,75,89,121,140,154],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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",[],[64,65,66,67,27,68,69,70,71,72,73,74],"town hall kit","kit","follow-up","questions","event","agenda","prepare","priorities","message","Rules","up",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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",[],[77,82,83,84,85,86,68,87,88],"draft","council","voice","but","head","manager","for",{"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,27,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,67,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,151,152,153,27],"press release writer","press release","writer","release","review","write","legal",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"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",[160],{"categoryNo":128,"categoryName":129,"taxonomyType":103,"taxonomyTypeDesc":104},[162,139,163,164,73,131,165,82,166,167,88,83],"meeting notice drafter","notice","content","board","posting","type"]