Agent skill · operations · nousresearch
teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
Why this skill is useful
Adds specific commands and operational workflows for managing Microsoft Teams meeting summaries and Graph subscriptions that the AI wouldn't reliably generate on its own.
What it needs
Requires hermes installed locally. Requires azure account access. About 4k tokens when loaded. Last updated 2026-08-07. 226,679 stars on the source repository.
What this skill does
Teams Meeting Pipeline Use this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, or any operational question about the Teams meeting pipeline. Works in any language — the triggers below are examples, not an exhaustive list. Everything operator-facing is a hermes teams-pipeline subcommand run via the terminal tool. There are no new model tools for this pipeline — the CLI is the surface. When to use this skill The user is asking to: summarize a Teams meeting / extract action items / pull meeting notes check pipeline status, inspect a stored meeting job, or see recent meetings replay / re-run a stored job that failed or needs a fresh summary validate Microsoft Graph setup after changing env or config troubleshoot "meeting summary never arrived" or "no new meetings are ingesting" manage Graph webhook subscriptions (create, renew, delete, inspect) set up automated subscription renewal (see pitfall below) Multilingual trigger examples (not exhaustive): English: "summarize the Teams meeting", "pipeline status", "replay job X" Turkish: "Teams meeting özetle", "action item çıkar", "toplantı notu", "pipeline durumu", "replay job" Prerequisites Before using the pipeline, verify these are set in ${HERMESHOME:-~/.hermes}/.env: If any are missing, direct the user to the Azure app registration guide at /docs/guides/microsoft-graph-app-registration — they need an Azure AD app registration with admin-consented Graph application permissions before the pipeline will work. Command reference Status and inspection (start here) Re-running / debugging Subscription management Decision tree for common asks User asks "why didn't I get a summary for today's meeting?" → start with list --status failed, then show <job-id> on the relevant row. If the job doesn't exist at all, check subscriptions — the webhook may have expired (see pitfall below). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nousresearch/teams-meeting-pipeline