使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/mohammedsadeghi/youtube-agent-skill --skill yt-plan开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
yt-plan
A plan that does not fit the week is a list of regrets. Ask two questions before writing anything: how many hours do you actually have, and what is already half-made.
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 shape of a week
- One anchor. The video the week is for. It gets the most time and it goes out on the day the
channel's own analytics say is best - ask for that, do not assume Tuesday.
- One cheap one. Built from something that exists: a clip, a reaction, a follow-up to the
comment that got the most replies last week.
- Shorts from the anchor. Three, cut from the long video, not written separately. Use
yt-shorts
if it is installed; otherwise, plan clips from the transcript the user provides.
Three uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone recognises, and the empty days are what make the filled ones survive a bad week.
What to hand back
A table: day, format, working title, the one sentence it promises, and what already exists for it. Then the honest line at the bottom - how many hours this costs, and what to drop first if the week goes wrong.
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?