본문으로 건너뛰기
cccskills
무료GitHub에 공개

youtube-transcribe-skill

Extract subtitles/transcripts from YouTube videos. Triggers: "youtube transcript", "extract subtitles", "video captions", "视频字幕", "字幕提取", "YouTube转文字", "提取字幕".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구YouTube
설치 방법 보기

포함된 파일(1)

  • SKILL.md4.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

YouTube Transcript Extraction

Extract subtitles/transcripts from a YouTube video URL and save them as a local file.

Input YouTube URL: $ARGUMENTS

Step 1: Verify URL

Confirm the input is a valid YouTube URL (supports youtube.com/watch?v=, youtu.be/, and youtube.com/shorts/ formats). If no URL is provided via arguments, check the conversation context for a YouTube link.

Step 2: CLI Quick Extraction (Priority Attempt)

Use command-line tools to quickly extract subtitles.

2.1 Check Tool Availability

Execute which yt-dlp.

  • If yt-dlp is found, proceed to 2.2.
  • If yt-dlp is not found, skip to Step 3.

2.2 Get Video Title

yt-dlp --cookies-from-browser=chrome --get-title "[VIDEO_URL]"
  • Tip: Always add --cookies-from-browser to avoid sign-in restrictions. Default to chrome.
  • If it fails with a browser error (e.g., "Could not open Chrome"), ask the user to specify their available browser (e.g., firefox, safari, edge) and retry.

2.3 Download Subtitles

yt-dlp --cookies-from-browser=chrome --write-auto-sub --write-sub --sub-lang zh-Hans,zh-Hant,en --skip-download --output "<Video Title>.%(ext)s" "[VIDEO_URL]"

2.4 Convert to Plain Text

yt-dlp saves subtitles as .vtt or .srt files. Convert the downloaded file to plain Timestamp Text format:

  1. Read the downloaded subtitle file (.vtt or .srt).
  2. Strip VTT/SRT headers, styling tags, and duplicate lines.
  3. Save as <Video Title>.txt with one Timestamp Text entry per line.

2.5 Verify Results

  • Exit code 0: Convert and save the subtitle file, then report completion.
  • Exit code non-0:
    • If error is related to browser/cookies, ask user for correct browser and retry.
    • If other errors (e.g., video unavailable), proceed to Step 3.

Step 3: Browser Automation (Fallback)

When the CLI method fails or yt-dlp is missing, use Chrome DevTools MCP to extract subtitles via browser UI automation.

3.1 Check Tool Availability

Check if Chrome DevTools MCP tools are available (look for tools matching chrome__new_page or similar).

If Chrome DevTools MCP is not available and yt-dlp was not found in Step 2, stop and notify the user: "Unable to proceed. Please either install yt-dlp (for fast CLI extraction) or configure Chrome DevTools MCP (for browser automation)."

3.2 Open Video Page

Use Chrome DevTools MCP new_page to open the video URL.

3.3 Analyze Page State

Use Chrome DevTools MCP take_snapshot to read the page accessibility tree.

3.4 Expand Video Description

The "Show transcript" button is usually hidden within the collapsed description area.

  1. Search the snapshot for a button labeled "...more", "...更多", or "Show more" (in the description block below the video title).
  2. Use Chrome DevTools MCP click to click that button.

3.5 Open Transcript Panel

  1. Use Chrome DevTools MCP take_snapshot to get the updated UI.
  2. Search for a button labeled "Show transcript", "显示转录稿", or "内容转文字".
  3. Use Chrome DevTools MCP click to click that button.
  4. If the button is not found, the video may not have a transcript available — notify the user and stop.

3.6 Extract Content via DOM

Directly reading the accessibility tree for long transcript lists is slow and token-heavy. Use Chrome DevTools MCP evaluate_script to run this JavaScript instead:

() => {
  const segments = document.querySelectorAll("ytd-transcript-segment-renderer");
  if (!segments.length) return "BUFFERING";
  return Array.from(segments)
    .map((seg) => {
      const time = seg.querySelector(".segment-timestamp")?.innerText.trim();
      const text = seg.querySelector(".segment-text")?.innerText.trim();
      return `${time} ${text}`;
    })
    .join("\n");
};

If it returns "BUFFERING", wait a few seconds and retry (up to 3 attempts).

3.7 Save and Cleanup

  1. Save the extracted text as <Video Title>.txt.
  2. Use Chrome DevTools MCP close_page to release resources.

Output Requirements

  • Save the subtitle file to the current working directory.
  • Filename format: <Video Title>.txt
  • File content format: Each line should be Timestamp Subtitle Text.
  • Report upon completion: file path, subtitle language, and total number of lines.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Explore user intent, requirements, and design options through collaborative dialogue before implementation. Use before building new features, components, or systems — whenever the user describes something to build and design decisions are involved. Triggers: "brainstorm", "help me design", "think through the requirements", "头脑风暴", "设计方案", "梳理需求". Not for bug fixes, config changes, or tasks with an obvious implementation path.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

Leverage OpenAI Codex/GPT models for autonomous code implementation, code review, and plan review. Triggers: "codex", "use gpt", "gpt-5", "let openai", "full-auto", "adversarial review", "second opinion review", "用codex", "让gpt实现", "对抗式审查", "让codex审查计划", "第二意见". Use this skill whenever the user wants to delegate coding tasks to OpenAI models, run code or plan reviews via codex, get a second-opinion review from a different model, or execute tasks in a sandboxed environment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

Multi-agent research orchestration: split a research goal into parallel sub-goals, run each via headless `claude -p` subprocesses, aggregate results into a polished report file. Use for systematic web/document research, competitive or industry analysis, batch link/dataset processing, and long-form evidence synthesis. Triggers: "深度调研", "deep research", "wide research", "多 Agent 调研", "系统调研".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for local uncommitted changes — this skill only reviews pull requests on GitHub.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

Generate or edit images using OpenAI GPT Image API (gpt-image-2, gpt-image-1, etc). Use ONLY when the user explicitly names OpenAI or GPT as the provider: "gpt image", "openai image", "generate image with openai", "用 openai 画图", "用 GPT 生成图片". For generic image requests without a provider, use nanobanana-skill instead. Do NOT use for diagrams (架构图/流程图) — draw those with Mermaid or code.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

feiskyer/claude-code-settings1.7천2026년 9월 28일 업데이트

feiskyer의 스킬 모두 보기

이 스킬의 문제 신고