teams-meeting-pipeline

Operate the Teams meeting summary pipeline via Hermes CLI commands.

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

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 health, 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 resolution 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 <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 summarize the most recent meeting 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 Microsoft Teams meeting with Hermes CLI?▼

Use hermes teams-pipeline list to find the meeting job ID, then run hermes teams-pipeline run <job-id> to replay and regenerate the summary. For a dry-run without persisting, use fetch --meeting-id or fetch --join-web-url.

Why did my Teams meeting summary never arrive?▼

Start with hermes teams-pipeline list --status failed, then inspect the job with show <job-id>. If no job exists, check subscriptions — Microsoft Graph webhook subscriptions expire after 72 hours and do not auto-renew, so notifications silently stop.

What environment variables does the Teams meeting pipeline require?▼

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

How do I prevent Microsoft Graph subscriptions from expiring?▼

Schedule hermes teams-pipeline maintain-subscriptions via hermes cron add, a systemd timer, or crontab at a 12-hour interval. Graph caps subscriptions at 72 hours, so automated renewal is required for production use.

Why do Graph API calls return 401 or 403 after 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.