teams-meeting-pipeline
Skill2 starsChanged 2 months agoApache-2.0View on GitHub
Teams meeting summaries, job replay, Graph subscriptions.
- Reads credentials
14 other projects use a version of this, 11 of them edited.
Adopted by
Most recently taken up by
- rodos4312/Meu-Agentword for word, first seen Nov 15, 2026
- NousResearch/hermes-agentword for word, first seen Nov 13, 2026
- ashleysbrain/skillsedited, first seen Nov 8, 2026
- delorenj/skillsedited, first seen Nov 7, 2026
- Stuko0/alice-agentedited, first seen Oct 13, 2026
- nobodyohm-web/Thotedited, first seen Oct 13, 2026
Used with
Projects with it also use pdf and subagent-driven-development.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillpdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Also in 5 projects that use this
OpenAISkillsubagent-driven-development
Use when executing implementation plans with independent tasks in the current session
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 3
- NousResearch/hermes-agent★ 264k100% same
- barzzly/BarzzLyp_Agent_Skills★ 0100% same
- rodos4312/Meu-Agent★ 0100% same
Edited · 11
- wundercorp/loki★ 2889% same
- delorenj/skills★ 1793% same
- Samin12/skills★ 897% same
- john-data-chen/hermes-agent-backup★ 296% same
- ashleysbrain/skills★ 199% same
- pedroiff0/awesome-skills★ 196% same
- Stuko0/alice-agent★ 185% same
- 2867203296/hermes-agent★ 099% same
- ishanbhosale08/Daedalus★ 096% same
- nobodyohm-web/Thot★ 0100% same
1 more not listed
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- AGENTS.mdAGENTS.md
- frontend-designSkill
- internal-commsSkill
- mcp-builderSkill
- skill-creatorSkill
- theme-factorySkill
- webapp-testingSkill
- web-artifacts-builderSkill
- chatbook-docxSkill
- chatbook-knowledge-captureSkill
- chatbook-meeting-preparationSkill
- chatbook-pptxSkill
- chatbook-xlsxSkill
- petdex-installSkill
- content-strategySkill
- copy-editingSkill
- customer-researchSkill
- airtableSkill
- apple-notesSkill
- apple-remindersSkill
- arxivSkill
- ascii-videoSkill
- blocked-page-recoverySkill
- boxSkill
- codebase-inspectionSkill
- competitor-news-monitorSkill
- design-mdSkill
- document-to-action-itemsSkill
- docxSkill
- dogfoodSkill
- email-inbox-triageSkill
- findmySkill
- gif-searchSkill
- githubSkill
- google-workspaceSkill
- grounded-citationsSkill
- himalayaSkill
- humanizerSkill
- imessageSkill
- llm-wikiSkill
- manim-videoSkill
- mapsSkill
- meeting-action-itemsSkill
- node-inspect-debuggerSkill
- notionSkill
- obsidianSkill
- p5jsSkill
- powerpointSkill
- product-price-monitorSkill
- python-debugpySkill
- reddit-readingSkill
- rss-feedsSkill
- simplify-codeSkill
- songseeSkill
- songwriting-and-ai-musicSkill
- weekly-review-planningSkill
- xlsxSkill
- xurlSkill
- experimental-designSkill
- scientific-critical-thinkingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 3 are common, 0 are distinctive, and 4 are very specific to this project.
3
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 26
Use this skill whenever the user asks about Microsoft Teams meeting summaries, transcripts, recordings, action items, Graph subscriptions, …
- Common: line 34
check pipeline status, inspect a stored meeting job, or see recent meetings
- Very specific: line 47
Before using the pipeline, verify these are set in ${HERMES_HOME:-~/.hermes}/.env:
- Very specific: line 55
If any are missing, direct the user to the Azure app registration guide at /docs/guides/microsoft-graph-app-registration — they need an …
- Common: line 105
When the user reports "the pipeline worked yesterday but nothing is arriving today":
- Very specific: line 106
Run hermes teams-pipeline subscriptions — if it's empty or all entries show expirationDateTime in the past, that's the cause.
- Very specific: line 113
Delivery mode mismatch: If summaries are produced (list shows success) but nothing lands in Teams, check …
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 subscriptionsRe-running / debugging
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 fetch --join-web-url "<url>" --organizer-user-id <id> # organizer-scoped lookup (required for /meet/ short URLs)Subscription management
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 renewedDecision tree for common asks
- User asks "why didn't I get a summary for today's meeting?" → start with
list --status failed, thenshow <job-id>on the relevant row. If the job doesn't exist at all, checksubscriptions— the webhook may have expired (see pitfall below). - User asks "is setup working?" →
validate, thentoken-health, thensubscriptions. If all three pass, request a test meeting and checklistfor a fresh row. - User asks "re-run summary for meeting X" →
listto find the job ID,run <job-id>to replay. If it fails again,show <job-id>to inspect the error andfetch --meeting-idto dry-run the artifact resolution. - User asks "add meeting X to the pipeline" → usually you don't — the pipeline is subscription-driven, not per-meeting. If they want a specific past meeting summarized, use
fetchto pull transcript +runafter a job is created.
Critical pitfall: Graph subscriptions expire in 72 hours
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":
- Run
hermes teams-pipeline subscriptions— if it's empty or all entries showexpirationDateTimein the past, that's the cause. - Recreate with
subscribeas shown above. - Set up automated renewal immediately via
hermes cron add, a systemd timer, or plain crontab. The operator runbook at/docs/guides/operate-teams-meeting-pipeline#automating-subscription-renewal-required-for-productionhas all three options. 12-hour interval is safe (6x headroom against the 72h limit).
Other pitfalls
- Transcript not available yet. Teams takes some time after a meeting ends to generate the transcript artifact.
fetch --meeting-idon a just-ended meeting may return empty. Wait 2-5 minutes and retry, or let the Graph webhook drive ingestion naturally. - Delivery mode mismatch. If summaries are produced (
listshows success) but nothing lands in Teams, checkplatforms.teams.extra.delivery_modeand the matching target config (incoming_webhook_urlORchat_idORteam_id+channel_id). The writer reads these from config.yaml orTEAMS_*env vars. - Graph app permissions. A token acquires cleanly (
token-healthpasses) 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.
Related docs
Point the user to these when they need more depth than this skill covers:
- Azure app registration walkthrough:
/docs/guides/microsoft-graph-app-registration - Full pipeline setup:
/docs/user-guide/messaging/teams-meetings - Operator runbook (renewal automation, troubleshooting, go-live checklist):
/docs/guides/operate-teams-meeting-pipeline - Webhook listener setup:
/docs/user-guide/messaging/msgraph-webhook
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

