teams-meeting-pipeline

Operate the Teams meeting summary pipeline via Hermes CLI commands.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill teams-meeting-pipeline-luckybbjason1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teams-meeting-pipeline
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/productivity/teams-meeting-pipeline
Command: npx skills add https://github.com/luckybbjason1/trading --skill teams-meeting-pipeline-luckybbjason1

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 operators a single CLI surface to summarize meetings, inspect pipeline status, replay failed jobs, and manage Graph subscriptions. ## Core Features & Use Cases - Pipeline Inspection: Validate configuration, check Graph token health, list recent 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. - Subscription Management: Create, renew, delete, and auto-maintain Microsoft Graph webhook subscriptions to prevent the 72-hour expiration pitfall. - Use Case: A user reports no summary arrived for today's meeting. Run hermes teams-pipeline list --status failed, inspect the job with show, 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 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 summarize a Teams meeting and extract action items?

Use the hermes teams-pipeline CLI to list recent meeting jobs and replay a stored job with `hermes teams-pipeline run <job-id>` to regenerate the summary. The pipeline is subscription-driven, so new meetings are ingested automatically via Graph webhooks.

Why did my Teams meeting summary never arrive?

Start with `hermes teams-pipeline list --status failed` and inspect the job with `show <job-id>`. If no job exists, check `subscriptions` — Microsoft Graph webhook subscriptions expire after 72 hours and silently stop delivering notifications unless renewed.

How do I renew Microsoft Graph webhook subscriptions?

Run `hermes teams-pipeline maintain-subscriptions` to renew near-expiry subscriptions, or `renew-subscription <sub-id>` for a specific one. Schedule it every 12 hours via hermes cron, systemd timer, or crontab to stay ahead of the 72-hour limit.

What credentials does the Teams meeting pipeline require?

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

Why does Graph return 401 or 403 even when token health passes?

This happens when Graph permissions were added to the Azure app registration but admin consent was not re-granted. Revisit the app registration in the Azure portal and click Grant admin consent again.