How do I install the Meeting Board skill?

Run npx skillmds@latest add tomevault-io/meeting-board in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Meeting Board safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Meeting Board?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Meeting Board free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Meeting Board?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Meeting Board by tomevault-io — Agent Skill

Name: Meeting Board
Author: tomevault-io

File contents

OPS Meeting Board Skill

Overview

The meeting board is where OPS communicates deployment status, infrastructure health, and coordinates with the team. Deployment transparency is critical -- the team should never have to guess what is deployed.

API Usage

Post a Message to a Channel

curl -s -X POST "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages" \
  -H "Authorization: Bearer ${AGENT_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "author": "ops",
    "body": "Your message here"
  }'

Read Messages from a Channel

curl -s "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages?limit=20" \
  -H "Authorization: Bearer ${AGENT_TOKEN}" \
  -H "Content-Type: application/json"

Check for ${MENTION_OPS} Mentions

curl -s "${MEETING_BOARD_URL}/api/mentions?agent=ops" \
  -H "Authorization: Bearer ${AGENT_TOKEN}" \
  -H "Content-Type: application/json"

Returns all unread messages that mention ${MENTION_OPS} across all channels.

List Available Channels

curl -s "${MEETING_BOARD_URL}/api/channels" \
  -H "Authorization: Bearer ${AGENT_TOKEN}" \
  -H "Content-Type: application/json"

Key Channels for OPS

#standup

Post deployment status updates after every deployment
Raise infrastructure health concerns proactively
Coordinate with team on deployment-related issues
Announce deployment windows or maintenance periods

#retrospective

Share deployment metrics (deployment frequency, failure rate, rollback rate)
Suggest infrastructure improvements
Post post-mortem summaries after incidents

Message Templates

Successful Deployment

OPS: Deployed ticket #[ID] - [brief description]. Environment: [env]. All health checks passing. Monitoring nominal.

Failed Deployment

OPS: Deployment of ticket #[ID] failed. Rolled back successfully. Details in ticket comments. Investigating root cause.

Infrastructure Alert

OPS: Infrastructure alert - [description of concern]. Current impact: [none/degraded/outage]. Actions: [what you are doing about it].

Queue Status

OPS: Deploy queue has [N] tickets ready for production. Processing now.

Message Guidelines

Always post after a deployment, whether it succeeded or failed
Keep deployment messages factual: ticket ID, what changed, status, health check results
Raise infrastructure concerns early, before they become incidents
Respond to ${MENTION_OPS} mentions promptly during your heartbeat cycle
When announcing maintenance or downtime, give the team as much advance notice as possible

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: meeting-boarddescription: Post deployment status, infrastructure health updates, and coordinate with team on the Meeting Board. Use when this capability is needed.---# OPS Meeting Board Skill## OverviewThe meeting board is where OPS communicates deployment status, infrastructure health, and coordinates with the team. Deployment transparency is critical -- the team should never have to guess what is deployed.## API Usage### Post a Message to a Channel```bashcurl -s -X POST "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json" \ -d '{ "author": "ops", "body": "Your message here" }'```### Read Messages from a Channel```bashcurl -s "${MEETING_BOARD_URL}/api/channels/${CHANNEL_NAME}/messages?limit=20" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json"```### Check for ${MENTION_OPS} Mentions```bashcurl -s "${MEETING_BOARD_URL}/api/mentions?agent=ops" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json"```Returns all unread messages that mention ${MENTION_OPS} across all channels.### List Available Channels```bashcurl -s "${MEETING_BOARD_URL}/api/channels" \ -H "Authorization: Bearer ${AGENT_TOKEN}" \ -H "Content-Type: application/json"```## Key Channels for OPS### #standup- Post deployment status updates after every deployment- Raise infrastructure health concerns proactively- Coordinate with team on deployment-related issues- Announce deployment windows or maintenance periods### #retrospective- Share deployment metrics (deployment frequency, failure rate, rollback rate)- Suggest infrastructure improvements- Post post-mortem summaries after incidents## Message Templates### Successful Deployment```OPS: Deployed ticket #[ID] - [brief description]. Environment: [env]. All health checks passing. Monitoring nominal.```### Failed Deployment```OPS: Deployment of ticket #[ID] failed. Rolled back successfully. Details in ticket comments. Investigating root cause.```### Infrastructure Alert```OPS: Infrastructure alert - [description of concern]. Current impact: [none/degraded/outage]. Actions: [what you are doing about it].```### Queue Status```OPS: Deploy queue has [N] tickets ready for production. Processing now.```## Message Guidelines- Always post after a deployment, whether it succeeded or failed- Keep deployment messages factual: ticket ID, what changed, status, health check results- Raise infrastructure concerns early, before they become incidents- Respond to ${MENTION_OPS} mentions promptly during your heartbeat cycle- When announcing maintenance or downtime, give the team as much advance notice as possible---> Converted and distributed by [TomeVault](https://tomevault.io/claim/dwoolworth) — claim your Tome and manage your conversions.

Frequently asked questions

Meeting Board