teams-meeting-pipeline

Operate Teams meeting summarization pipelines and Microsoft Graph webhook subscriptions via Nyxora CLI.

5|2|Updated May 26, 2026
One-click install
npx skills add https://github.com/perasyudha/Nyxora --skill teams-meeting-pipeline-perasyudha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teams-meeting-pipeline
Source: https://github.com/perasyudha/Nyxora/tree/main/packages/core/playbooks/productivity/teams-meeting-pipeline
Command: npx skills add https://github.com/perasyudha/Nyxora --skill teams-meeting-pipeline-perasyudha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams meeting summaries and transcripts often fail silently due to expired Graph webhook subscriptions, missing admin consent, or delivery misconfiguration, leaving operators without visibility into why summaries never arrive. ## Core Features & Use Cases - Pipeline Inspection: List recent meeting jobs, filter by status, and show full job details to diagnose failures. - Job Replay and Dry-Run Fetching: Re-run stored jobs to regenerate summaries, or fetch transcripts by meeting ID or join URL without persisting. - Subscription Management: Create, renew, delete, and auto-maintain Microsoft Graph webhook subscriptions that expire every 72 hours. - Use Case: A user reports that meeting summaries stopped arriving. Run nyxora teams-pipeline subscriptions to find the expired webhook, recreate it with subscribe, and schedule maintain-subscriptions on a 12-hour cron to prevent recurrence. ## Quick Start Ask the assistant to check the Teams meeting pipeline status and list any failed meeting jobs using the nyxora 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 summarize a Microsoft Teams meeting automatically?

The pipeline is subscription-driven: a Microsoft Graph webhook notifies the system when a meeting ends, and the transcript is fetched and summarized automatically. Use `nyxora teams-pipeline list` to see recent jobs and `show <job-id>` for details.

Why did my Teams meeting summary never arrive?

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

How do I replay a failed Teams meeting summary job?

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

What permissions does the Microsoft Graph app registration need?

The Azure AD app registration needs 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; revisit the Azure portal and click Grant admin consent.

Why does fetching a transcript return empty right after a meeting ends?

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