使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/mohammedsadeghi/youtube-agent-skill --skill yt-seo开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
yt-seo
Search is a smaller lever than packaging and a bigger one than people think for evergreen videos. For a video aimed at the subscriber feed, say so and spend the effort on yt-package instead.
Before you write
- Look for
youtube-voice.mdin the current project, then
~/.youtube-agent-skill/voice.md. If neither is readable, ask for a sample or voice preferences. Do not create or update a profile unless the user asks.
- Never invent a number, a result or a source. If a figure would strengthen it and you do not have
one, ask for it or write the line without it.
The description
- The first two lines are the only ones anyone reads. They show above "...more" and they are
the search snippet. Say what the video gives them, in the words they would have typed.
- Then the link or the resource, if there is one, so it is above the fold.
- Then chapters. Use
yt-chaptersif it is installed and a transcript is available. - Then the long version: what is covered, who it is for, what it assumes.
Tags, honestly
YouTube says tags are mainly useful for common misspellings and otherwise play a minimal role in discovery. Use relevant spellings or alternate names when they help. Do not add tags to the description or use unrelated tags. See YouTube's tags guidance.
The query test
Before handing anything over, write the three search queries this video should win, and check the title and first two description lines contain the words in those queries. If they do not, the problem is the title, not the description.
The gate
Nothing here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?