[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K45Z8MYT7FVMV48WE0MACS":3,"skill-same:01M6K45Z8MYT7FVMV48WE0MACS":72},{"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":27,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6K45Z8MYT7FVMV48WE0MACS","social-post-series",null,"Generate a multi-post city social media series with tone control, accessibility, and channel fit.","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\u002Fsocial-post-series\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"social","series","social post","post","social post series","accessibility","generate","Media","social media","channel","campaign","tone","control","fit","multi","with","2026-11-10 10:12:30",false,"---\nname: social-post-series\ndescription: Generate a multi-post city social media series with tone control, accessibility, and channel fit.\nargument-hint: [campaign-topic]\n---\n\n# Social Post Series\n\n**Purpose:** Plan and write a coordinated sequence of city social posts that inform, drive action, and stay within government-speech, records, and moderation constraints.\n\n## Required inputs\n- Goal and the single action residents should take (attend, register, report, apply)\n- Dates, links, and facts verified by the department\n- Channels and audience (Facebook, Instagram, X, Nextdoor, YouTube, email, text alerts)\n- Languages and accessibility needs; images and approved brand assets\n- Approval chain and posting windows\n\n## Workflow\n1. **Define the arc.** Typical sequence: awareness, explain, how to participate, reminder, day-of, thank-you\u002Fresults. Space posts to match deadlines.\n2. **Write each post** with one idea, one call to action, and a link; lead with the benefit or deadline. Keep within platform norms (short on X, visual on Instagram, fuller context on Facebook).\n3. **Tone:** warm, plain, neutral. Avoid sarcasm, slang that excludes, partisan framing, and defensive replies. Use identical facts across channels.\n4. **Accessibility:** alt text on images, captions on video, CamelCase hashtags, no text-only graphics without a text equivalent, readable contrast, and plain-language copy. Provide translations or links to them.\n5. **Legal guardrails:** no endorsement of candidates or ballot measures; election-period posts need review (verify state law). Do not post private resident information, minors' images without release, or confidential decisions. Credit and license images properly. Avoid promotional material for vendors.\n6. **Moderation plan:** written comment policy (spam, threats, obscenity, off-topic by objective rules), no deleting criticism based on viewpoint (see `first-amendment-comment-limits`), a response rota, and templates for common questions. Direct service requests to 311.\n7. **Records:** social posts and comments are generally public records; archive them per retention schedule (see `records-retention-trigger-check`).\n8. **Measure:** reach, link clicks, registrations, resident questions; adjust next post.\n\n## Output structure\n- Series calendar: date\u002Ftime | channel | post copy | visual | alt text | link | owner | approval\n- Reply bank for the three most common questions\n- Moderation rules summary and escalation contacts\n\n## Example\n> Post 2 (Tue): \"The Elm Street plan has 3 options. Learn what each means for parking, bikes, and travel time: [link]. Open house Thurs 6 pm at the library. Interpretation available.\"\n\n## Red flags \u002F escalate to the city attorney\n- Posts about investigations, claims, or personnel\n- Emergency messaging (use the crisis workflow)\n- Threats, doxxing, or harassment of staff in comments\n\n## Common mistakes\n- Posting a decision before it is final\n- Hiding critics' comments\n- Link-only posts with no context\n\n*Not legal advice.*\n","# Social Post Series\n\n**Purpose:** Plan and write a coordinated sequence of city social posts that inform, drive action, and stay within government-speech, records, and moderation constraints.\n\n## Required inputs\n- Goal and the single action residents should take (attend, register, report, apply)\n- Dates, links, and facts verified by the department\n- Channels and audience (Facebook, Instagram, X, Nextdoor, YouTube, email, text alerts)\n- Languages and accessibility needs; images and approved brand assets\n- Approval chain and posting windows\n\n## Workflow\n1. **Define the arc.** Typical sequence: awareness, explain, how to participate, reminder, day-of, thank-you\u002Fresults. Space posts to match deadlines.\n2. **Write each post** with one idea, one call to action, and a link; lead with the benefit or deadline. Keep within platform norms (short on X, visual on Instagram, fuller context on Facebook).\n3. **Tone:** warm, plain, neutral. Avoid sarcasm, slang that excludes, partisan framing, and defensive replies. Use identical facts across channels.\n4. **Accessibility:** alt text on images, captions on video, CamelCase hashtags, no text-only graphics without a text equivalent, readable contrast, and plain-language copy. Provide translations or links to them.\n5. **Legal guardrails:** no endorsement of candidates or ballot measures; election-period posts need review (verify state law). Do not post private resident information, minors' images without release, or confidential decisions. Credit and license images properly. Avoid promotional material for vendors.\n6. **Moderation plan:** written comment policy (spam, threats, obscenity, off-topic by objective rules), no deleting criticism based on viewpoint (see `first-amendment-comment-limits`), a response rota, and templates for common questions. Direct service requests to 311.\n7. **Records:** social posts and comments are generally public records; archive them per retention schedule (see `records-retention-trigger-check`).\n8. **Measure:** reach, link clicks, registrations, resident questions; adjust next post.\n\n## Output structure\n- Series calendar: date\u002Ftime | channel | post copy | visual | alt text | link | owner | approval\n- Reply bank for the three most common questions\n- Moderation rules summary and escalation contacts\n\n## Example\n> Post 2 (Tue): \"The Elm Street plan has 3 options. Learn what each means for parking, bikes, and travel time: [link]. Open house Thurs 6 pm at the library. Interpretation available.\"\n\n## Red flags \u002F escalate to the city attorney\n- Posts about investigations, claims, or personnel\n- Emergency messaging (use the crisis workflow)\n- Threats, doxxing, or harassment of staff in comments\n\n## Common mistakes\n- Posting a decision before it is final\n- Hiding critics' comments\n- Link-only posts with no context\n\n*Not legal advice.*\n",{"name":5,"description":7,"argument-hint":49},[50],"campaign-topic","master","edf1fceb08dc8ba63f1ad9159df28c1e0ef449fb","skills\u002Fpublic-engagement\u002Fsocial-post-series",0,"https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT","https:\u002F\u002Fgithub.com\u002FBrianPillmore","2026-11-02 04:58:40",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add BrianPillmore\u002FMayorGPT --skill social-post-series",{"tool":64,"command":65},"bunx","bunx skills add BrianPillmore\u002FMayorGPT --skill social-post-series",{"tool":67,"command":68},"pnpm","pnpm dlx skills add BrianPillmore\u002FMayorGPT --skill social-post-series","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBrianPillmore\u002FMayorGPT\u002Fblob\u002Fmaster\u002Fskills\u002Fpublic-engagement\u002Fsocial-post-series\u002FSKILL.md",true,[],[73,91,105,124,138,152],{"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":79,"publishedAt":44},"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",[],[80,81,82,83,84,85,86,87,88,43,89,90],"town hall kit","kit","prepare","Rules","up","message","priorities","agenda","event","questions","follow-up",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":44},"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",[],[93,98,99,100,101,102,88,103,104],"council","voice","but","draft","head","manager","for",{"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":44},"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":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000034","行政与办公人员",[115,116,117,118,119,89,120,121,122,123],"public comment summarizer","public comment","summarizer","public","meeting","comments","options","synthesize","themes",{"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":44},"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,135,136,137,43],"press release writer","press release","writer","release","write","review","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":44},"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":25,"taxonomyTypeDesc":26},[146,119,147,148,83,118,149,101,150,151,104,98],"meeting notice drafter","notice","content","board","posting","type",{"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":44},"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,38,164,104,88,147,165,33,166,167],"plan","access","language","language access plan","build","serving","english","outreach","practical"]