Teams Meeting Pipeline — Teams meeting summaries, job replay, Graph subscriptions
Teams Meeting Pipeline — Teams meeting summaries, job replay, Graph subscriptions
Start with meaning, then move to detail.
This lesson explains Teams Meeting Pipeline — Teams meeting summaries, job replay, Graph subscriptions as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, When to use this skill, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Teams Meeting Pipeline — Teams meeting summaries, job replay, Graph subscriptions without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Teams meeting summaries, job replay, Graph subscriptions
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03When to use this skill
Read this after the foundation, then connect it to the previous step.
- 04Prerequisites
Read this after the foundation, then connect it to the previous step.
- 05Command reference
Read this after the foundation, then connect it to the previous step.
- 06Status and inspection (start here)
Read this after the foundation, then connect it to the previous step.
- 07Re-running / debugging
Read this after the foundation, then connect it to the previous step.
- 08Subscription management
Read this after the foundation, then connect it to the previous step.
- 09Decision tree for common asks
Read this after the foundation, then connect it to the previous step.
- 10Critical pitfall: Graph subscriptions expire in 72 hours
Finish here to verify the result and special cases.
Copy only after you understand the effect.
MSGRAPH_TENANT_ID=...
MSGRAPH_CLIENT_ID=...
MSGRAPH_CLIENT_SECRET=...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 subscriptionshermes teams-pipeline run <job-id> # replay a stored job (re-summarize, re-deliver)
hermes teams-pipeline fetch --meeting-id <id> # dry-run: resolve meeting + transcript without persisting
hermes teams-pipeline fetch --join-web-url "<url>" # dry-run by join URLRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.