Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Transcription Pro

ASecurity

Master transcription — speech-to-text workflows, accuracy optimization, speaker diarization, and transcript management.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgodocumentation

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill transcription-pro --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Transcription Pro?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Transcription Pro
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-transcription-pro/badge)](https://www.skillsdirectory.com/skills/aicodedecode-transcription-pro)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: transcription-pro
description: Master transcription — speech-to-text workflows, accuracy optimization, speaker diarization, and transcript management.
category: enterprise-communication
---

## Overview

Transcription converts speech to text for meetings, interviews, podcasts, legal proceedings, and accessibility. This skill covers professional transcription practice: choosing approaches (AI vs. human), maximizing accuracy, speaker identification, editing workflows, and managing transcript libraries.


Professional transcription converts audio and video to accurate text: for accessibility, searchability, records, and content repurposing.
Beyond raw conversion, mastery covers accuracy optimization, speaker identification, timestamping, and the workflows that make transcripts genuinely useful.
## When to use

- Transcribing meetings, interviews, or calls
- Choosing between AI and human transcription
- Improving transcript accuracy
- Setting up speaker diarization
- Creating accessible content (captions)
- Building searchable audio archives

- Making video content accessible and searchable
- Creating meeting records and archives
- Repurposing webinars and interviews into written content
- Meeting legal or compliance documentation needs
- Transcribing legal proceedings
## Core concepts

**AI vs. human.** AI transcription: fast, cheap, 90–95% accurate on clear audio — best for searchable archives, rough drafts, and high volume. Human: 99%+ accurate, handles accents/crosstalk/jargon — best for legal, publishing, and critical records. Hybrid (AI draft + human edit) balances cost and quality.

**Accuracy drivers.** Audio quality dominates: close mics, quiet rooms, minimal crosstalk. Then: domain vocabulary (custom vocabularies for jargon/names), speaker separation (fewer overlapping voices), and audio format (uncompressed or high-bitrate). Garbage audio in, garbage transcript out — no model fixes a bad recording.

**Speaker diarization.** "Who spoke when" — essential for multi-person transcripts. Accuracy depends on distinct voices and minimal overlap. Label speakers with real names post-transcription for readability; verify attributions on critical quotes.

**Timestamps.** Word- or sentence-level timestamps enable: click-to-play audio sync, clip extraction, and precise quoting. Essential for legal, research, and content repurposing.

**Editing workflows.** Light edit (fix names, key terms — for internal use), full edit (readability: remove fillers, fix grammar lightly — for publishing), verbatim (every um and false start — for legal/research). Match edit level to purpose; over-editing wastes money.

**Use cases.** Accessibility (captions are often legally required), searchability (find moments in hours of audio), records (decisions, agreements), content repurposing (podcast → blog), and analysis (interview coding, call analytics).


**Accuracy factors.** Audio quality (close mics beat room mics), speaker separation, domain vocabulary (custom dictionaries for jargon), accents and languages, and background noise.
Garbage audio produces garbage transcripts — invest at the source.
Human review for critical content; AI-only for drafts and search.
**Speaker diarization.** Identifying who spoke when — essential for multi-person content.
Enroll voice profiles where possible; label unknown speakers consistently.
Diarization errors compound in long recordings — spot-check.
**Timestamps and formatting.** Word-level timestamps enable search and captioning; paragraph breaks by speaker; filler word handling policies.
Format for the use case: verbatim for legal, cleaned for readability.
Define standards upfront; reformatting later wastes effort.
## Practical workflow

1. **Define requirements.** Purpose (archive? publish? legal?), accuracy needed, turnaround time, speaker count, and budget. These determine AI vs. human vs. hybrid.
2. **Capture good audio.** Separate mics when possible, record locally as backup (not just cloud), test levels beforehand, minimize background noise. This step matters more than model choice.
3. **Transcribe.** Run AI transcription with custom vocabulary (names, jargon, product terms). For critical content, send to human transcription or human-edit the AI draft.
4. **Edit to purpose.** Apply the right edit level. Verify: speaker labels, proper nouns, numbers/dates, and key quotes. Spot-check timestamps on important sections.
5. **Deliver and store.** Format for use (clean transcript, captions file, searchable archive), store audio + transcript together, tag with metadata (date, participants, topic), and set retention per policy.
6. **Leverage.** Search across transcripts, extract clips/quotes, feed into summaries, and analyze patterns (for research or QA).

**Pre-recording checklist:** mics tested → quiet environment → backup recording running → participant names collected (for labels) → custom vocabulary prepared → consent obtained.


**Production workflow:** capture quality audio → transcribe (AI first pass) → human review (critical content) → format per standard → QA spot-check → publish with metadata.
Match effort to purpose — internal search needs less polish than published captions.
**Captioning for video:** accuracy 99%+ for broadcast → speaker labels → sound descriptions [applause] → reading speed (160–180 wpm max) → positioning.
Captions are accessibility infrastructure — treat them as such, not as afterthoughts.
## Common pitfalls

- **Bad audio.** Expecting AI to transcribe a echoey conference room with 8 people on one mic. Fix capture first.
- **Wrong accuracy tier.** Using raw AI output for published/legal content. Match method to stakes.
- **Ignoring speaker labels.** "Speaker 1, Speaker 2" in a 10-person meeting. Label and verify.
- **No custom vocabulary.** Product names and jargon consistently wrong. Provide vocabularies upfront.
- **Over-editing.** Paying for full cleanup of internal archive transcripts. Match edit level to purpose.
- **No timestamps.** Transcripts without time alignment can't link back to audio. Include timestamps by default.
- **Privacy neglect.** Transcripts contain everything said. Access controls, retention policies, and redaction for sensitive content.
- **No audio standards.** Accepting terrible source audio. Publish recording guidelines; reject unusable submissions early.
- **Ignoring turnaround needs.** Real-time captioning vs. post-production have different tools and costs. Match method to deadline honestly.
- **Privacy violations.** Transcribing sensitive conversations without consent. Clear policies on what gets transcribed, stored, and shared.
- **No quality sampling.** Assuming 100% accuracy. Sample and score regularly — accuracy drifts with audio conditions.
- **Ignoring speaker overlap.** Crosstalk producing garbled output. Flag overlapping speech; do not guess attributions.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →