glebis/transcript-analyzer
transcript-analyzer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add glebis/claude-skills transcript-analyzerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:07 PM170.1s11 files scanned
SKILL.md
- 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:
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 pointscripts/src/lib/extract-service.ts- AI processing logic using Cerebrasscripts/src/lib/markdown.ts- Markdown output generationscripts/src/lib/term-utils.ts- Term deduplication utilitiesscripts/src/lib/mockExtractor.ts- Mock mode for testingscripts/src/types/index.ts- TypeScript type definitionsscripts/data/glossary.json- Default glossary storage
Related Skills
glebis/release
documentation
VerifiedTrustedCommunity
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
242SKILL.mdUpdated Jun 4, 2026
glebis/library-sync
development
VerifiedTrustedCommunity
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
242SKILL.mdUpdated Jun 4, 2026
glebis/job-babysitter
development
VerifiedTrustedCommunity
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.
242SKILL.mdUpdated Jun 4, 2026
glebis/peer-agent-collaboration
development
VerifiedTrustedCommunity
Use when the user wants Claude Code, Codex, or other AI coding/business agents to work together as peers. This skill should be used whenever the user mentions coordinating Claude Code and Codex, agent handoffs, multi-agent workflows, parity, respect, pushback between agents, deciding which agent should lead, or turning a business/code workflow into a two-agent operating model.
242SKILL.mdUpdated Jun 4, 2026