复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
This is the open-source content repository behind
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
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.
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/, …).
Submit through the platform — not through a pull request:
SKILL.md.SKILL.md — the skill definition (required, per the Agent Skills spec)LICENSE (recommended)Every submission is scanned automatically before it can be published. The audit flags things like:
eval, exec, raw system commands)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:
.
├── 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.
The marketplace catalog is MIT-licensed. Individual skills carry their own licenses — check each skill's LICENSE file.
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: skillThis skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.
Pattern Recognition: Identifies recurring behaviors across meetings like:
Communication Analysis: Evaluates communication effectiveness:
Actionable Feedback: Provides specific, timestamped examples with:
Trend Tracking: Compares patterns over time when analyzing multiple meetings
~/meetings/)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.
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
When a user requests meeting analysis:
Discover Available Data
Clarify Analysis Goals
If not specified, ask what they want to learn:
Analyze Patterns
For each requested insight:
Conflict Avoidance:
Speaking Ratios:
Filler Words:
Active Listening:
Leadership & Facilitation:
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]
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]
Offer Follow-Up Options
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
User: "Analyze my team meetings and tell me about my facilitation style."
Output: Provides insights on:
User: "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."
Output: Creates a comparative analysis showing:
From Granola (free with Lenny's newsletter subscription):
From Zoom:
From Google Meet:
From Fireflies.ai, Otter.ai, etc.:
YYYY-MM-DD - Meeting Name.txt format
评论 (0)
暂无评论,成为第一个评论者吧!