teams-meeting-pipeline

Teams meeting summaries, job replay, Graph subscriptions.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/productivity/teams-meeting-pipeline/SKILL.md

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable operator guide: copy-paste-ready CLI commands, a decision tree for common asks, and genuinely non-obvious pitfalls (72-hour Graph subscription expiry) with recovery steps. It is concise and well-structured, with only minor tightening possible.

Dimension	Reasoning	Score
Conciseness	The body is efficient — terse command blocks with inline comments, a decision tree, and operator pitfalls — and avoids explaining concepts Claude already knows; minor redundancy (env vars repeated from frontmatter, multilingual trigger list) keeps it just below a 5.	4 / 5
Actionability	Commands are copy-paste ready with concrete flags and placeholders (e.g. 'fetch --join-web-url "<url>" --organizer-user-id <id>'), and the decision tree maps common asks to exact commands, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Sequences are clear with explicit validation checkpoints ('validate, then token-health, then subscriptions; if all three pass...') and recovery steps for the 72h expiry pitfall; it stops short of a 5 because the workflows are diagnostic rather than a single explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with one-level-deep, clearly signaled '/docs/' references in 'Related docs'; no bundle files exist to verify, and structure is good with only minor organization gaps, fitting the 'good structure' anchor.	4 / 5
	Total	17 / 20 Passed

Description

40%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear, distinct niche but is overly terse: it uses noun phrases instead of concrete actions and omits any 'Use when...' trigger guidance, leaving both what and when weakly specified.

Suggestions

Rewrite as concrete third-person actions, e.g. 'Summarizes Teams meetings, replays stored meeting jobs, and manages Microsoft Graph webhook subscriptions.'

Add an explicit trigger clause, e.g. 'Use when the user asks about Teams meeting summaries, transcripts, recordings, action items, or Graph subscription setup and renewal.'

Include common synonyms users say — transcripts, recordings, action items, webhooks — to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists three domain nouns ('Teams meeting summaries, job replay, Graph subscriptions') with no explicit verbs, matching the anchor that names the domain but offers only minimal or generic actions rather than concrete actions.	2 / 5
Completeness	It offers a vague 'what' (a noun list with no verbs) and no 'Use when...' trigger clause, matching the anchor for a vague 'what' with no 'when'; the missing-trigger cap at 3 does not apply because the 'what' itself is vague.	2 / 5
Trigger Term Quality	'Teams meeting', 'summaries', 'replay', and 'Graph subscriptions' are relevant natural terms, but coverage is thin and misses common variations like transcripts, recordings, action items, or webhooks, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Teams + Microsoft Graph niche is specific and unlikely to fire for unrelated skills, with only minor overlap risk against adjacent productivity skills, fitting the 'mostly distinct' anchor.	4 / 5
	Total	11 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/productivity/teams-meeting-pipeline/SKILL.md
Commit: 6327930

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.