teams-meeting-pipeline

Operates Microsoft Teams meeting summarization, job replay, and Graph webhook subscription management via CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams meeting summaries can silently stop arriving, transcripts get lost, and Microsoft Graph webhook subscriptions expire after 72 hours without warning. This Skill gives you a single operational surface to diagnose, replay, and maintain the entire Teams meeting ingestion pipeline. ## Core Features & Use Cases - Pipeline Diagnostics: Validate configuration, check Graph token health, list recent or failed meeting jobs, and inspect individual job details. - Job Replay and Dry-Runs: Re-run stored jobs to regenerate summaries, or dry-run transcript fetching by meeting ID or join URL without persisting anything. - Subscription Lifecycle Management: Create, renew, delete, and auto-maintain Graph webhook subscriptions to prevent the 72-hour expiration pitfall. - Use Case: A user reports that yesterday's meeting summary never arrived. You run hermes teams-pipeline list --status failed, inspect the failing job with show, and discover the webhook subscription expired — then recreate it and set up automated renewal. ## Quick Start Ask the assistant to check the Teams meeting pipeline status and list any failed meeting jobs using the hermes teams-pipeline commands.

Frequently Asked Questions about teams-meeting-pipeline

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

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

Run hermes teams-pipeline list to find the job ID, then hermes teams-pipeline run <job-id> to replay it. If it fails again, use show <job-id> to inspect the error and fetch --meeting-id to dry-run transcript resolution.

Why did my Teams meeting summaries stop arriving?▼

Microsoft Graph webhook subscriptions expire after 72 hours and do not auto-renew. Run hermes teams-pipeline subscriptions to check expiration, recreate with the subscribe command, and schedule maintain-subscriptions every 12 hours.

What permissions does the Microsoft Graph app registration need?▼

The pipeline requires an Azure AD app registration with admin-consented Graph application permissions. If token-health passes but API calls return 401 or 403, admin consent was not re-granted after adding permissions 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.

How do I verify the Teams pipeline setup is working?▼

Run hermes teams-pipeline validate first, then token-health, then subscriptions. If all three pass, request a test meeting and check hermes teams-pipeline list for a fresh job row.