SkillAtlasSkill 详情

meeting-insights-analyzer

This is the open-source content repository behind

审核状态:已审核Quality 80Security 88

复制安装命令

用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。

复制前请先查看来源、License 和安全提示。

项目 README

来源文件:README.md

抓取于 2026年9月4日

Skill Store — Marketplace Repository

This is the open-source content repository behind Skill Store. It stores every approved Agent Skill, the records that go with it, and the automated security audits published with each skill.

This repo is a companion to the Skill Store platform, not the place to submit skills. Skills are added through skillstore.io — its review pipeline writes to this repo automatically. Please do not open a pull request here to add a skill; PRs adding skills will be closed. See Contributing a skill below.

Installing a skill

The recommended way to install any skill is the skillstore CLI — one command works for both Claude Code and Codex:

npx skillstore add author/skill-name

For example:

npx skillstore add aiskillstore/code-review

It downloads the skill and drops it into the right skills/ directory for your tool. Claude Code auto-discovers it; for Codex, restart the session.

Prefer to do it by hand, or installing via Claude Web? See the full Installation Guides for every method (CLI, manual, and ZIP upload) and the scope directories (~/.agents/skills/, .claude/skills/, ~/.claude/skills/, .codex/skills/, …).

Contributing a skill

Submit through the platform — not through a pull request:

  1. Go to skillstore.io/submit.
  2. Enter the GitHub repository URL that contains your SKILL.md.
  3. Your submission runs through automated security analysis.
  4. A maintainer reviews and approves it.
  5. On approval, the skill is published here and appears on skillstore.io.

What makes a valid skill

  • SKILL.md — the skill definition (required, per the Agent Skills spec)
  • Supporting files the skill references (optional)
  • LICENSE (recommended)

Security audit

Every submission is scanned automatically before it can be published. The audit flags things like:

  • Dangerous code patterns (eval, exec, raw system commands)
  • File access outside the project scope
  • Network calls to external hosts
  • Obfuscated or minified code
  • Credential / secret handling

Security analysis is report-only: findings inform maintainers and users, but a risk result does not automatically block an otherwise approved skill from being published. See our Security Trust Center for the methodology, limitations, and risk-level definitions.

Live Security Passport example:

Skillstore security

Repository layout

.
├── skills/        # Approved, published skills (one folder each, with SKILL.md)
├── pending/       # Submissions awaiting review
├── packages/
│   ├── cli/       # The `skillstore` CLI (npx skillstore add …)
│   └── skillstore/
├── schemas/       # JSON schemas for skill records
├── scripts/       # Maintenance & scoring scripts
└── .github/workflows/   # Submission, audit, and sync automation

The contents of this repo are maintained by Skill Store's automated pipeline. Manual changes are limited to maintainers.

Links

License

The marketplace catalog is MIT-licensed. Individual skills carry their own licenses — check each skill's LICENSE file.

其他

中风险

  • 来源需自行核对维护者身份。
  • 未检测到明显脚本安装指令。
  • 未检测到明显外部权限要求。
  • 未检测到高风险命令。
  • 扫描发现:1 条。

Codex — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/aiskillstore/marketplace.git
  3. 将 "skills/89jobrien/meeting-insights-analyzer" 文件夹复制到 Codex 的 skills 目录中。
  4. 重启 Codex 让新的 skill 生效。

Codex — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Codex 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Codex 让新的 skill 生效。

Claude Code — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/aiskillstore/marketplace.git
  3. 将 "skills/89jobrien/meeting-insights-analyzer" 文件夹复制到 Claude Code 的 skills 目录中。
  4. 重启 Claude Code 让新的 skill 生效。

Claude Code — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Claude Code 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Claude Code 让新的 skill 生效。

Cursor — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/aiskillstore/marketplace.git
  3. 将 "skills/89jobrien/meeting-insights-analyzer" 文件夹复制到 Cursor 的 skills 目录中。
  4. 重启 Cursor 让新的 skill 生效。

Cursor — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Cursor 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Cursor 让新的 skill 生效。

GitHub Copilot — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/aiskillstore/marketplace.git
  3. 将 "skills/89jobrien/meeting-insights-analyzer" 文件夹复制到 GitHub Copilot 的 skills 目录中。
  4. 重启 GitHub Copilot 让新的 skill 生效。

GitHub Copilot — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 GitHub Copilot 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 GitHub Copilot 让新的 skill 生效。

Windsurf — Git Clone 安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 克隆仓库:git clone https://github.com/aiskillstore/marketplace.git
  3. 将 "skills/89jobrien/meeting-insights-analyzer" 文件夹复制到 Windsurf 的 skills 目录中。
  4. 重启 Windsurf 让新的 skill 生效。

Windsurf — 手动复制安装

  1. 安装前请先查看来源仓库和风险报告。
  2. 从源仓库下载 SKILL.md 及相关文件。
  3. 在 Windsurf 的 skills 目录中创建新文件夹。
  4. 将所有 skill 文件复制到新文件夹中。
  5. 重启 Windsurf 让新的 skill 生效。
查看 SKILL.md 原文
name: meeting-insights-analyzer
description: Analyzes meeting transcripts and recordings to uncover behavioral patterns,
  communication insights, and actionable feedback. Identifies when you avoid conflict,
  use filler words, dominate conversations, or miss opportunities to listen. Perfect
  for professionals seeking to improve their communication and leadership skills.
author: Joseph OBrien
status: unpublished
updated: '2025-12-23'
version: 1.0.1
tag: skill
type: skill

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

  1. 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
  2. Communication Analysis: Evaluates communication effectiveness:

    • Clarity and directness
    • Use of filler words and hedging language
    • Tone and sentiment patterns
    • Meeting control and facilitation
  3. Actionable Feedback: Provides specific, timestamped examples with:

    • What happened
    • Why it matters
    • How to improve
  4. Trend Tracking: Compares patterns over time when analyzing multiple meetings

How to Use

Basic Setup

  1. Download your meeting transcripts to a folder (e.g., ~/meetings/)
  2. Navigate to that folder in Claude Code
  3. 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

Instructions

When a user requests meeting analysis:

  1. Discover Available Data

    • Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)
    • Check if files contain speaker labels and timestamps
    • Confirm the date range of meetings
    • Identify the user's name/identifier in transcripts
  2. Clarify Analysis Goals

    If not specified, ask what they want to learn:

    • Specific behaviors (conflict avoidance, interruptions, filler words)
    • Communication effectiveness (clarity, directness, listening)
    • Meeting facilitation skills
    • Speaking patterns and ratios
    • Growth areas for improvement
  3. Analyze Patterns

    For each requested insight:

    Conflict Avoidance:

    • Look for hedging language ("maybe", "kind of", "I think")
    • Indirect phrasing instead of direct requests
    • Changing subject when tension arises
    • Agreeing without commitment ("yeah, but...")
    • Not addressing obvious problems

    Speaking Ratios:

    • Calculate percentage of meeting spent speaking
    • Count interruptions (by and of the user)
    • Measure average speaking turn length
    • Track question vs. statement ratios

    Filler Words:

    • Count "um", "uh", "like", "you know", "actually", etc.
    • Note frequency per minute or per speaking turn
    • Identify situations where they increase (nervous, uncertain)

    Active Listening:

    • Questions that reference others' previous points
    • Paraphrasing or summarizing others' ideas
    • Building on others' contributions
    • Asking clarifying questions

    Leadership & Facilitation:

    • Decision-making approach (directive vs. collaborative)
    • How disagreements are handled
    • Inclusion of quieter participants
    • Time management and agenda control
    • Follow-up and action item clarity
  4. Provide Specific Examples

    For each pattern found, include:

    ### [Pattern Name]
    
    **Finding**: [One-sentence summary of the pattern]
    
    **Frequency**: [X times across Y meetings]
    
    **Examples**:
    
    1. **[Meeting Name/Date]** - [Timestamp]
    
       **What Happened**:
       > [Actual quote from transcript]
    
       **Why This Matters**:
       [Explanation of the impact or missed opportunity]
    
       **Better Approach**:
       [Specific alternative phrasing or behavior]
    
    [Repeat for 2-3 strongest examples]
    
  5. Synthesize Insights

    After analyzing all patterns, provide:

    # Meeting Insights Summary
    
    **Analysis Period**: [Date range]
    **Meetings Analyzed**: [X meetings]
    **Total Duration**: [X hours]
    
    ## Key Patterns Identified
    
    ### 1. [Primary Pattern]
    - **Observed**: [What you saw]
    - **Impact**: [Why it matters]
    - **Recommendation**: [How to improve]
    
    ### 2. [Second Pattern]
    [Same structure]
    
    ## Communication Strengths
    
    1. [Strength 1 with example]
    2. [Strength 2 with example]
    3. [Strength 3 with example]
    
    ## Growth Opportunities
    
    1. **[Area 1]**: [Specific, actionable advice]
    2. **[Area 2]**: [Specific, actionable advice]
    3. **[Area 3]**: [Specific, actionable advice]
    
    ## Speaking Statistics
    
    - Average speaking time: [X% of meeting]
    - Questions asked: [X per meeting average]
    - Filler words: [X per minute]
    - Interruptions: [X given / Y received per meeting]
    
    ## Next Steps
    
    [3-5 concrete actions to improve communication]
    
  6. Offer Follow-Up Options

    • Track these same metrics in future meetings
    • Deep dive into specific meetings or patterns
    • Compare to industry benchmarks
    • Create a personal communication development plan
    • Generate a summary for performance reviews

Examples

Example 1: Conflict Avoidance Analysis (Inspired by Dan Shipper)

User: "I download all of my meeting recordings and put them in a folder. Tell me all the times I've subtly avoided conflict."

Output:

# Conflict Avoidance Patterns

Found 23 instances across 15 meetings where you used indirect
communication or avoided addressing tensions directly.

## Pattern: Hedging on Critical Feedback

**Frequency**: 8 times across 7 meetings

**Example 1: 1:1 with Sarah** - 00:14:32

**What Happened**:
> "So, I was thinking... maybe we could, like, potentially
> consider looking at the timeline again? I mean, if you
> think that makes sense. But whatever you think is best!"

**Why This Matters**:
You needed to address that Sarah's project was behind schedule,
but the hedging language ("maybe", "potentially", "if you think")
and the deflection at the end ("whatever you think") made it easy
for her to miss the urgency.

**Better Approach**:
"Sarah, the project is two weeks behind schedule. We need to
discuss what's blocking progress and create a new timeline
today."

[Additional examples...]

## Recommendations

1. **Name the issue directly** in the first sentence
2. **Remove hedging words** like "maybe," "kind of," "sort of"
3. **Ask specific questions** instead of hinting
4. **Schedule difficult conversations** instead of raising them casually

Example 2: Leadership Facilitation

User: "Analyze my team meetings and tell me about my facilitation style."

Output: Provides insights on:

  • How much you speak vs. team members (60% vs. 40%)
  • Whether you ask questions or make statements (3:1 ratio)
  • How you handle disagreements (tendency to resolve too quickly)
  • Who speaks least and whether you draw them in
  • Examples of good and missed facilitation moments

Example 3: Personal Development Tracking

User: "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."

Output: Creates a comparative analysis showing:

  • Decrease in interruptions (8 per meeting → 3 per meeting)
  • Increase in clarifying questions (2 → 7 per meeting)
  • Improvement in building on others' ideas
  • Specific examples showing the difference
  • Remaining areas for growth

Setup Tips

Getting Meeting Transcripts

From Granola (free with Lenny's newsletter subscription):

  • Granola auto-transcribes your meetings
  • Export transcripts to a folder: [Instructions on how]
  • Point Claude Code to that folder

From Zoom:

  • Enable cloud recording with transcription
  • Download VTT or SRT files after meetings
  • Store in a dedicated folder

From Google Meet:

  • Use Google Docs auto-transcription
  • Save transcript docs to a folder
  • Download as .txt files or give Claude Code access

From Fireflies.ai, Otter.ai, etc.:

  • Export transcripts in bulk
  • Store in a local folder
  • Run analysis on the folder

Best Practices

  1. Consistent naming: Use YYYY-MM-DD - Meeting Name.txt format
  2. Regular analysis: Review monthly or quarterly for trends
  3. Specific queries: Ask about one behavior at a time for depth
  4. Privacy: Keep sensitive meeting data local
  5. Action-oriented: Focus on one improvement area at a time

Common Analysis Requests

  • "When do I avoid difficult conversations?"
  • "How often do I interrupt others?"
  • "What's my speaking vs. listening ratio?"
  • "Do I ask good questions?"
  • "How do I handle disagreement?"
  • "Am I inclusive of all voices?"
  • "Do I use too many filler words?"
  • "How clear are my action items?"
  • "Do I stay on agenda or get sidetracked?"
  • "How has my communication changed over time?"

Related Use Cases

  • Creating a personal development plan from insights
  • Preparing performance review materials with examples
  • Coaching direct reports on their communication
  • Analyzing customer calls for sales or support patterns
  • Studying negotiation tactics and outcomes

发现问题?提交给管理员复核

评分:

评论 (0)

暂无评论,成为第一个评论者吧!