teams-meeting-pipeline

Operate the Teams meeting summary pipeline via Hermes CLI commands.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/brittb-dev/zerogravityclaw --skill teams-meeting-pipeline-brittb-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teams-meeting-pipeline
Source: https://github.com/brittb-dev/zerogravityclaw/tree/main/src/hermes-core/skills/productivity/teams-meeting-pipeline
Command: npx skills add https://github.com/brittb-dev/zerogravityclaw --skill teams-meeting-pipeline-brittb-dev

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 - Status and Inspection: Validate configuration, check Graph token health, list recent or failed 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 the 72-hour expiry pitfall. - Use Case: A user reports that yesterday's meeting summary never arrived. Run hermes teams-pipeline list --status failed to find the job, show <job-id> to inspect the error, and subscriptions to check whether the webhook expired. ## 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 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 generate or 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 show <job-id> on the relevant row. If no job exists, check subscriptions — Microsoft Graph webhook subscriptions expire after 72 hours and do not auto-renew.

How do I renew Microsoft Graph webhook subscriptions automatically?▼

Run hermes teams-pipeline maintain-subscriptions on a schedule via hermes cron add, a systemd timer, or crontab. A 12-hour interval is recommended since Graph caps subscriptions at 72 hours.

What permissions does the Teams meeting pipeline need in Azure?▼

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

Why does transcript fetch 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.

Why do Graph API calls return 401 or 403 after a token acquires successfully?▼

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