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

youtube-launch-kitYouTube 启动套件

Agent Skill

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

总安装

1,529

周安装

65

GitHub Stars

公开资料未说明

下载量

536
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install youtube-launch-kit

简介

将视频主题或文字记录转化为完整的 YouTube 发布方案。

  • 提供标题变体、关键词优化描述与发布时间建议。
  • 自动化生成符合平台算法的内容包装策略。
  • 适用于新频道启动或内容矩阵规划场景。
  • 建议结合真实受众画像调整输出结果。youtube-launch-kit 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

slug
youtube-launch-kit
name
YouTube Launch Kit
description
Turn a video topic, rough notes, or transcript into a complete YouTube launch package. Outputs two title variants, a keyword-optimized description with timestamped chapters, 10 tags, a pinned comment, a discussion seed (also known as first comment prompt or first pinned comment), an optional thumbnail prompt, and an optional 3-tweet promo set. Use when a creator pastes a video topic, outline, notes, or transcript and asks for a title, description, tags, launch copy, pinned comment, first comment prompt, discussion seed, thumbnail idea, or promo tweets for YouTube.
version
1.0.0
license
MIT
tags
metadata
openclaw
requires
env
[]
bins
[]

YouTube Launch Kit

Turn a video concept or recording into a complete launch package — titles, description, chapters, tags, pinned comment, discussion seed, and optional promo assets. One paste in, full launch out.

When to use this skill

Trigger this skill when the user:

  • Pastes a video topic, rough notes, or outline and asks for a title, description, or tags
  • Shares a transcript and wants launch copy generated from it
  • Says "write my YouTube description," "optimize my title," "what tags should I use," "write my pinned comment," "write a first comment prompt," "write a discussion seed," "give me a thumbnail prompt," or "help me launch this video"
  • Asks for a full YouTube launch package or upload checklist
  • Wants promo tweets or social copy for a YouTube video

Do NOT trigger for:

  • Channel strategy or long-term content planning — out of scope
  • Video editing notes or scripting (pre-production writing, not launch copy)
  • Analytics review or performance diagnosis — separate skill

Step 1 — Identify input state and collect what's missing

Determine which of three input states the user is in. Do not ask clarifying questions beyond what's listed below.

State A: Topic + notes/outline (primary)

User has a concept and rough structure but hasn't recorded yet.

Required:

  1. Video topic (one sentence describing what the video covers)
  2. Notes or outline — bullet points, rough section order, key points to hit, anything they've planned

Optional (use if provided, don't ask twice):

  1. Target audience (e.g., "beginners," "freelance designers," "new parents")
  2. Channel niche or name
  3. Tone — educational, entertaining, motivational, tutorial-focused (default: educational/tutorial)

If notes are missing and only a topic is provided, proceed as State C and note the limitation.

State B: Transcript (fallback)

User has already recorded and has a transcript from auto-captions, Whisper, or another source.

Required: The transcript text (full or partial — work with what's provided)

Optional: Target audience, channel niche, tone

From the transcript: extract real chapter structure, pull exact phrases for keyword-dense copy, and use the creator's own language in the description and pinned comment.

State C: Topic only (edge case)

User has a topic but no notes and no transcript.

Proceed with title variants, tags, description intro paragraph, and a structural chapter scaffold. State explicitly once: *"Chapter timestamps are structural placeholders — fill in the actual times after recording."* Do not repeat this caveat.


Step 2 — Generate the launch package

Deliver all core deliverables in a single response, clearly labeled with H2 headers. Never skip a core deliverable. Offer optional deliverables at the end.


Title Variants (2)

Produce exactly two variants. Label them by intent, not by letter/number.

Curiosity-framed: Withhold one key detail or tease the outcome. Front-load the most compelling word or phrase. Drives browse traffic (suggested videos, homepage feed).

Clarity-framed: Direct, keyword-forward, searchable. Lead with the primary keyword. Drives search traffic.

Rules:

  • Maximum 60 characters each (YouTube truncates beyond this in most surfaces)
  • No manufactured urgency ("You WON'T believe...") unless the video genuinely delivers a surprise
  • No all-caps words
  • No trailing ellipsis in the clarity variant

Description

Structure in this exact order:

Opening paragraph (first 150–200 characters): Keyword-dense, hooks the viewer and states the video's premise. This is what appears above-the-fold in search results and what YouTube's algorithm indexes most heavily. Must contain the primary keyword naturally — do not stuff.

Body (2–3 sentences): Expand on what the viewer will get. Written in the creator's voice. Specific, not generic ("You'll learn the exact 3-step process I use" > "This video covers a lot of useful tips").

Timestamped chapters: Minimum 4 chapters. First chapter must be at 0:00. Labels must be content-specific — never use "Intro," "Part 1," "Outro," or "Conclusion" as standalone labels.

  • State A/C inputs: Use structural timestamps in 0:00 / XX:XX placeholder format. The creator fills in actual times post-recording.
  • State B (transcript): Derive timestamps from transcript structure. Use actual minute markers where inferable.

CTA section: One subscribe prompt + one resource link placeholder [LINK]. Keep brief — two lines maximum.


Tags (10)

Apply the tag formula exactly:

  • 2 broad tags — high-volume, category-level (e.g., productivity, YouTube)
  • 5 niche tags — specific to the topic and audience (e.g., notion for beginners, youtube growth tips)
  • 3 long-tail tags — exact-phrase searches a viewer would type (e.g., how to organize your notion workspace, youtube tags for small channels)

First tag must exactly match or closely mirror the chosen title — this is YouTube's strongest tag-to-title relevance signal.

Present tags as a comma-separated list, ready to paste into the YouTube tag field.


Pinned Comment

50–80 words. Written in the creator's voice, intended to be pinned to the top of the comments.

Purpose: sticky reference — chapters, key resources, corrections, or links mentioned in the video. Not an engagement play; that's the discussion seed.

Format: lead with a chapter list or the most valuable resource, then link placeholders. Example structure:

⏱ Chapters are in the description — jump to whatever's most useful. 🔗 [Resource name]: [LINK] 🔗 [Resource name]: [LINK]

Discussion Seed

20–40 words. A question the creator posts as their first comment to seed early replies.

Rules:

  • Must be specific to this video's content — never "What did you think?" or "Let me know in the comments!"
  • Framed in first person from the creator's voice
  • Asks something the viewer can answer from their own experience, not just by recapping the video
  • Also called "first comment prompt" or "first pinned comment" in other frameworks — same output, different name

Optional Deliverables

After delivering the five core outputs above, offer both of the following once. Generate whichever ones the user requests (or both if they asked upfront):

Thumbnail Prompt (optional) A Midjourney or DALL-E compatible image prompt for the video thumbnail. Format:

  • Subject description (person, object, or scene)
  • Visual style (photo-realistic, illustrated, bold graphic, etc.)
  • Text overlay suggestion (short phrase, ≤5 words, high contrast)
  • Aspect ratio: 16:9

Promo Tweet Set (optional) 3 tweets, each ≤280 characters. Sequence:

  1. Announcement — just published, what the video is about, link placeholder [YOUTUBE_LINK]
  2. Hook — the most interesting insight, counterintuitive point, or moment from the video
  3. CTA — subscriber-directed, drives watch + subscribe

Do not auto-generate optional deliverables unless asked. Offer them at the end of the core package.


Step 3 — SEO rules

Rules-based layer (apply to every output)

These signals are derived from known YouTube algorithm behavior — apply them without exception:

  1. Description opening: First 100–150 characters do the most indexing work. Primary keyword must appear here, naturally integrated.
  2. Title-tag alignment: First tag mirrors the winning title. No exceptions.
  3. Tag formula: Enforced as written above — 2 broad, 5 niche, 3 long-tail. Padding beyond 10 provides no ranking benefit and dilutes relevance.
  4. Chapter labels: YouTube uses chapter titles as secondary index signals. Descriptive labels outperform generic ones.
  5. Title length: 60-character ceiling. Titles truncated in search results lose click-through rate.

LLM knowledge layer

Keyword selection and semantic variation draw on training knowledge of what searches well in a given niche. This works reliably for evergreen topics across most creator categories.

Honest ceiling — state this once in every session, do not repeat:

*"Keyword recommendations reflect training knowledge, not live search data. For trending topics or highly competitive niches, validate tags with TubeBuddy or VidIQ after running this skill."*

No external API key is required and none should be suggested as mandatory. TubeBuddy/VidIQ are validation tools, not prerequisites.


Step 4 — Style guardrails

  • Never invent content. Do not include facts, statistics, claims, or timestamps not present in the input. If the notes don't mention a specific number, don't write one.
  • No generic chapter labels. "Intro," "Main Content," "Part 2," "Conclusion" are banned as standalone labels.
  • No "like and subscribe" in the pinned comment. Creators know to ask; including it reads as template filler.
  • Match the creator's voice. If the notes use casual language, the description uses casual language. Don't formalize input that wasn't formal.
  • Curiosity title must deliver. If the video input doesn't support the curiosity framing, use the clarity variant as the recommended title and note why.
  • Description body is specific, not hype. "You'll learn the exact method" > "This video is packed with tips."

Step 5 — Follow-up offers

After delivering the package, offer once:

  • "Want a version of either title tuned for a different audience or tone?"
  • "Want the thumbnail prompt or promo tweet set?"
  • "If you have a transcript, I can regenerate with accurate chapter timestamps."

Do not auto-regenerate unless asked.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

72.36%
按下载量换算388

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills