[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K459HYMDATPZTCGF6NVQXA":3,"skill-same:01M6K459HYMDATPZTCGF6NVQXA":55},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6K459HYMDATPZTCGF6NVQXA","faq-builder",null,"Convert a project, policy, or controversy into a plain-language public FAQ that reduces repeated confusion.","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\u002Ffaq-builder\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26],"builder","faq","faq builder","policy","convert","public","language","project","plain-language","2026-11-10 10:12:30",false,"---\nname: faq-builder\ndescription: Convert a project, policy, or controversy into a plain-language public FAQ that reduces repeated confusion.\nargument-hint: [topic]\n---\n\n# FAQ Builder\n\n**Purpose:** Turn complex municipal decisions into a short, accurate FAQ that answers the questions residents actually ask, in the order they ask them.\n\n## Required inputs\n- Topic, current status, and decision timeline\n- Source documents: staff report, ordinance or resolution, maps, budget\n- Question sources: 311 logs, emails, public comments, social posts, council questions\n- Facts that are settled vs. still under consideration\n\n## Workflow\n1. **Collect real questions** from the sources above; cluster them by theme (what, why, who, how much, when, where, how to participate, what happens next). Use residents' wording, then translate jargon.\n2. **Rank** by frequency and consequence. Open with \"What is this?\" and \"How does it affect me?\" Put \"How can I weigh in?\" high with dates and methods.\n3. **Write each answer** in 2-4 short sentences at about an 8th-grade reading level. State the fact, the source, and the date. Define terms once.\n4. **Handle contested topics** neutrally: describe the options, the reasons for each, and the decision process; do not advocate on a pending decision (public funds generally cannot be used to campaign for a ballot measure; verify state law). Distinguish \"adopted,\" \"proposed,\" and \"under study.\"\n5. **Address misconceptions** respectfully (\"Some residents have asked whether...\") with evidence.\n6. **Include numbers carefully:** show units, timeframe, funding source, and what is not included. Verify each number against the staff report.\n7. **Include process facts:** meeting dates, comment deadlines, contacts, how decisions are made, appeals.\n8. **Accessibility and language:** plain headings, alt text for graphics, translation plan (see `language-access-plan`).\n9. **Maintain it:** version date, owner, review trigger; keep a changelog and archive old versions as records.\n\n## Output structure\n- Title and \"last updated\" line\n- 8-15 questions in groups, each with short answer and source\n- \"What we do not know yet\" box\n- How to participate and contact information\n- Internal sheet: source citations, approver, and open items\n\n## Example\n> **Will my taxes go up?** The proposal does not change the property-tax rate. It would use $__ from the __ fund (source: staff report, p. 4). Any future rate change would require a separate public hearing.\n\n## Red flags \u002F escalate to the city attorney\n- Statements about legal rights, liability, or the effect of litigation\n- Pending litigation, bids, or personnel matters\n- Anything that sounds like promoting a candidate or ballot measure\n\n## Common mistakes\n- Answering the questions staff wish residents asked\n- Mixing plan, proposal, and adopted policy\n- Letting the FAQ go stale after a vote\n\n*Not legal advice.*\n","# FAQ Builder\n\n**Purpose:** Turn complex municipal decisions into a short, accurate FAQ that answers the questions residents actually ask, in the order they ask them.\n\n## Required inputs\n- Topic, current status, and decision timeline\n- Source documents: staff report, ordinance or resolution, maps, budget\n- Question sources: 311 logs, emails, public comments, social posts, council questions\n- Facts that are settled vs. still under consideration\n\n## Workflow\n1. **Collect real questions** from the sources above; cluster them by theme (what, why, who, how much, when, where, how to participate, what happens next). Use residents' wording, then translate jargon.\n2. **Rank** by frequency and consequence. Open with \"What is this?\" and \"How does it affect me?\" Put \"How can I weigh in?\" high with dates and methods.\n3. **Write each answer** in 2-4 short sentences at about an 8th-grade reading level. State the fact, the source, and the date. Define terms once.\n4. **Handle contested topics** neutrally: describe the options, the reasons for each, and the decision process; do not advocate on a pending decision (public funds generally cannot be used to campaign for a ballot measure; verify state law). Distinguish \"adopted,\" \"proposed,\" and \"under study.\"\n5. **Address misconceptions** respectfully (\"Some residents have asked whether...\") with evidence.\n6. **Include numbers carefully:** show units, timeframe, funding source, and what is not included. Verify each number against the staff report.\n7. **Include process facts:** meeting dates, comment deadlines, contacts, how decisions are made, appeals.\n8. **Accessibility and language:** plain headings, alt text for graphics, translation plan (see `language-access-plan`).\n9. **Maintain it:** version date, owner, review trigger; keep a changelog and archive old versions as records.\n\n## Output structure\n- Title and \"last updated\" line\n- 8-15 questions in groups, each with short answer and source\n- \"What we do not know yet\" box\n- How to participate and contact information\n- Internal sheet: source citations, approver, and open items\n\n## Example\n> **Will my taxes go up?** The proposal does not change the property-tax rate. It would use $__ from the __ fund (source: staff report, p. 4). Any future rate change would require a separate public hearing.\n\n## Red flags \u002F escalate to the city attorney\n- Statements about legal rights, liability, or the effect of litigation\n- Pending litigation, bids, or personnel matters\n- Anything that sounds like promoting a candidate or ballot measure\n\n## Common mistakes\n- Answering the questions staff wish residents asked\n- Mixing plan, proposal, and adopted policy\n- Letting the FAQ go stale after a vote\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":32},[33],"topic","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Ffaq-builder",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill faq-builder",{"tool":47,"command":48},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill faq-builder",{"tool":50,"command":51},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill faq-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Ffaq-builder\u002FSKILL.md",true,[],[56,75,89,121,139,153],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":27},"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",[],[63,64,65,66,67,68,69,70,71,72,73,74],"town hall kit","kit","follow-up","questions","with","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":27},"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":27},"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,67,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":27},"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","行政与办公人员",[23,131,132,133,134,135,136,66,137,138],"public comment summarizer","public comment","summarizer","options","synthesize","themes","comments","meeting",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":27},"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",[],[146,147,148,149,150,151,152,67],"press release writer","press release","writer","release","review","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":27},"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,138,162,163,73,23,164,82,165,166,88,83],"meeting notice drafter","notice","content","board","posting","type"]