// Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
Configure, extend, or contribute to Hermes Agent.
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.
Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's system prompt as KANBAN_GUIDANCE (from agent/prompt_builder.py); this skill is what you load when you want deeper detail on specific scenarios.
Use when a Hermes Kanban worker wants to run Codex CLI as an isolated implementation lane while Hermes keeps ownership of task lifecycle, reconciliation, testing, and handoff.
Article illustrations: type × style × palette consistency.
Zero-install localhost tunnels over SSH via Pinggy.
| name | teams-meeting-pipeline |
| description | Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions. |
| version | 1.1.0 |
| author | Hermes Agent + Teknium |
| license | MIT |
| prerequisites | {"env_vars":["MSGRAPH_TENANT_ID","MSGRAPH_CLIENT_ID","MSGRAPH_CLIENT_SECRET"],"commands":["hermes"]} |
| metadata | {"hermes":{"tags":["Teams","Microsoft Graph","Meetings","Productivity","Operations"],"related_docs":["/docs/guides/microsoft-graph-app-registration","/docs/user-guide/messaging/teams-meetings","/docs/guides/operate-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.
The user is asking to:
Multilingual trigger examples (not exhaustive):
Before using the pipeline, verify these are set in ~/.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.
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
hermes 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 URL
hermes teams-pipeline subscribe \
--resource communications/onlineMeetings/getAllTranscripts \
--notification-url https://<your-public-host>/msgraph/webhook \
--client-state "$MSGRAPH_WEBHOOK_CLIENT_STATE"
hermes teams-pipeline renew-subscription <sub-id> --expiration <iso-8601>
hermes teams-pipeline delete-subscription <sub-id>
hermes teams-pipeline maintain-subscriptions # renew near-expiry ones
hermes teams-pipeline maintain-subscriptions --dry-run # show what would be renewed
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).validate, then token-health, then subscriptions. If all three pass, request a test meeting and check list for a fresh row.list to find the job ID, run <job-id> to replay. If it fails again, show <job-id> to inspect the error and fetch --meeting-id to dry-run the artifact resolution.fetch to pull transcript + run after a job is created.Microsoft Graph caps webhook subscriptions at 72 hours and will not auto-renew them. If maintain-subscriptions is not scheduled, meeting notifications silently stop arriving 3 days after any manual subscription creation.
When the user reports "the pipeline worked yesterday but nothing is arriving today":
hermes teams-pipeline subscriptions — if it's empty or all entries show expirationDateTime in the past, that's the cause.subscribe as shown above.hermes cron add, a systemd timer, or plain crontab. The operator runbook at /docs/guides/operate-teams-meeting-pipeline#automating-subscription-renewal-required-for-production has all three options. 12-hour interval is safe (6x headroom against the 72h limit).fetch --meeting-id on a just-ended meeting may return empty. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally.list shows success) but nothing lands in Teams, check platforms.teams.extra.delivery_mode and the matching target config (incoming_webhook_url OR chat_id OR team_id+channel_id). The writer reads these from config.yaml or TEAMS_* env vars.token-health passes) but Graph API calls return 401/403 when permissions were added but admin consent wasn't re-granted. Have the user revisit the app registration in the Azure portal and click "Grant admin consent" again.Point the user to these when they need more depth than this skill covers:
/docs/guides/microsoft-graph-app-registration/docs/user-guide/messaging/teams-meetings/docs/guides/operate-teams-meeting-pipeline/docs/user-guide/messaging/msgraph-webhook