teams-meeting-pipeline

Operate the Microsoft Teams meeting summary pipeline via Hermes CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually summarizing Microsoft Teams meetings, tracking pipeline job status, and managing short-lived Microsoft Graph webhook subscriptions that expire after 72 hours creates operational overhead and risks missed meeting action items and lost transcript data for teams.

Core Features & Use Cases

  • End-to-End Pipeline Control: Summarize Teams meetings, extract action items, replay failed summary jobs, and inspect detailed job status via the Hermes CLI.
  • Webhook Subscription Management: Create, renew, and monitor Microsoft Graph webhook subscriptions to automate meeting transcript ingestion, with explicit guidance for the critical 72-hour expiration pitfall that causes silent pipeline failures.
  • Use Case: A distributed project team that relies on Teams meeting summaries for sprint tracking can use this Skill to automatically ingest new meeting transcripts, re-run failed summary generation, and ensure webhook subscriptions are renewed so no action items or key decisions are missed.

Quick Start

Use the teams-meeting-pipeline skill to check your Teams meeting pipeline status and confirm all active Graph subscriptions are not nearing expiration.

Frequently Asked Questions about teams-meeting-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Microsoft Teams meeting summaries and action item extraction?

Automate Teams meeting summaries by operating a meeting summary pipeline that ingests meeting transcripts, generates meeting summaries, and extracts action items. Use the Hermes CLI to trigger transcript ingestion and summary generation for enterprise Teams workflows.

Why do my Microsoft Graph webhook subscriptions stop working after 72 hours?

Microsoft Graph webhook subscriptions expire after 72 hours, causing silent pipeline failures for meeting transcript ingestion. You must create, renew, and monitor webhook subscriptions regularly to ensure continuous automated meeting summary generation.

What do I need to configure before automating Teams meeting transcript ingestion?

You need valid Microsoft Graph application permissions with admin consent, a configured Hermes CLI, and required environment variables for Microsoft Graph tenant, client ID, and client secret to automate Teams meeting transcript ingestion correctly.

How do I replay failed meeting summary jobs and inspect pipeline status?

Replay failed meeting summary jobs and inspect detailed pipeline status by executing pipeline operational tasks through the Hermes CLI. This allows you to re-run failed summary generation and view detailed job status for enterprise Teams workflows.

Can I troubleshoot missing Teams meeting summaries in my enterprise pipeline?

Troubleshoot missing meeting summaries by inspecting pipeline status, verifying Microsoft Graph webhook subscription health, and replaying failed summary jobs. This ensures meeting transcripts are ingested and action items are successfully extracted.

What is the best way to manage Microsoft Graph webhook subscriptions for Teams meeting automation?

Manage Microsoft Graph webhook subscriptions by creating, renewing, and monitoring them to automate meeting transcript ingestion. The pipeline provides explicit guidance for the critical 72-hour expiration pitfall to prevent silent pipeline failures.