zoom-meeting-context

Correlates Zoom meeting history against current network state via the Zoom Meetings MCP.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill zoom-meeting-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zoom-meeting-context
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/zoom-meeting-context
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill zoom-meeting-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When someone in a Zoom meeting asks "didn't we have this issue before?", there is no easy way to search past meeting discussions and compare them against the network's actual current state. This Skill closes that gap by searching historical Zoom meetings and reconciling what was discussed then with live network truth.

Core Features & Use Cases

  • Historical Meeting Search: Queries the official Zoom Meetings MCP through the zoom-rtms-mcp pass-through to find prior meetings by topic or approximate timeframe.
  • State Correlation: Reuses NetClaw's existing Member Claw routing (pyATS, NetBox, Splunk) to check the network's current state for the same location or technology discussed historically.
  • Honest Reporting: Explicitly reports when no matching past meeting exists instead of fabricating a correlation, and stays strictly read-only with no configuration changes.
  • Use Case: During an incident call, an engineer asks whether a similar BGP issue in Toronto was discussed before; the Skill finds the prior meeting, summarizes the decisions made, and states whether current BGP state matches or differs.

Quick Start

Ask the agent to search past Zoom meetings for a previous discussion about the Toronto BGP issue and compare it with the network's current state.

Frequently Asked Questions about zoom-meeting-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past Zoom meetings for a previous incident discussion?

Reference the past discussion by topic or approximate timeframe, and the Skill calls zoom_search_historical_meetings through zoom-rtms-mcp, which passes the query to the official Zoom Meetings MCP. It then summarizes what was discussed and decided in any matching meeting.

How does Zoom meeting correlation check current network state?

After finding a relevant past meeting, the Skill reuses NetClaw's existing Member Claw routing path (pyATS, NetBox, Splunk, and similar sources) to verify the current state of the same location or technology, then states plainly whether it matches or differs from the historical discussion.

Does this Skill answer live questions asked during a Zoom meeting?

No. Live in-meeting questions are recognized automatically inside zoom-rtms-mcp's own extractor and routed to the existing investigation path. This Skill only handles the historical-correlation case of searching prior meetings.

What happens when no matching past Zoom meeting is found?

The Skill explicitly says no relevant meeting was found rather than presenting an unrelated result as a match. Fabricating a historical correlation is explicitly prohibited by the specification.

Can this Skill make configuration changes based on meeting history?

No. It is strictly read-only correlation. Any change request, however phrased, still goes through NetClaw's existing device-write approval gate unchanged.

What credentials are required for Zoom meeting history search?

The Skill requires python3 and a ZOOM_MEETING_MCP_CREDENTIAL environment variable. The official Zoom Meetings MCP is remote and OAuth-based, with no local vendoring.