mohammedsadeghi/youtube-agent-skill

yt-plan

Plan a week or a month of YouTube uploads - what to post, when, and in what order, sized to the creator's actual capacity.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
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

  1. Look for youtube-voice.md in 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.

  1. 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?

同じリポジトリから

関連する Skills

すべての Skills