mcpbeat

Transcript Analyzer

glebis/transcript-analyzer

This skill analyzes meeting transcripts to extract decisions, action items, opinions, questions, and terminology using Cerebras AI (llama-3.3-70b). Use this skill when the user asks to analyze a transcript, extract action items from meetings, find decisions in conversations, build glossaries from discussions, or summarize key points from recorded meetings.

79k tokens
context cost
the whole folder, loaded on every use
13
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
337
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/glebis/claude-skills --skill transcript-analyzer

What comes with it

313 431 bytes besides the instruction
.claude-plugin/plugin.json
scripts/cli.ts
scripts/data/glossary.json
scripts/package-lock.json
scripts/package.json
scripts/src/lib/extract-service.ts
scripts/src/lib/markdown.ts
scripts/src/lib/mockExtractor.ts
scripts/src/lib/term-utils.ts
scripts/src/lib/utils.ts
scripts/src/types/index.ts
scripts/tsconfig.json

The instruction itself

13 sections, as written by the author

Transcript Analyzer

Overview

Analyze meeting transcripts using AI to automatically extract and categorize:

  • Decisions - Explicit agreements or choices made
  • Action Items - Tasks assigned to people
  • Opinions - Viewpoints expressed but not agreed upon
  • Questions - Unresolved questions raised
  • Terms - Domain-specific terminology for glossary

Prerequisites

Before first use, install dependencies:

cd ~/.claude/skills/transcript-analyzer/scripts && npm install

Usage

To analyze a transcript:

cd ~/.claude/skills/transcript-analyzer/scripts && npm run cli -- <transcript-file> -o <output.md> [options]

Options

| Option | Description |

|--------|-------------|

| <file> | Transcript file to analyze (first positional arg) |

| -o, --output <path> | Write markdown to file instead of stdout |

| --include-transcript | Include full transcript in output [default: off] |

| --no-extractions | Exclude extractions section |

| --no-glossary | Exclude glossary section |

| --glossary <path> | Custom glossary JSON path |

| --skip-glossary | Don't preload glossary terms |

| --max-terms <num> | Limit glossary suggestions |

| --chunk-size <num> | Override chunk size (default: 3000) |

Examples

Basic Analysis

cd ~/.claude/skills/transcript-analyzer/scripts && npm run cli -- /path/to/meeting.md -o /path/to/analysis.md

Include Original Transcript

cd ~/.claude/skills/transcript-analyzer/scripts && npm run cli -- /path/to/meeting.md -o /path/to/analysis.md --include-transcript

Extractions Only (No Glossary)

cd ~/.claude/skills/transcript-analyzer/scripts && npm run cli -- /path/to/meeting.md -o /path/to/analysis.md --no-glossary

Analyze Specific Section

To analyze only part of a transcript, extract the section first:

sed -n '50,100p' /path/to/meeting.md > /tmp/section.md
cd ~/.claude/skills/transcript-analyzer/scripts && npm run cli -- /tmp/section.md -o /path/to/section-analysis.md

Output Format

The tool generates markdown with:

  • YAML Frontmatter - Processing metadata:
  • chunks processed
  • extractions count by type
  • new terms discovered
  • model used (llama-3.3-70b via Cerebras)
  • token usage (input/output/total)
  • Extractions - Categorized findings with confidence scores:
  • Each extraction includes speaker (if identified), source snippet, and related terms
  • Glossary - Approved terms from existing glossary + suggested new terms with definitions

Configuration

The skill uses Cerebras API with the key stored in scripts/.env:

CEREBRAS_API_KEY=<your-key>

Scripts

  • scripts/cli.ts - Main CLI entry point
  • scripts/src/lib/extract-service.ts - AI processing logic using Cerebras
  • scripts/src/lib/markdown.ts - Markdown output generation
  • scripts/src/lib/term-utils.ts - Term deduplication utilities
  • scripts/src/lib/mockExtractor.ts - Mock mode for testing
  • scripts/src/types/index.ts - TypeScript type definitions
  • scripts/data/glossary.json - Default glossary storage

How to use it

Copy the folder

Take glebis/transcript-analyzer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.