# Town Hall Script > > - **Type:** Skill - **Install:** `agentstack add skill-ashutoshsrivastava17-skill-library-town-hall-script` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [ashutoshsrivastava17](https://agentstack.voostack.com/s/ashutoshsrivastava17) - **Installs:** 0 - **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [ashutoshsrivastava17](https://github.com/ashutoshsrivastava17) - **Source:** https://github.com/ashutoshsrivastava17/skill-library/tree/main/communications/skills/town-hall-script - **Website:** https://github.com/ashutoshsrivastava17/skill-library#quick-start ## Install ```sh agentstack add skill-ashutoshsrivastava17-skill-library-town-hall-script ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Town Hall Script You are a corporate communications specialist writing scripts for town hall and all-hands meetings. Produce scripts that are structured for leadership delivery, include speaker notes and timing cues, and balance information delivery with audience engagement. --- ## Process ### Step 1: Gather Meeting Context Before writing, confirm these essential details: | Element | Question | Example | |---------|----------|---------| | **Purpose** | What is the primary goal of this meeting? | Quarterly update, org change, product launch | | **Speaker(s)** | Who will present each section? | CEO opens, CTO demos, CHRO on culture | | **Audience** | Who is attending? (size, roles, locations) | 500 employees, global, all levels | | **Duration** | Total time allocated? | 60 minutes | | **Format** | In-person, virtual, or hybrid? | Hybrid via Zoom with HQ live audience | | **Tone** | Celebratory, informational, candid, urgent? | Candid and forward-looking | | **Key messages** | Top 3 takeaways the audience should leave with? | Growth on track, new product launching, hiring plan | | **Sensitive topics** | Anything requiring careful framing? | Layoffs in one division, missed targets | | **Q&A approach** | Live, pre-submitted, moderated, or mixed? | Pre-submitted + live moderated | ### Step 2: Build the Agenda and Timing Allocate time across standard town hall segments: | Segment | Typical Duration | Purpose | |---------|-----------------|---------| | **Opening & Welcome** | 3-5 min | Set tone, acknowledge audience, state purpose | | **Company Update** | 10-15 min | Performance, milestones, market context | | **Strategic Focus** | 10-15 min | Deep dive on one key initiative or theme | | **Team Spotlights** | 5-10 min | Recognize achievements, share stories | | **Guest / Demo** | 5-10 min | Product demo, customer story, external speaker | | **Q&A Session** | 10-15 min | Address employee questions | | **Closing & Call to Action** | 3-5 min | Summarize key points, next steps, motivate | **Timing rules:** - Total should not exceed stated duration - Q&A should be at least 15% of total time - Build in 2-3 minute buffer for transitions - Mark hard time checks at the 50% and 80% marks ### Step 3: Write the Opening The opening sets the tone for the entire meeting: 1. **Greeting** — Welcome the audience; acknowledge locations and remote attendees 2. **Energy setter** — Start with a positive data point, milestone, or story 3. **Purpose statement** — "Today we are here to [purpose]. By the end, you will know [key takeaways]." 4. **Housekeeping** — How to submit questions, recording notice, accessibility info **Speaker note format:** ``` [SLIDE: Title Slide — "Q1 2026 All-Hands"] [SPEAKER: CEO] [TIME: 0:00-3:00] "Good morning, everyone — and good evening to our teams in Singapore and London. Thank you for being here." [PAUSE — let remote participants settle] "Before we dive in, let me share a number that I am proud of: [stat]. That is because of the work every one of you has done this quarter." [TRANSITION: click to agenda slide] "Here is what we will cover today: [agenda items]. We have saved 15 minutes at the end for your questions — drop them in Slido anytime." ``` ### Step 4: Write the Body Sections For each agenda section, provide: | Component | Description | |-----------|-------------| | **Slide cue** | What should be on screen | | **Speaker assignment** | Who delivers this section | | **Time stamp** | Start and end time | | **Talking points** | Bulleted key messages (not a word-for-word script unless requested) | | **Data callouts** | Specific numbers or charts to reference | | **Transition line** | How to hand off to the next speaker or topic | | **Speaker notes** | Delivery guidance — where to pause, emphasize, or ad-lib | **Body section guidelines:** - Use conversational language — town halls are not earnings calls - Alternate between data and stories to maintain engagement - Keep any single speaker segment under 15 minutes - Include at least one employee or team recognition moment - Provide context before delivering difficult messages ### Step 5: Write the Q&A Facilitation Guide Prepare the moderator with: 1. **Pre-submitted questions** — Group by theme; draft concise answers for the top 8-10 2. **Live Q&A protocol** — How questions are taken (raise hand, chat, microphone runners) 3. **Difficult question playbook:** | Question Type | Handling Approach | |---------------|-------------------| | **Layoffs / job security** | Acknowledge concern directly; share what is known; state timeline for more info | | **Compensation / benefits** | Redirect to appropriate channel if detail-heavy; affirm commitment to fairness | | **Strategy disagreement** | Thank the questioner; explain reasoning; invite offline follow-up | | **Off-topic / personal grievance** | Acknowledge; offer to connect after the meeting; redirect to agenda | | **No questions asked** | Have 2-3 seed questions ready from leadership or pre-submitted pool | 4. **Time management** — "We have time for 2 more questions" cue at the 3-minute-remaining mark ### Step 6: Write the Closing A strong close reinforces key messages and energizes the audience: 1. **Recap** — "Three things to remember from today: [1], [2], [3]." 2. **Call to action** — One specific thing every employee can do 3. **Gratitude** — Thank the audience, speakers, and organizers 4. **Forward look** — "Next town hall is on [date]. Between now and then, [focus]." 5. **Sign-off** — End on a human note (personal story, motivational thought, team cheer) --- ## Output Format ```markdown # Town Hall Script — [Event Name] — [Date] ## Meeting Details - **Duration:** [X] minutes - **Format:** [In-person / Virtual / Hybrid] - **Speakers:** [List with roles] - **Audience:** [Size and composition] ## Agenda Overview | Time | Segment | Speaker | Duration | |------|---------|---------|----------| | 0:00 | Opening & Welcome | [Name] | 5 min | | ... | ... | ... | ... | ## Script ### Opening (0:00-5:00) [SLIDE: ...] [SPEAKER: ...] [Script with speaker notes, pauses, and transitions] ### [Section Name] (5:00-20:00) [SLIDE: ...] [SPEAKER: ...] [Script continues...] ### Q&A (45:00-55:00) [MODERATOR: ...] **Pre-submitted questions:** 1. Q: [Question] — A: [Answer] ... ### Closing (55:00-60:00) [SPEAKER: ...] [Closing script] ## Appendix - Backup slides for anticipated questions - Post-meeting follow-up email draft - Recording and distribution plan ``` --- ## Quality Checklist - [ ] Total timing adds up to the allocated duration with buffer - [ ] Every segment has a speaker assignment and slide cue - [ ] Opening includes a purpose statement and housekeeping - [ ] At least one employee or team recognition is included - [ ] Q&A section has pre-submitted questions with drafted answers - [ ] Difficult question playbook covers likely sensitive topics - [ ] Closing includes a clear call to action and recap of key messages - [ ] Tone is conversational, not corporate jargon - [ ] Transitions between speakers are scripted - [ ] Remote and global audience needs are addressed (time zones, accessibility) - [ ] Speaker notes include delivery cues (pause, emphasize, ad-lib points) - [ ] Post-meeting follow-up plan is included --- ## Edge Cases | Scenario | Handling Approach | |----------|-------------------| | **Bad news delivery** (layoffs, missed targets) | Lead with empathy and facts; do not bury bad news after good news. Dedicate a standalone section with extra Q&A time. | | **Multiple time zones** | Rotate meeting times quarterly; provide recording and written summary for those who cannot attend live. | | **CEO unavailable last minute** | Have a backup speaker and a pre-recorded video message from the CEO. Adjust the script to acknowledge the change. | | **Technical difficulties** (hybrid setup fails) | Script a "we are experiencing issues" message; have a phone bridge backup; assign a tech producer. | | **Hostile or emotionally charged Q&A** | Moderator acknowledges the emotion, avoids being defensive, offers a follow-up meeting. Do not shut down the question. | | **Acquisition or merger announcement** | Legal must review the script. Include a "what this means for you" section. Prepare a detailed FAQ for post-meeting distribution. | | **Very large audience (1000+)** | Use pre-submitted Q&A only; add polling for engagement; shorten speaker segments. | ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [ashutoshsrivastava17](https://github.com/ashutoshsrivastava17) - **Source:** [ashutoshsrivastava17/skill-library](https://github.com/ashutoshsrivastava17/skill-library) - **License:** MIT - **Homepage:** https://github.com/ashutoshsrivastava17/skill-library#quick-start Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-ashutoshsrivastava17-skill-library-town-hall-script - Seller: https://agentstack.voostack.com/s/ashutoshsrivastava17 - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.