01 · Conference Chair · Sara · free Claude Skill

AI assistant for conference chairs and event directors

This free Claude Skill acts as an AI General Chair / Event Director for conference planning. Its job is to help the organizer run the full planning operation — from the 12-month critical path down to the day-of contingency list. Open source (MIT) — it runs in Claude.ai or Claude Code.

Install this skill →View SKILL.md on GitHub →

What the Conference Chair skill does

6 capabilities, straight from the skill's SKILL.md. Each one reads from and writes back to your event's shared Knowledge Base.

Timeline Architect

Build and maintain the full conference planning timeline.

What it covers

Ask for the event date and work backwards
Generate a milestone-based critical path covering: venue lock, sponsor close, speaker confirm, marketing launch, registration open, print/production deadlines, day-of logistics
Output as a table with: milestone, owner, deadline, dependencies, status
Flag any compressed timelines or missing gaps
When ClickUp/Asana is connected, create a project for the event with tasks for each milestone — assign owners and set due dates automatically
When Google Calendar is connected, block milestone deadlines as all-day events with 1-week-prior reminders

Committee Coordinator

Run the organizing committee like a chief of staff.

What it covers

Draft meeting agendas from a topic list or prior action items
After a meeting summary or transcript is provided, extract: decisions made, action items (with owner + deadline), open questions
Track open items across meetings and flag anything overdue
Draft follow-up emails from meeting notes
When Zoom is connected, pull meeting recordings and transcripts to auto-extract action items
When ClickUp/Asana is connected, create sub-tasks from action items and assign to committee members
When Google Drive is connected, store meeting notes in 09-meeting-notes/ in the Knowledge Base

Risk Register Manager

Maintain a live risk log for the event.

What it covers

When risks are described, categorize by: likelihood (H/M/L), impact (H/M/L), and area (venue, sponsor, tech, speaker, ops, weather)
Suggest mitigation actions for each
Output a ranked risk register table
On request, generate a risk summary for the board or steering committee
When ClickUp/Asana is connected, maintain a Risk Register list with custom fields for likelihood, impact, and status
Save the latest risk register snapshot to 09-meeting-notes/risk-register-{YYYY-MM-DD}.md

Board / Stakeholder Briefing Writer

Translate operational status into executive-ready updates.

What it covers

Ask for: current date, event date, key metrics (registrations, sponsor revenue, budget status, open risks)
Output a 1-page status brief: headline status, progress by workstream, key decisions needed, risks
Match the voice and formality level of the organizer's organization
When Canva is connected, generate a visual status deck with branded charts and infographics
When Google Drive is connected, save briefing documents in 09-meeting-notes/board-briefs/

Cross-Team Status Aggregator

Pull status from all workstreams into a single view.

What it covers

Collect updates across all conference roles: program/content readiness, sponsorship pipeline, marketing campaign status, venue/logistics progress, finance/budget health, attendee experience setup
When ClickUp/Asana is connected, query all event-related projects and surface blockers, overdue items, and upcoming deadlines across teams
Produce a traffic-light dashboard: green (on track), yellow (at risk), red (blocked) for each workstream
Flag cross-team dependencies: "Marketing can't announce speakers until Program confirms the lineup" or "Finance can't invoice sponsors until Sponsorship signs contracts"
Output as an executive summary table or a narrative briefing, depending on the audience

Decision Log Keeper

Track every major decision and who made it.

What it covers

After meetings or async approvals, log: decision, date, who decided, rationale, affected workstreams
Maintain a running Decision Log document at 09-meeting-notes/decision-log.md with links to supporting files
Surface past decisions on request: "What did we decide about the venue?" or "When did we approve the catering budget?"
Flag decisions that may need revisiting based on new information or timeline changes

Example tasks for conference chairs

You don't call the skill by name — ask the way you'd brief a colleague. These are requests the skill is written to pick up:

Plan the conference
Build the event timeline
Committee meeting agenda
Board update on the event
What's at risk for the conference
Create tasks in ClickUp
Track in Asana
Schedule a Zoom meeting

Try this firstBuild a 9-month timeline for a 500-person summit on Sept 15

What you get back: A milestone critical path with owners, deadlines, dependencies.

How it works

Always check the shared Knowledge Base first. Never re-ask the organizer for facts that already live there. Save every artifact you produce back into the right subfolder of the KB.
Always start by asking for the event date, scale (# of attendees), and which task the organizer needs right now
When given raw notes, emails, or meeting transcripts, extract structure from them before asking follow-up questions
Produce outputs in clean tables and clear prose — ready to copy-paste into an email or deck
If a request spans multiple workstreams (e.g., "update on everything"), produce a structured briefing across all areas
When creating tasks, use a consistent naming convention: [EVENT-NAME] - Milestone/Task description

Tools it can connect to (optional)

The skill works without any integrations. Connect the tools your team already uses and it can act in them.

Shared Knowledge Base (Google Drive / Dropbox / OneDrive / Notion)

single source of truth for the event; every role reads from and writes to it. The first connector to set up.

Firecrawl

web scraping tool / skill used to bootstrap the Knowledge Base from an existing event website

Google Calendar

block event milestones, committee meetings, and deadline reminders

Gmail

draft and send committee follow-up emails, stakeholder updates

AgentMail

create dedicated event inboxes for committee communications, automated follow-ups, and stakeholder notifications without using personal email

Google Drive

store and retrieve planning documents, meeting notes, decision logs, and templates

ClickUp / Asana

create and track milestones as tasks/projects, assign owners, monitor progress across all workstreams

Zoom

pull meeting recordings and transcripts for automated action item extraction

Canva

generate visual status decks and branded briefing materials

Works with the rest of your AI team

Pull sponsor revenue status from the Sponsorship skill to include in board briefings
Pull budget health from the Finance & Registration skill for financial reporting
Pull speaker confirmation status from the Program & Content skill for timeline tracking
Pull venue and vendor readiness from the Venue & Logistics skill for risk assessment
Pull campaign performance metrics from the Marketing & Communications skill for status updates
Pull attendee registration numbers from the Finance & Registration skill for progress reporting

Sample outputs from the mock conference

What this skill produced for FutureStack 2026, a fictional 800-person conference.

Sara ChenCritical-path timelineRead the sample →Sara ChenRisk registerRead the sample →Sara ChenBoard briefingRead the sample →

Step-by-step guides

How to build a conference planning timeline with ClaudeRead the guide →

How to install the Conference Chair skill

≈ 5 minutes · easiest · no install

In your browser with Claude.ai

Sign in at claude.ai and create a Project — name it after your event and the role, e.g. “Summit — Conference Chair”.
Open conference-general-chair/SKILL.md and copy everything.
Paste it into the Project's instructions and save.
Start chatting — every new chat in that Project uses the skill.

≈ 10 minutes · recommended · Claude Code

All eight skills with one command

Install Node.js 18+ and Git if you don't have them.

In your terminal, run:

npx @msg2ai/conference-team-skills install

Open Claude Code and ask a question for that role — the right skill activates automatically. You can also invoke it directly with /conference-general-chair.

Manual · Git or ZIP

Clone or download the repository

Clone into your Claude skills folder:

git clone https://github.com/msg2ai/conference-team-skills.git ~/.claude/skills/conference-team-skills

Or download the ZIP and move the extracted folder to ~/.claude/skills/conference-team-skills.

Plugin install, the desktop app and IDE extensions, Codex, Cursor and troubleshooting: see the full install guide.

The other seven skills

02 · Program DirectorAI assistant for conference program chairsSee the skill →03 · Head of SponsorshipAI assistant for conference sponsorship leadsSee the skill →04 · CMOAI assistant for conference marketing and communicationsSee the skill →05 · Head of OperationsAI assistant for conference venue and logistics coordinatorsSee the skill →06 · CFOAI assistant for conference finance and registration chairsSee the skill →07 · Chief Experience OfficerAI assistant for conference attendee experience leadsSee the skill →08 · Head of WebAI web builder for conference websitesSee the skill →

Get all eight skills, free

One AI teammate per committee role. MIT licensed — use, modify and redistribute, including for commercial events.

View on GitHub →How to install