teams-meeting-pipeline

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams meeting summaries and transcripts often fail silently due to expired Microsoft 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 webhook subscriptions that expire after 72 hours. - Setup Validation & Troubleshooting: 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 job, show <job-id> to inspect the error, and run <job-id> to replay it after fixing the expired subscription. ## 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?▼

Use the hermes teams-pipeline CLI, which ingests meetings via Microsoft Graph webhook subscriptions and generates summaries with action items. Run `hermes teams-pipeline list` to see recent jobs and `show <job-id>` for full details.

Why did my Teams meeting summary never arrive?▼

The most common cause is an expired Graph webhook subscription, since Microsoft Graph caps subscriptions at 72 hours without auto-renewal. Run `hermes teams-pipeline subscriptions` to check expiration, then recreate and schedule `maintain-subscriptions` every 12 hours.

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

Find the job with `hermes teams-pipeline list --status failed`, inspect it with `show <job-id>`, then replay it using `hermes teams-pipeline run <job-id>`. You can also dry-run artifact resolution with `fetch --meeting-id` before replaying.

What permissions does Microsoft Graph need for Teams transcripts?▼

The pipeline requires 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 2-5 minutes after a meeting ends to generate the transcript artifact, so an immediate fetch may return empty. Wait and retry, or let the Graph webhook drive ingestion naturally once the artifact is ready.