Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计通过

transcript-polisher成绩单抛光机

Agent Skill

transcript-polisher 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

336

周安装

14

GitHub Stars

9

下载量

112
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:transcript-polisher(成绩单抛光机)
来源仓库:https://github.com/cdeistopened/skill-stack
仓库路径:skills/transcript-polisher
安装命令:
npx skills add https://github.com/cdeistopened/skill-stack --skill transcript-polisher
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/cdeistopened/skill-stack --skill transcript-polisher

简介

将原始转录本转化为可读性强的专业文档,保留原意同时优化表达。

  • 适用于访谈、播客和会议记录的后期编辑与排版场景。
  • 使用时平衡真实性与清晰度,去除冗余但保留核心信息。
  • 通过 GitHub 安装,支持主流宿主环境,建议核对发言人授权。
  • transcript-polisher 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Transcript Polisher

Transform raw podcast or interview transcripts into polished, professional documents that maintain authentic voice while dramatically improving readability.

Purpose

Raw transcripts from automated services are often unreadable - filled with filler words, incomplete sentences, and poor formatting. This skill cleans them up while preserving what was actually said.

Core Philosophy: Balance authenticity with clarity. Remove everything that doesn't add meaning while preserving what was actually said. Create the "ideal version" of what the speaker wanted to communicate - without changing their words or ideas.

Target: 25-35% length reduction while maintaining 100% fidelity to meaning.

When to Use This Skill

  • Processing raw transcripts from Rev, Otter, Descript, YouTube auto-captions
  • Cleaning up interview recordings or video transcripts
  • Preparing spoken content for publication as articles or show notes
  • Converting conversational content into readable written format

Not for: Written content that wasn't originally spoken, pre-polished articles, or scripts that are already edited.


Workflow

Step 1: Add Document Structure

Create proper header with:

# [Guest Name]: [Compelling Episode Title]

*[Podcast Name] Episode - [Host Names]*

---

## Timestamped Outline
[Add 10 chapters maximum - see guidelines below]

---

## [Time] Chapter Title
[Content starts here]

Timestamped Outline Rules:

  • Format: **MM:SS** - Descriptive Chapter Title
  • 10 chapters maximum for 45-60 minute episodes
  • Focus on major topic changes, not minute-by-minute
  • Use compelling, specific titles (not generic descriptions)

Good Examples:

  • 12:25 - The Turnaround: From Struggling to Thriving
  • 29:08 - Why Successful Strategies Don't Spread

Poor Examples:

  • 12:25 - Guest talks about their experience
  • 29:08 - Discussion about the industry

Step 2: Identify and Label Speakers

Replace generic speaker markers (>>, Speaker 1, etc.) with actual names:

  • Bold all speaker names: **Isaac:** Content here
  • Use first names for casual podcasts, full names for professional interviews
  • Be consistent throughout

Step 3: Aggressive Editing Pass

Apply aggressive polishing while maintaining 100% fidelity.

Remove ALL filler words:

  • "um," "uh," "ah," "er," "hmm"
  • "you know," "I mean," "like" (when used as filler)
  • "so," "well," "basically," "literally" (when empty)
  • "kind of," "sort of" (when hedging unnecessarily)

Consolidate restarts:

  • ❌ "I think that... well, what I think is... the main thing is..."
  • ✅ "The main thing is..."

Pick the clearest version when speakers repeat:

  • If they say the same thing 3 ways, keep only the best one
  • Combine fragments into complete thoughts

Fix awkward grammar:

  • Complete sentence fragments
  • Fix subject-verb agreement
  • Repair run-on sentences

Keep only the strongest examples:

  • If speaker gives 5+ examples, keep 1-2 best ones
  • Remove redundant illustrations of the same point

Add clarity to vague pronouns:

  • Use minimal bracketed additions: "they [the teachers] decided..."
  • Only when meaning would be unclear otherwise

Step 4: Preserve What Matters

Never edit:

  • Unique voice and natural rhythm
  • Exact wording of powerful statements
  • Emotional moments and authenticity
  • Specialized terminology
  • Cultural references that reveal personality
  • Natural dialogue patterns
  • Humor and personality
  • Memorable phrases

The 100% Fidelity Rule:

  • ❌ Never paraphrase or change meaning
  • ❌ Never add ideas not present in original
  • ❌ Never remove key insights or stories
  • ✅ Only remove redundancy and inefficiency
  • ✅ Preserve exact wording of powerful statements
  • ✅ Keep all substantive content

Step 5: Quality Check

Before finishing:

  • Length reduced by 25-35%
  • All filler words removed
  • Speakers properly identified and bolded
  • Chapter breaks added with compelling titles
  • Grammar fixed but voice preserved
  • Key insights and stories intact
  • No meaning changed or paraphrased
  • Reads naturally when spoken aloud

Editing Guidelines

What TO Edit (Aggressively)

1. Filler Words Remove ALL instances unless part of signature style:

  • um, uh, ah, er, hmm
  • you know, I mean, like
  • so, well, basically, literally, actually
  • kind of, sort of, I think, probably, maybe

2. False Starts and Restarts

Before: "I think that... well, what I was trying to say is... the main thing is that we need to focus"
After: "The main thing is that we need to focus"

3. Redundant Explanations When the same point is made multiple ways, keep only the clearest version.

4. Verbal Hedging (when excessive)

Before: "I think it's probably maybe kind of important to sort of consider..."
After: "It's important to consider..."

5. Conversational Detours Remove tangents that don't serve the narrative or provide insight.

6. Grammar Issues

  • Incomplete sentences → complete
  • Subject-verb disagreement → fix
  • Run-on sentences → break up

7. Excessive Examples If 5+ examples are given for one point, keep 1-2 strongest.

8. Vague Pronouns (minimal intervention) Only add bracketed clarity when meaning is genuinely unclear:

"They [the board members] decided to..."

What NOT to Edit

1. Unique Voice and Natural Rhythm Keep the speaker's distinctive patterns, even if informal.

2. Powerful Statements Preserve exact wording of quotable moments.

3. Emotional Moments Don't sanitize authentic expressions:

  • ✅ Keep: "That bugged the crap out of me"
  • ❌ Don't change to: "That bothered me significantly"

4. Specialized Terminology Keep industry/domain-specific language even if uncommon.

5. Cultural References Preserve references that reveal personality and context.

6. Natural Dialogue Patterns Keep the back-and-forth feel of conversation.


Common Transcription Errors to Fix

Auto-Caption Issues

  • OCR errors (e.g., "quad code" → "Claude Code")
  • Homophone mistakes ("their" vs "there")
  • Missing punctuation
  • Run-on sentences
  • Mis-identified technical terms

Audio Transcription Issues

  • Speaker confusion
  • Overlapping dialogue
  • Background noise artifacts
  • Timestamp errors

Output Format

Final polished transcript should be:

  • Markdown formatted
  • Properly sectioned with timestamps
  • Speaker names bold and consistent
  • 25-35% shorter than original
  • Grammar perfect but voice authentic
  • Ready for publication or repurposing

Before/After Examples

Example 1: Filler Removal

Before:

"So, um, I think that, you know, what we really need to focus on is, like, the fact that, you know, students are, um, actually learning better when, you know, they have more autonomy."

After:

"Students learn better when they have more autonomy."

(15 words → 8 words = 47% reduction)

Example 2: Consolidating Restarts

Before:

"The thing about... what I'm trying to say is... the main point here is that we need to rethink how we approach this. We need to rethink our approach. What I mean is, the whole system needs to be reconsidered."

After:

"The whole system needs to be reconsidered."

(Kept only the clearest expression of the idea)

Example 3: Voice Preservation

Before:

"Look, this bugged the crap out of me for years. Nobody wanted to talk about it. Like, everyone knew, but nobody would say anything."

After:

"Look, this bugged the crap out of me for years. Nobody wanted to talk about it. Everyone knew, but nobody would say anything."

(Only removed the filler "like" - preserved the authentic voice and expression)


Bundled Resources

  • references/editing-guidelines.md - Detailed editing rules with examples
  • references/structure-template.md - Header format and chapter guidelines

Related Skills

  • anti-ai-writing - Further humanize and polish the output
  • social-content-creation - Repurpose transcript insights to social posts
  • hook-and-headline-writing - Create compelling chapter titles

*Remember: 100% fidelity to meaning, 25-35% reduction in length. Remove what doesn't add meaning. Preserve what makes it authentic.*

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.81%
按下载量换算40

Claude

29.4%
按下载量换算33

Cursor

18.18%
按下载量换算20

Gemini CLI

10.22%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills