teams-meeting-pipeline

Operate the Teams meeting summary pipeline via GPUCLOUD CLI commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams meeting summaries can silently stop arriving, jobs fail without visibility, and Microsoft Graph webhook subscriptions expire after 72 hours. This Skill gives you a single CLI surface to summarize meetings, inspect pipeline status, replay failed jobs, and manage Graph subscriptions. ## Core Features & Use Cases - Status and Inspection: Validate configuration, check Graph token health, list recent meeting jobs, and inspect individual job details. - Replay and Debugging: Re-run stored jobs to regenerate summaries, or dry-run transcript resolution by meeting ID or join URL. - Subscription Management: Create, renew, delete, and auto-maintain Microsoft Graph webhook subscriptions to prevent silent ingestion failures. - Use Case: A user reports no summary arrived for today's meeting. Run gpucloud teams-pipeline list --status failed, inspect the job with show <job-id>, and if no job exists, check subscriptions for an expired webhook and recreate it. ## Quick Start Ask the assistant to check the Teams meeting pipeline status and list any failed meeting jobs using the gpucloud 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 Teams meeting and extract action items?▼

Use gpucloud teams-pipeline list to find the meeting job, then run gpucloud teams-pipeline run <job-id> to replay it and regenerate the summary. For a specific past meeting, use fetch --meeting-id to resolve the transcript first.

Why did my Teams meeting summary never arrive?▼

Start with gpucloud teams-pipeline list --status failed, then inspect the job with show <job-id>. If no job exists, run subscriptions to check whether the Microsoft Graph webhook expired, since Graph caps subscriptions at 72 hours without auto-renewal.

How do I renew Microsoft Graph webhook subscriptions automatically?▼

Run gpucloud teams-pipeline maintain-subscriptions to renew near-expiry subscriptions, and schedule it via gpucloud cron add, a systemd timer, or crontab. A 12-hour interval provides safe headroom against the 72-hour Graph expiration limit.

What environment variables does the Teams meeting pipeline require?▼

The pipeline requires MSGRAPH_TENANT_ID, MSGRAPH_CLIENT_ID, and MSGRAPH_CLIENT_SECRET set in ~/.gpucloud/.env. These come from an Azure AD app registration with admin-consented Microsoft Graph application permissions.

Why do Graph API calls return 401 or 403 after token health passes?▼

A token can acquire cleanly while API calls fail when permissions were added but admin consent was not re-granted. Revisit the app registration in the Azure portal and click Grant admin consent again.

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 may return empty immediately. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally.