Token导航 LogoToken导航

Agent Skill · 开发

transcribe-refiner(转录精炼机)

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

transcribe-refiner 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有未通过项,按安装量在开发类的 21,746 个 Skill 里排第 18,691。

总安装 321周安装 13GitHub Stars 公开资料未说明下载 101核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/prakharmnnit/skills-and-personas --skill transcribe-refiner

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

transcribe-refiner 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中整理协作事项。适用于围绕仓库状态、代码变更或团队协作进行信息梳理。

通过 npx skills add 命令从 GitHub 仓库安装使用。安装前需确认权限范围、维护状态及是否触发联网或文件操作。建议结合原始 README 文档进一步验证具体用法和功能边界。

来源仓库内路径:skills/transcribe-refiner

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/prakharmnnit/skills-and-personas --skill trans…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

transcribe-refiner 怎么安装?

在终端执行 npx skills add https://github.com/prakharmnnit/skills-and-personas --skill transcribe-refi…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

transcribe-refiner 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

transcribe-refiner 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

transcribe-refiner 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

transcribe-refiner 用的人多吗?

公开数据是累计安装 321 次,近一周安装 13 次,下载 101 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

transcribe-refiner 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
transcribe-refiner

转录精炼机 · 本页

321—需要联网未明确未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Transcribe Refiner - Caption Cleanup Engine

Transform raw auto-generated captions into clean, readable transcripts with zero content loss.

Core Purpose

Auto-generated captions (Zoom, YouTube, Teams, etc.) are messy: fragmented sentences, timestamps everywhere, speaker tags on every line, filler words, transcription errors. This skill reconstructs them into coherent, flowing text that can be consumed by humans or downstream skills (like lecture-alchemist).

Critical Rules

Zero Content Loss

Every substantive statement, technical term, concept, question, and answer from the raw captions MUST appear in the output. Only noise is removed, never content.

Remove: Timestamps, redundant speaker tags, filler words (um, uh, basically, right?, you know), technical interruptions ("can you hear me?", "let me share my screen"), duplicate sentences from reconnection.

Preserve: Every teaching point, code reference, question asked, answer given, tangent with value, name, URL, command, or technical term.

Smart Error Correction

Auto-captions make predictable errors. Fix them using domain context:

Common ErrorLikely CorrectDomain Clue
"lowest function""loss function"AI/ML context
"wait""weight"neural network context
"epic""epoch"training context
"by Torch""PyTorch"ML framework
"relaunch bowl""relaunch poll"Zoom context
"solidity" vs "Solidity"capitalize if Web3Web3 context
"know JS""Node.js"WebDev context
"react" vs "React"capitalize if frameworkWebDev context

When uncertain about a correction, keep the original and flag it: [unclear: "original text"]

Speaker Handling

  • Identify unique speakers from tags
  • Normalize names (e.g., [rishabh] → **Rishabh:**)
  • Only include speaker attribution at natural conversation changes
  • For single-speaker lectures, omit speaker tags entirely after initial identification
  • For Q&A, clearly mark: **Student:** and **Instructor:**

Input Formats

FormatCharacteristicsHandling
Zoom captions (.txt)[speaker] HH:MM:SS\ntextStrip timestamps, merge fragments
YouTube (.vtt/.srt)Numbered blocks with timecodesStrip timecodes and sequence numbers
Otter.aiSpeaker-labeled paragraphsNormalize speaker labels
TeamsTimestamped speaker blocksStrip timestamps, merge
Raw pasteMixed formatAuto-detect and clean

Processing Steps

  1. Strip noise - Remove timestamps, sequence numbers, formatting artifacts
  2. Merge fragments - Join broken sentences across caption blocks
  3. Remove filler - Strip "um", "uh", "basically", "right?", "you know" (but keep if they carry meaning like "right?" as a genuine question)
  4. Fix transcription errors - Use domain context to correct obvious misrecognitions
  5. Remove technical interruptions - "Can you hear me?", "Let me share my screen", "Is my screen visible?", connection issues
  6. Form paragraphs - Group related sentences into natural paragraphs by topic
  7. Identify sections - Insert --- breaks at major topic transitions
  8. Normalize Q&A - Clearly separate questions from instruction
  9. Add metadata header - Speaker(s), estimated duration, domain detected

Output Format

# Transcript: [Topic/Title if identifiable]

**Speaker(s):** [Name(s)]
**Estimated Duration:** [from timestamp range]
**Domain:** [Auto-detected: WebDev / AI-ML / Web3 / DSA / General]
**Cleaning Notes:** [e.g., "Fixed 12 transcription errors, removed ~45 filler instances"]

---

[Clean, flowing paragraphs organized by topic]

[Natural paragraph breaks at topic changes]

---

[Next topic section]

---

## Q&A Segments

**Student:** [Question]

**Instructor:** [Answer]

Topic Inventory (Anti-Loss System)

This is the critical mechanism that prevents data loss across the pipeline. After cleaning, generate a Topic Inventory at the end of output -- a manifest of every substantive item found in the transcript.

## Topic Inventory

### Concepts Mentioned
1. [Concept] - paragraph [N]
2. [Concept] - paragraph [N]
...

### Technical Terms Introduced
- [term]: first mentioned in paragraph [N]
...

### Code/Commands Referenced
- [code snippet or command] - paragraph [N]
...

### Questions Asked (Q&A)
- Q: [question summary] - paragraph [N]
...

### Names/Resources Mentioned
- [name, URL, tool, book, etc.]
...

### Corrections Applied
| Original Caption | Corrected To | Confidence |
|-----------------|-------------|------------|
| "lowest function" | "loss function" | High |
| "epic" | "epoch" | High |
| [unclear text] | [kept as-is] | Low |

### Stats
- Raw caption blocks: [N]
- Substantive paragraphs produced: [N]
- Filler instances removed: [N]
- Transcription errors corrected: [N]
- Uncertain corrections flagged: [N]

This inventory travels to the next stage (lecture-alchemist) for cross-verification. Every item in this inventory MUST appear in the final notes.

Timestamp Anchors

Preserve approximate timestamps as hidden anchors for key topic transitions. Format:

<!-- T:20:36:30 --> Neural network architecture introduction
<!-- T:20:45:12 --> Activation functions
<!-- T:21:03:45 --> Training loop

These allow the reader to jump back to the recording at specific points.

Quality Checklist

Before output, verify:

  • Every teaching point from raw input is in the output
  • Topic Inventory is complete and accurate
  • Transcription errors corrected using domain context
  • Uncertain corrections flagged with [unclear:...]
  • Filler words removed without losing meaning
  • Sentences properly merged (no mid-word breaks)
  • Q&A segments clearly separated
  • Technical interruptions removed
  • Timestamp anchors placed at topic transitions
  • Output reads as natural, flowing text

Pipeline Position

This skill is Stage 1 in the lecture processing pipeline:

  1. transcribe-refiner (this) → clean transcript + Topic Inventory
  2. lecture-alchemist → structured study notes (verifies against inventory)
  3. concept-cartographer → visual diagrams (verifies against inventory)
  4. obsidian-markdown → Obsidian vault formatting

Downstream Packaging Contract

  1. Keep source-rich traceability in pipeline artifacts (segment_ledger, coverage_matrix, enhanced_notes).
  2. Learner-facing final tutorial note should be sanitized for readability (no inline [source:...] tags).
  3. Final published naming should follow:

- <Domain> Class <NN> [DD/MM/YYYY] - <Topic> (title/H1) - <DomainFile> Class <NN> [DD-MM-YYYY] - <Topic>.md (published filename)

平台分布

Codex

34.27%
按下载量换算35

Claude

34.17%
按下载量换算35

Cursor

19%
按下载量换算19

Gemini CLI

9.91%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills