YouTube To Blog Post

Turn YouTube videos into publication-ready Hugo posts that match this repository's blogging conventions.

When to Use This Skill

Use this skill when:

• •The user provides only YouTube URL(s) with no extra writing instructions.
• •The user asks to convert a YouTube video into a technical blog post.
• •The user wants one cohesive post from multiple YouTube links.

Do not use this skill for non-YouTube-only source sets.

Core Workflow

1. •Parse input URLs and keep original order.
2. •Extract each YouTube video ID from youtube.com/watch, youtu.be, or youtube.com/shorts format.
3. •Gather source material with YouTube MCP:
   • •youtube_get_video
   • •youtube_get_transcript (prefer chunks or full for depth)
   • •youtube_segment_topics
   • •youtube_extract_entities
   • •youtube_get_comments only when audience reactions add useful context
4. •Build structured notes per key claim: claim, transcript quote/time marker, video url, confidence.
5. •Build a fixed output outline first, then write section-by-section from notes, prioritizing explanation accuracy over aggressive compression.
6. •Generate exactly one post file under content/post/YYYY/YYYY-MM-DD-slug.md unless the user explicitly asks for multiple posts.
7. •Write the post in Korean by default unless the user explicitly requests another language.
8. •Run a completion audit against required section order and checklist (PASS/FAIL per item).
9. •Run task build before handoff.

Anti-Truncation Execution Rules

• •Never draft in one long free-form pass.
• •Use a staged pipeline:
  1. •source collection -> 2) evidence notes -> 3) fixed outline -> 4) section-by-section writing -> 5) completion audit.
• •Fixed outline must include every required section before body writing starts.
• •If transcript depth is insufficient for any segment, mark uncertainty and avoid high-confidence technical assertions for that segment.
• •If any required section is missing after writing, regenerate only missing sections and re-run the audit.
• •Hard gate: no final handoff is allowed unless all checklist items are PASS.

Required Post Contract

Use YAML frontmatter with at least:

---
title: "..."
date: 2026-02-21T17:00:00+09:00
draft: false
categories:
  - ...
tags:
  - ...
description: "..."
---

Body requirements:

• •Write in Korean unless user explicitly requests another language.
• •Add a concise intro.
• •Insert <!--more--> after the intro/excerpt area.
• •Add a Sources section immediately after <!--more--> with all input URLs in original order.
• •Use this exact section order:
  1. •Intro
  2. •<!--more-->
  3. •Sources
  4. •Topic Sections (at least 3, based on transcript/topic segmentation)
  5. •Practical Takeaways
  6. •Conclusion
• •Prioritize precise explanation of mechanisms, assumptions, and trade-offs over short summary-style writing.
• •For key technical points, explain what, why, and how concretely.
• •Use Mermaid diagrams aggressively for flows, architecture, timelines, and comparisons.
• •Require Mermaid in at least 2 major technical sections.
• •Prefer multiple small Mermaid diagrams over one oversized diagram.
• •Add practical takeaways and a short conclusion.

Synthesis Rules

• •Keep claims grounded in transcript and metadata context.
• •Do not dump raw transcript text.
• •Prefer source-backed explicit explanations over broad paraphrased summaries.
• •Resolve overlap or conflicts by prioritizing primary-source statements.
• •If uncertainty exists, state uncertainty explicitly instead of inventing details.
• •Ensure every non-trivial factual paragraph in the final post maps to at least one evidence-note entry.

Multi-URL Rule

• •If multiple YouTube URLs are given, produce one unified post by default.
• •Do not split into multiple posts unless the user explicitly requests it.

Validation Checklist

1. •Confirm file path follows content/post/YYYY/YYYY-MM-DD-slug.md.
2. •Confirm exactly one new post file was created for this request (unless user explicitly asked split output).
3. •Confirm frontmatter includes title, date, draft: false, categories, tags, description.
4. •Confirm section order is exactly: Intro -> <!--more--> -> Sources -> Topic Sections(>=3) -> Practical Takeaways -> Conclusion.
5. •Confirm Sources includes all input URLs in original order.
6. •Confirm Mermaid diagrams appear in at least 2 major technical sections.
7. •Confirm core sections explain key claims with concrete detail, not only high-level summaries.
8. •Confirm every non-trivial factual paragraph maps to evidence notes.
9. •Run task build and verify success.

Checklist enforcement:

• •Mark each item as PASS/FAIL explicitly.
• •If any item is FAIL, do not hand off. Fix gaps and rerun the checklist.

references/youtube-post-quality-checklist.md is mandatory acceptance criteria, not optional reference.