What is teams-meeting-pipeline?

An operational tool for a Microsoft Teams meeting-summary pipeline. It works with meeting transcripts and recordings to produce summaries and action items, while also exposing the pipeline's status and Microsoft Graph subscriptions.

It is for summarizing Teams meetings, extracting action items, checking pipeline jobs, replaying failures, validating setup, and managing Graph webhook subscriptions.

It helps investigate missing meeting summaries, failed processing jobs, and meetings that are not being received. It also provides a way to rerun jobs and manage the webhooks that notify the pipeline about new meetings.

teams-meeting-pipeline — Skill for Claude Code and Codex by johnson778

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add johnson7788/MultiUserClaw --skill teams-meeting-pipeline

Clone the repo

git clone --depth 1 https://github.com/johnson7788/MultiUserClaw

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/johnson7788/multiuserclaw/teams-meeting-pipeline/github.svg)](https://agentmods.dev/skills/johnson7788/multiuserclaw/teams-meeting-pipeline)

Your own site

<a href="https://agentmods.dev/skills/johnson7788/multiuserclaw/teams-meeting-pipeline"><img src="https://agentmods.dev/badge/skills/johnson7788/multiuserclaw/teams-meeting-pipeline/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/johnson7788/multiuserclaw/teams-meeting-pipeline"><img src="https://agentmods.dev/badge/skills/johnson7788/multiuserclaw/teams-meeting-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,568 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 97% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.01568
Opus 5	$0.00015	$0.00784
Sonnet 5	$0.00006	$0.00314
Haiku 4.5	$0.00003	$0.00157

Measured 7d ago against content hash 5d3091690cf5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

teams-meeting-pipeline scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to teams-meeting-pipeline — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

hermes-agent/skills/productivity/teams-meeting-pipeline/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 ${HERMES_HOME:-~/.hermes}/.env:

MSGRAPH_TENANT_ID=...
MSGRAPH_CLIENT_ID=...
MSGRAPH_CLIENT_SECRET=...

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)

hermes teams-pipeline validate              # config snapshot — run first after any change
hermes teams-pipeline token-health          # Graph token status
hermes teams-pipeline token-health --force-refresh   # force a fresh token acquisition
hermes teams-pipeline list                  # recent meeting jobs
hermes teams-pipeline list --status failed  # only failed jobs
hermes teams-pipeline show <job-id>         # full detail of one job
hermes teams-pipeline subscriptions         # current Graph webhook subscriptions

Read the full file on GitHub · 117 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 117 lines · 31 tokens per session scan A 5d3091690cf5

Subscribe to this mod's changes

teams-meeting-pipeline is a skill published in the GitHub repository johnson7788/MultiUserClaw (319 stars, last pushed 29d ago), licensed MIT. It adds 31 tokens to every session and 1,568 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to teams-meeting-pipeline, differing in 8 lines, and is treated as a copy.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

teams-meeting-pipeline