teams-meeting-pipeline

Summarizes Microsoft Teams meetings and manages Graph webhook subscriptions via CLI commands.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill teams-meeting-pipeline-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teams-meeting-pipeline
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/productivity/teams-meeting-pipeline
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill teams-meeting-pipeline-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams meeting summaries and transcripts often fail silently due to expired Graph webhook subscriptions, missing permissions, or delivery misconfigurations, leaving operators without visibility into why meeting notes never arrived. ## Core Features & Use Cases - Meeting Summaries & Replay: List, inspect, and re-run stored meeting jobs to regenerate summaries and action items on demand. - Graph Subscription Management: Create, renew, delete, and auto-maintain Microsoft Graph webhook subscriptions that expire every 72 hours. - Diagnostics & Validation: Validate configuration, check Graph token health, and dry-run transcript fetching by meeting ID or join URL. - Use Case: A user reports that yesterday's meeting summary never arrived. Run hermes teams-pipeline list --status failed to find the failed job, show <job-id> to inspect the error, and run <job-id> to replay it after fixing the issue. ## Quick Start Ask the agent to check the Teams meeting pipeline status and summarize the most recent meeting.

Frequently Asked Questions about teams-meeting-pipeline

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

FAQPage Schema
How do I summarize a Microsoft Teams meeting automatically?▼

Teams meeting summaries are produced by a subscription-driven pipeline: Microsoft Graph webhooks notify the system when transcripts are ready, and jobs are created automatically. Use hermes teams-pipeline list to see recent meetings and show <job-id> for details.

How do I replay a failed Teams meeting summary job?▼

Run hermes teams-pipeline list --status failed to find the job ID, then hermes teams-pipeline run <job-id> to re-summarize and re-deliver. If it fails again, inspect the error with show <job-id> and dry-run artifact resolution with fetch --meeting-id.

Why did my Teams meeting summaries stop arriving after a few days?▼

Microsoft Graph caps webhook subscriptions at 72 hours and does not auto-renew them. Check hermes teams-pipeline subscriptions for expired entries, recreate with subscribe, and schedule maintain-subscriptions every 12 hours via cron or a systemd timer.

What permissions does Microsoft Graph need for Teams transcripts?▼

You need an Azure AD app registration with admin-consented Graph application permissions, configured via MSGRAPH_TENANT_ID, MSGRAPH_CLIENT_ID, and MSGRAPH_CLIENT_SECRET. If API calls return 401/403 after adding permissions, re-grant admin consent in the Azure portal.

Why is the Teams transcript empty right after a meeting ends?▼

Teams takes time to generate the transcript artifact after a meeting ends, so fetch --meeting-id may return empty immediately. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally.