[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K462B8XJ2FFYH8BAXR0ZM5":3,"skill-same:01M6K462B8XJ2FFYH8BAXR0ZM5":54},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6K462B8XJ2FFYH8BAXR0ZM5","speechwriter",null,"Draft remarks for the mayor, council, manager, or department head in a strong but grounded municipal voice.","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\u002Fspeechwriter\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25],"council","voice","but","draft","head","event","manager","for","2026-11-10 10:12:30",false,"---\nname: speechwriter\ndescription: Draft remarks for the mayor, council, manager, or department head in a strong but grounded municipal voice.\nargument-hint: [event-or-topic]\n---\n\n# Speechwriter\n\n**Purpose:** Write remarks that sound like the speaker, serve a clear purpose, and keep official promises and facts accurate.\n\n## Required inputs\n- Speaker, role, and how they naturally talk (past speeches or samples)\n- Event, audience, length (words ≈ minutes x 130), setting, other speakers, and media presence\n- The one message to land and the one action to ask for\n- Verified facts, numbers, names, and approved stories; sensitivities and what must not be said\n\n## Workflow\n1. **Frame:** audience, purpose (inform, honor, persuade, reassure), and \"one sentence the audience should remember.\"\n2. **Structure:** opening that connects to place or people (not \"Good evening, thank you for having me\" alone); one to three points, each with a concrete example or number; a story rooted in a real resident or project with permission; a close that names the next step.\n3. **Fact check** every claim against sources; label estimates; say \"approximately.\" Do not announce decisions that the council has not made or details under embargo.\n4. **Voice:** short sentences, active verbs, local references, plain words. Match the speaker's humor and formality level. Avoid cliches and borrowed lines; do not copy others' text without attribution.\n5. **Legal and ethical checks:** no campaign or candidate advocacy at official events (verify rules on ballot measures and public funds); no comments on pending litigation, personnel, quasi-judicial matters (see `ethics-conflict-check`); respect confidential closed-session material. Include acknowledgments in correct protocol order (verify local protocol) and pronounce names right.\n6. **Delivery aids:** a speaking copy with breaks and emphasis, time marks, pronunciation guide, and a 90-second cut. Accessible slides or handouts if used.\n7. **Anticipate Q&A or hecklers**: two or three lines for tough questions and a plan for interruptions.\n8. **Record:** speeches may be public records and widely quoted; keep the final text.\n\n## Output structure\n- Speech text with timings\n- Source\u002Ffact table for each claim\n- 90-second version and 3 quotable lines\n- Do-not-say list and Q&A prep\n\n## Example opening\n> \"Eleven years ago, this lot was a place people crossed the street to avoid. Tonight, it is a library with a line out the door.\"\n\n## Red flags \u002F escalate to the city attorney\n- Speech touches litigation, labor negotiations, land-use cases before the body, or elections\n- Promises of funding or timelines not yet approved\n- Quotes or stories involving identifiable residents without permission\n\n## Common mistakes\n- Too many points and statistics\n- Reading dense policy language aloud\n- Overpromising for applause\n\n*Not legal advice.*\n","# Speechwriter\n\n**Purpose:** Write remarks that sound like the speaker, serve a clear purpose, and keep official promises and facts accurate.\n\n## Required inputs\n- Speaker, role, and how they naturally talk (past speeches or samples)\n- Event, audience, length (words ≈ minutes x 130), setting, other speakers, and media presence\n- The one message to land and the one action to ask for\n- Verified facts, numbers, names, and approved stories; sensitivities and what must not be said\n\n## Workflow\n1. **Frame:** audience, purpose (inform, honor, persuade, reassure), and \"one sentence the audience should remember.\"\n2. **Structure:** opening that connects to place or people (not \"Good evening, thank you for having me\" alone); one to three points, each with a concrete example or number; a story rooted in a real resident or project with permission; a close that names the next step.\n3. **Fact check** every claim against sources; label estimates; say \"approximately.\" Do not announce decisions that the council has not made or details under embargo.\n4. **Voice:** short sentences, active verbs, local references, plain words. Match the speaker's humor and formality level. Avoid cliches and borrowed lines; do not copy others' text without attribution.\n5. **Legal and ethical checks:** no campaign or candidate advocacy at official events (verify rules on ballot measures and public funds); no comments on pending litigation, personnel, quasi-judicial matters (see `ethics-conflict-check`); respect confidential closed-session material. Include acknowledgments in correct protocol order (verify local protocol) and pronounce names right.\n6. **Delivery aids:** a speaking copy with breaks and emphasis, time marks, pronunciation guide, and a 90-second cut. Accessible slides or handouts if used.\n7. **Anticipate Q&A or hecklers**: two or three lines for tough questions and a plan for interruptions.\n8. **Record:** speeches may be public records and widely quoted; keep the final text.\n\n## Output structure\n- Speech text with timings\n- Source\u002Ffact table for each claim\n- 90-second version and 3 quotable lines\n- Do-not-say list and Q&A prep\n\n## Example opening\n> \"Eleven years ago, this lot was a place people crossed the street to avoid. Tonight, it is a library with a line out the door.\"\n\n## Red flags \u002F escalate to the city attorney\n- Speech touches litigation, labor negotiations, land-use cases before the body, or elections\n- Promises of funding or timelines not yet approved\n- Quotes or stories involving identifiable residents without permission\n\n## Common mistakes\n- Too many points and statistics\n- Reading dense policy language aloud\n- Overpromising for applause\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":31},[32],"event-or-topic","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Fspeechwriter",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill speechwriter",{"tool":46,"command":47},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill speechwriter",{"tool":49,"command":50},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill speechwriter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fspeechwriter\u002FSKILL.md",true,[],[55,73,105,124,138,152],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":26},"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",[],[62,63,64,65,66,67,68,69,23,70,71,72],"kit","town hall kit","prepare","Rules","up","message","priorities","agenda","with","questions","follow-up",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":89,"publishedAt":26},"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",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[90,91,92,93,94,95,96,97,98,99,100,101,70,102,103,104],"social","series","social post","post","social post series","social media","channel","campaign","tone","control","fit","multi","generate","Media","accessibility",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":26},"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",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000034","行政与办公人员",[115,116,117,118,119,120,121,71,122,123],"public comment","public","summarizer","public comment summarizer","options","synthesize","themes","comments","meeting",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":26},"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",[],[131,132,133,134,70,135,136,137],"release","writer","press release","press release writer","review","write","legal",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":26},"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",[144],{"categoryNo":112,"categoryName":113,"taxonomyType":87,"taxonomyTypeDesc":88},[146,123,147,148,149,150,116,25,65,151,18,21],"notice","meeting notice drafter","posting","type","board","content",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"publishedAt":26},"01M6K45DQ2DZEQFE01X1YG38Y0","language-access-plan","Build a practical language-access and accessibility plan for a notice, hearing, program, or outreach campaign serving limited-English-proficient and disabled residents.","https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Flanguage-access-plan\u002FSKILL.md",[],[159,160,161,162,163,164,165,97,104,166,25,23,146,167],"plan","access","language","language access plan","outreach","practical","build","serving","english"]