Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill meeting-insights-analyzergit clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLICWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mattmre/evokore-mcp-public/meeting-insights-analyzer)<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/meeting-insights-analyzer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/meeting-insights-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/meeting-insights-analyzer"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/meeting-insights-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.02304 |
| Opus 5 | $0.00028 | $0.01152 |
| Sonnet 5 | $0.00011 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
meeting-insights-analyzer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to meeting-insights-analyzer — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Insights Analyzer
This skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.
When to Use This Skill
- Analyzing your communication patterns across multiple meetings
- Getting feedback on your leadership and facilitation style
- Identifying when you avoid difficult conversations
- Understanding your speaking habits and filler words
- Tracking improvement in communication skills over time
- Preparing for performance reviews with concrete examples
- Coaching team members on their communication style
What This Skill Does
-
Pattern Recognition: Identifies recurring behaviors across meetings like:
- Conflict avoidance or indirect communication
- Speaking ratios and turn-taking
- Question-asking vs. statement-making patterns
- Active listening indicators
- Decision-making approaches
-
Communication Analysis: Evaluates communication effectiveness:
- Clarity and directness
- Use of filler words and hedging language
- Tone and sentiment patterns
- Meeting control and facilitation
-
Actionable Feedback: Provides specific, timestamped examples with:
- What happened
- Why it matters
- How to improve
-
Trend Tracking: Compares patterns over time when analyzing multiple meetings
How to Use
Basic Setup
- Download your meeting transcripts to a folder (e.g.,
~/meetings/) - Navigate to that folder in Claude Code
- Ask for the analysis you want
Quick Start Examples
Analyze all meetings in this folder and tell me when I avoided conflict.
Look at my meetings from the past month and identify my communication patterns.
Compare my facilitation style between these two meeting folders.
Advanced Analysis
Analyze all transcripts in this folder and:
1. Identify when I interrupted others
2. Calculate my speaking ratio
3. Find moments I avoided giving direct feedback
4. Track my use of filler words
5. Show examples of good active listening
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 331 lines · 56 tokens per session scan A 3460b0db90bf
meeting-insights-analyzer is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 2,304 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to meeting-insights-analyzer, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
code-walkthrough
Use when guiding a developer through unfamiliar codebases via step-by-step walkthroughs.
docs-style-guide
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
oo-api-bible
API.Bible (scripture.api.bible). Use this skill for ANY API.Bible request — searching and reading data. Whenever a task involves API.Bible, use this skill instead of calling the API directly.
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
peak-end-rule
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.