jakeschincariol/youtube-agent-skill

yt-comment

Draft replies to YouTube comments in the creator's voice, triaged by which ones are worth answering.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-comment

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

yt-comment

The comment section is a retention surface, not a chore. Replies in the first few hours are what decide whether a thread becomes a conversation other people read.

Before you write

  1. Read ~/.claude/youtube/voice.md if it exists. That is the user's voice profile: how they talk

on camera, the words they never use, who they are talking to, what they will not claim. If it does not exist, ask for three of their own videos, read or transcribe them, infer the voice, and write the file. A script in the wrong voice is worse than no script, because they have to read it out loud.

  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.

Triage first, always

Sort what the user pastes into four piles and say how many are in each before writing anything:

  1. Questions - answer them. These are your next video's topics, so note the repeats.
  2. Corrections - if they are right, say so plainly and thank them. Never argue a fact you

cannot check.

  1. Praise - reply to a few, briefly, with something specific from their comment. A wall of

identical "thank you!" replies reads as automated because it is.

  1. Bait - do not reply. Say so and move on. Never write a comeback, however deserved.

Writing the reply

  • Under 30 words. A long reply in a comment thread is a blog post nobody asked for.
  • Answer the actual question in the first sentence.
  • One question back, only when it is real.
  • No emoji unless the user's own replies use them. Check their voice file.
  • Never promise a video you have not agreed to make.

The heart and the pin

Say which ONE comment to pin and why. Pin the question the most people also have, not the nicest one. Heart generously - it costs nothing and it is visible.

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
jakeschincariol
コミュニティ

yt-audit

Audit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for "audit my channel", "why isn't my channel growing", "review my videos", or a pasted channel URL.

1時間の導入数
4
GitHub Stars
6791
更新日
9月16日
jakeschincariol
コミュニティ

yt-chapters

Write YouTube chapters from a transcript, validated against YouTube's own rules so they actually render. Use for "add chapters", "timestamps", "break this video into sections".

1時間の導入数
4
GitHub Stars
6791
更新日
9月16日
jakeschincariol
コミュニティ

yt-package

Write and lint the title and thumbnail for a YouTube video as one pairing, checking truncation, duplication and vagueness before publish. Use for "title ideas", "what should I call this", "thumbnail text", "my CTR is bad", packaging, or any request to rename or repackage an existing video.

1時間の導入数
4
GitHub Stars
6791
更新日
9月16日
jakeschincariol
コミュニティ

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. Use for "plan my week", "content calendar", "what should I post", "I have no idea what to make next".

1時間の導入数
4
GitHub Stars
6791
更新日
9月16日