Agent skill

Transcript Analyzer

This skill analyzes meeting transcripts to extract decisions, action items, opinions, questions, and terminology using Cerebras AI (llama-3.3-70b).

MITAuto-check: notes

Install Transcript Analyzer

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/transcript-analyzer .claude/skills/transcript-analyzer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .claude/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/glebis/claude-skills/tree/main/transcript-analyzer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/transcript-analyzer .agents/skills/transcript-analyzer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .agents/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/transcript-analyzer .cursor/skills/transcript-analyzer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .cursor/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/glebis/claude-skills.git --path transcript-analyzer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/transcript-analyzer .gemini/skills/transcript-analyzer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .gemini/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/transcript-analyzer .github/skills/transcript-analyzer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .github/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add glebis/claude-skills --skill transcript-analyzer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install glebis/claude-skills transcript-analyzer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/transcript-analyzer .opencode/skills/transcript-analyzer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "transcript-analyzer" agent skill from https://github.com/glebis/claude-skills/tree/main/transcript-analyzer into .opencode/skills/transcript-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "transcript-analyzer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: transcript-analyzer
GitHub stars: 388
Token cost: ~883 tokens
SKILL.md length: 240 words
Files: 13 (incl. scripts)
Skills in repo: 91
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

This skill analyzes meeting transcripts to extract decisions, action items, opinions, questions, and terminology using Cerebras AI (llama-3.3-70b).

Works in 3 steps: YAML Frontmatter - Processing metadata → Extractions - Categorized findings with… → Glossary - Approved terms from existing…
The user asks to analyze a transcript
SKILL.md covers Overview, Prerequisites, Usage and Examples, plus 3 more sections
Runs TypeScript scripts from its folder; calls npm; needs CEREBRAS_API_KEY

What it does

Transcript Analyzer is an agent skill from glebis/claude-skills. 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.

Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including scripts (for example `.claude-plugin/plugin.json`, `scripts/cli.ts` and `scripts/data/glossary.json`).

The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.

When your agent uses it

The user asks to analyze a transcript
Extract action items from meetings
Find decisions in conversations
Build glossaries from discussions

Example prompts

“/transcript-analyzer”

Requirements

Node.js
A credential in CEREBRAS_API_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

YAML Frontmatter - Processing metadata
Extractions - Categorized findings with confidence scores
Glossary - Approved terms from existing glossary + suggested new terms with definitions

What it can do on your machine

Read from SKILL.md and the folder at commit 7524dff. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 11 files in scripts/ (TypeScript), which the agent can run.
Shell commands in SKILL.md call:
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- CEREBRAS_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Transcript Analyzer loads about 883 tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 240 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~95
When it runs · the whole SKILL.md, loaded when a task matches: ~883

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:94

bras API with the key stored in `scripts/.env`:

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from glebis/claude-skills at commit 7524dff, republished under its MIT licence (© glebis). 240 words, ~883 tokens.

Download SKILL.mdSave it as .claude/skills/transcript-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.

name: transcript-analyzer
description: 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.

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:

bash

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

Usage

To analyze a transcript:

bash

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

bash

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

Include Original Transcript

bash

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

Extractions Only (No Glossary)

bash

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:

bash

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

Files

SKILL.md and 12 other files (scripts) in transcript-analyzer of glebis/claude-skills.

SKILL.md
.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

Open the folder on GitHubat commit 7524dff

Compare with similar skills

Transcript Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Transcript Analyzer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Transcript Analyzer this skillglebis/claude-skills	388	—	~883	Automated safety check: Notes	MIT	11 days ago
Meeting Action ItemsNousResearch/hermes-agent	252k	—	~950	Automated safety check: Pass	MIT	today
Meeting Notes And Actionscomposio-community/awesome-codex-skills	17k	—	~357	Automated safety check: Pass	None	2 mo ago
Meeting Analyzeralirezarezvani/claude-skills	28k	1 repos	~3k	Automated safety check: Pass	MIT	1 mo ago
Document To Action ItemsNousResearch/hermes-agent	252k	—	~976	Automated safety check: Pass	MIT	today
Analyze GitHub Action Logswithastro/astro	63k	1 repos	~1.3k	Automated safety check: Pass	Custom licence	today

Similar skills

Meeting Action Items
NousResearch/hermes-agent
Turn meeting notes into cited decisions, owners, tickets. An agent skill from NousResearch/hermes-agent.
252k GitHub stars~950 tokensUpdated today
Productivity & AutomationAuto-check passed
Meeting Notes And Actions
composio-community/awesome-codex-skills
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate…
17k GitHub stars~357 tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Meeting Analyzer
alirezarezvani/claude-skills
Analyzes meeting transcripts and recordings to surface behavioral patterns, communication anti-patterns, and actionable coaching feedback.
28k GitHub starsUsed in 1 repo~3k tokens
Documents & OfficeAuto-check passed
Document To Action Items
NousResearch/hermes-agent
Extract cited obligations, deadlines, tasks from documents. An agent skill from NousResearch/hermes-agent.
252k GitHub stars~976 tokensUpdated today
Documents & OfficeAuto-check passed
Analyze GitHub Action Logs
withastro/astro
Official
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
63k GitHub starsUsed in 1 repo~1.3k tokens
DevOps & CloudAuto-check passed
Action Items List Manager
asgeirtj/system_prompts_leaks
Maintains a private to-do list stored as a JSON file in the assistant's notes: adding tasks, recording what is awaited, tracking blockers and closing finished items.
69k GitHub stars~4.9k tokensUpdated yesterday
Productivity & AutomationAuto-check passed

More from glebis/claude-skills

All 91 skills in this repo

PII Annotation and Agreement Scorer
glebis/claude-skills
Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.
388 GitHub stars~1.3k tokensUpdated 11 days ago
Auto-check passed
Non-Destructive Chrome Automation
glebis/claude-skills
Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.
388 GitHub stars~973 tokensUpdated 11 days ago
Auto-check passed
Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
388 GitHub stars~2.6k tokensUpdated 11 days ago
Auto-check: notes
Elimination Research
glebis/claude-skills
This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…
388 GitHub stars~1.6k tokensUpdated 11 days ago
Auto-check passed
Narrated HTML Presentations
glebis/claude-skills
Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.
388 GitHub stars~2.3k tokensUpdated 11 days ago
Auto-check: notes
Synthetic Coaching Session Generator
glebis/claude-skills
Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.
388 GitHub stars~2.9k tokensUpdated 11 days ago
Auto-check passed

Questions about Transcript Analyzer

What does Transcript Analyzer do?

This skill analyzes meeting transcripts to extract decisions, action items, opinions, questions, and terminology using Cerebras AI (llama-3.3-70b). Transcript Analyzer is an agent skill from glebis/claude-skills.3-70b).

When should I use Transcript Analyzer?

Transcript Analyzer fits situations like: the user asks to analyze a transcript; extract action items from meetings; find decisions in conversations; build glossaries from discussions.

How do I install Transcript Analyzer in Claude Code?

Run `npx skills add glebis/claude-skills --skill transcript-analyzer -a claude-code`. Or copy the skill folder (transcript-analyzer in glebis/claude-skills) into .claude/skills/transcript-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Transcript Analyzer in Codex?

Run `npx skills add glebis/claude-skills --skill transcript-analyzer -a codex`. Or copy the skill folder (transcript-analyzer in glebis/claude-skills) into .agents/skills/transcript-analyzer in your project. Codex loads it when a task matches its description.

Can I use Transcript Analyzer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glebis/claude-skills --skill transcript-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/transcript-analyzer, .gemini/skills/transcript-analyzer, .github/skills/transcript-analyzer and .opencode/skills/transcript-analyzer in your project.

What does Transcript Analyzer need to run?

Going by SKILL.md and its folder, Transcript Analyzer needs TypeScript for the scripts in its folder, the command-line tools its instructions call (npm) and credentials named CEREBRAS_API_KEY. Our summary lists: Node.js; A credential in CEREBRAS_API_KEY.

Does Transcript Analyzer access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Transcript Analyzer safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Transcript Analyzer use?

Transcript Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Transcript Analyzer use?

About 883 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Transcript Analyzer?

Skills that share tags, products or a category with Transcript Analyzer: Meeting Action Items (NousResearch/hermes-agent, 252k stars), Meeting Notes And Actions (composio-community/awesome-codex-skills, 17k stars), Meeting Analyzer (alirezarezvani/claude-skills, 28k stars) and Document To Action Items (NousResearch/hermes-agent, 252k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Transcript Analyzer?

glebis (a GitHub user) maintains it in glebis/claude-skills, which has 388 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 26, 2026.

Source: glebis/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Transcript Analyzer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Transcript Analyzer

Overview

Prerequisites

Usage

Options

Examples

Basic Analysis

Include Original Transcript

Extractions Only (No Glossary)

Analyze Specific Section

Output Format

Configuration

Scripts

Files

Compare with similar skills

Similar skills

More from glebis/claude-skills

Questions about Transcript Analyzer