AGENT SKILL

teams-meeting-pipeline

Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

License 许可
MIT
最近更新
2026-08-31
Stars
★ 0
Forks
0

01 前言 Front Matter

name
teams-meeting-pipeline
author
Hermes Agent + Teknium
license
MIT
version
1.1.0
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" ] } }
description
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
prerequisites
{ "commands": [ "hermes" ], "env_vars": [ "MSGRAPH_TENANT_ID", "MSGRAPH_CLIENT_ID", "MSGRAPH_CLIENT_SECRET" ] }

03 SKILL.md 正文

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/.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

Re-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

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 renewed

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).
  • User asks "is setup working?" → validate, then token-health, then subscriptions. If all three pass, request a test meeting and check list for a fresh row.
  • User asks "re-run summary for meeting X" → 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.
  • 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 fetch to pull transcript + run after 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":

  1. Run hermes teams-pipeline subscriptions — if it's empty or all entries show expirationDateTime in the past, that's the cause.
  2. Recreate with subscribe as shown above.
  3. 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-production has 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-id on 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 (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.
  • Graph app permissions. A token acquires cleanly (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.

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

04 同仓库更多 Skills

lzy18001500226
lzy18001500226/MoSim

skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

★ 0
lzy18001500226
lzy18001500226/MoSim

skill-creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

★ 0
lzy18001500226
lzy18001500226/MoSim

openai-docs

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.

★ 0
lzy18001500226
lzy18001500226/MoSim

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

★ 0
lzy18001500226
lzy18001500226/MoSim

skill-creator-cc

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

★ 0
lzy18001500226
lzy18001500226/MoSim

prd-writing-guide

Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.

★ 0