Skip to main content

teams-meeting-pipeline

Enables users to manage Microsoft Teams meeting summaries and subscriptions via the Hermes CLI, enhancing productivity and operations.

Install this skill

or
56/100

Security score

The teams-meeting-pipeline skill was audited on May 17, 2026 and we found 12 security issues across 3 threat categories. Review the findings below before installing.

Categories Tested

Security Issues

medium line 33

Webhook reference - potential data exfiltration

SourceSKILL.md
33- manage Graph webhook subscriptions (create, renew, delete, inspect)
low line 63

Webhook reference - potential data exfiltration

SourceSKILL.md
63hermes teams-pipeline subscriptions # current Graph webhook subscriptions
low line 79

Webhook reference - potential data exfiltration

SourceSKILL.md
79--notification-url https://<your-public-host>/msgraph/webhook \
low line 80

Webhook reference - potential data exfiltration

SourceSKILL.md
80--client-state "$MSGRAPH_WEBHOOK_CLIENT_STATE"
medium line 90

Webhook reference - potential data exfiltration

SourceSKILL.md
90- 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` — th
medium line 97

Webhook reference - potential data exfiltration

SourceSKILL.md
97Microsoft 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 man
medium line 106

Webhook reference - potential data exfiltration

SourceSKILL.md
106- **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
medium line 107

Webhook reference - potential data exfiltration

SourceSKILL.md
107- **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
medium line 116

Webhook reference - potential data exfiltration

SourceSKILL.md
116- Webhook listener setup: `/docs/user-guide/messaging/msgraph-webhook`
medium line 42

Access to hidden dotfiles in home directory

SourceSKILL.md
42Before using the pipeline, verify these are set in `~/.hermes/.env`:
medium line 42

Access to .env file

SourceSKILL.md
42Before using the pipeline, verify these are set in `~/.hermes/.env`:
low line 79

External URL reference

SourceSKILL.md
79--notification-url https://<your-public-host>/msgraph/webhook \
Scanned on May 17, 2026
View Security Dashboard
Installation guide →