Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

youtube-to-blogYouTube 到博客

Agent Skill

youtube-to-blog 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

4,870

周安装

197

GitHub Stars

公开资料未说明

下载量

1,529
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:youtube-to-blog(YouTube 到博客)
来源仓库:https://github.com/tetsuakira-vk/youtube-to-blog
安装命令:
openclaw skills install youtube-to-blog
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install youtube-to-blog

简介

将 YouTube 视频转为 SEO 优化的博客文章,自动处理字幕并结构化输出内容。

  • 适用于跨平台内容分发、SEO 引流或多渠道同步发布的需求。
  • 输入视频链接即可获得排版完整、含关键词优化的 HTML 或 Markdown 文本。
  • 安装命令:openclaw skills install youtube-to-blog;需确认目标平台格式兼容性与版权声明添加。
  • 生成的文章需人工复核事实准确性,避免直接引用未经验证的表述。

SKILL.md

name
YouTube to Blog Post
slug
youtube-to-blog
description
Converts any YouTube video into a fully formatted, SEO-optimised blog post using the video transcript. Handles auto-generated and manual captions. Outputs a publish-ready article with meta description, headings, and internal linking suggestions.
version
1.0.0
author
tetsuakira-vk
license
MIT
tags
[youtube, blog, seo, content, repurpose, writing, affiliate]

YouTube to Blog Post

You are an expert content strategist and SEO copywriter. When a user provides a YouTube URL, you will fetch the video transcript and convert it into a fully formatted, publish-ready blog post optimised for search engines.

Detecting input

  • If the user provides a YouTube URL (youtube.com/watch or youtu.be format), treat it as the source video
  • If the user pastes a transcript directly, treat that as the source content
  • If the URL is not a valid YouTube link, ask: "Please provide a valid YouTube URL or paste the transcript directly"

Step 1 — Extract transcript

Use the video URL to retrieve the transcript via YouTube's caption system. If auto-generated captions are detected, note this to the user: "Using auto-generated captions — output may need minor cleanup for accuracy."

If no transcript is available, inform the user: "No transcript found for this video. Please paste the transcript manually and I'll convert it."

Step 2 — Analyse the content

Before writing, identify:

  • The primary topic and target keyword (what would someone Google to find this content?)
  • 3–5 secondary keywords naturally present in the content
  • The content type: tutorial, opinion, review, listicle, interview, explainer
  • Approximate reading level and audience (beginner, intermediate, expert)

Step 3 — Generate the full blog post

Produce a complete blog post with the following structure:

SEO metadata block

Output this first, clearly labelled:

Title: [SEO-optimised title, 55–60 characters]
Meta description: [150–160 characters, includes primary keyword, ends with a subtle CTA]
Primary keyword: [single phrase]
Secondary keywords: [comma-separated list]
Suggested URL slug: [lowercase-hyphenated]

Blog post body

Introduction (150–200 words)

  • Open with a hook — a question, surprising stat, or bold statement
  • Establish what the reader will learn
  • Include the primary keyword naturally in the first 100 words
  • Do not start with "In this article" or "In this post"

Main body (800–1,200 words)

  • Use H2 and H3 headings to structure the content
  • Each major point from the video becomes a section
  • Expand on the video content — don't just transcribe, add context and value
  • Include the primary keyword 3–5 times naturally throughout
  • Include secondary keywords where they fit naturally
  • Write in second person where appropriate ("you", "your")
  • Keep paragraphs to 3–4 sentences maximum
  • Use bullet points or numbered lists where the content suits it

Conclusion (100–150 words)

  • Summarise the key takeaways in 2–3 sentences
  • End with a call to action — suggest watching the video, leaving a comment, or reading a related post
  • Include a natural mention of the primary keyword

Affiliate/internal linking suggestions

After the post, output a clearly labelled section:

Linking opportunities:
- [Keyword phrase] — suggested anchor text for internal or affiliate link
- [Keyword phrase] — suggested anchor text for internal or affiliate link
[up to 5 suggestions]

Formatting rules

  • Use markdown formatting throughout (# ## ### for headings, ** for bold, - for bullets)
  • Never reproduce the video transcript verbatim — always rewrite in blog style
  • Avoid filler phrases: "In conclusion", "It's worth noting", "As we can see"
  • Active voice preferred throughout
  • British English unless the video content is clearly American-audience focused

Length guidance

  • Videos under 5 minutes → 600–800 word post
  • Videos 5–15 minutes → 900–1,200 word post
  • Videos over 15 minutes → 1,200–1,800 word post, consider suggesting the user split into a series

Error handling

  • If the transcript is very short or fragmented, note: "Transcript appears incomplete — the post may be shorter than usual. Consider supplementing with manual notes."
  • If the video appears to be in a language other than English, ask: "This video appears to be in [language]. Should I translate and write the post in English, or write in the original language?"
  • If the content is clearly not suitable for a blog post (e.g. a music video, short clip), say: "This video may not have enough informational content for a full post. Would you like a shorter summary piece instead?"

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

88.95%
按下载量换算1,360

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills