reporting-meetings

Query Webex meeting quality, usage reports, workspace metrics, and live monitoring data.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/achobgood/wxops --skill reporting-meetings-achobgood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reporting-meetings
Source: https://github.com/achobgood/wxops/tree/main/.claude/skills/reporting-meetings
Command: npx skills add https://github.com/achobgood/wxops --skill reporting-meetings-achobgood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting actionable analytics out of Webex Meetings requires knowing which of several CLI groups (meeting-qualities, meeting-reports, analytics, workspace-metrics, live-monitoring) answers which question, what OAuth scopes each report needs, and how to parse the varying JSON response shapes. This Skill encodes that mapping plus ready-to-run analysis recipes. ## Core Features & Use Cases - Meeting quality diagnostics: Pull per-participant jitter, latency, and packet loss for a specific meeting and flag sessions exceeding thresholds. - Usage and attendance reporting: Summarize meeting counts by day, list attendees with join/leave times, and rank top meeting hosts. - Historical and workspace analytics: Track messaging adoption trends, room device utilization, workspace occupancy, and live global meeting counts. - Use Case: After an executive complains about a bad all-hands call, run the meeting quality recipe against the meeting ID to identify which participants had packet loss above 5% or latency above 200ms. ## Quick Start Ask the agent to analyze the audio quality of a specific Webex meeting by its meeting ID using the wxcli meeting-qualities command.

Frequently Asked Questions about reporting-meetings

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

FAQPage Schema
How do I check Webex meeting quality for a specific meeting?

Run wxcli meeting-qualities list with the meeting ID to get per-participant jitter, latency, and packet loss in JSON. Find the meeting ID first with wxcli meetings list, then pipe the output through the provided Python recipe to flag sessions exceeding thresholds.

How to get a Webex meeting attendance report?

Use wxcli meeting-reports list-attendees with the site URL and meeting ID to list who joined, including join and leave times. The report only contains people who actually joined; the invited total comes from the totalInvitee field in meeting-reports list.

What OAuth scopes are required for Webex meeting analytics?

Meeting quality, usage reports, historical analytics, and live monitoring require the analytics:read_all scope. Workspace metrics require spark-admin:workspace_metrics_read. Verify your token first with wxcli whoami before running report commands.

Does this skill cover Webex Calling CDR or Contact Center reports?

No. Webex Calling CDR and queue statistics are handled by the separate reporting skill, and Contact Center analytics by the reporting-cc skill. This skill covers only Meetings quality, usage, workspace metrics, and platform analytics.

Why do Webex analytics responses have different JSON shapes?

Response shapes vary across API versions and endpoints: some return lists, others return a single object with parallel metric arrays under a metrics key. The recipes use isinstance checks and field fallbacks to handle both forms safely.