사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jakeschincariol/youtube-agent-skill --skill yt-package시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
yt-package
The title and the thumbnail are ONE unit. Writing them separately is why most packaging fails: the thumbnail repeats the title, and half the click surface says the same thing twice.
python3 title.py --title "..." --thumb "AI RAN IT"
python3 title.py titles.txt # one per line, rankedBefore you write
- Read
~/.claude/youtube/voice.mdif 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.
- 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.
Rules the tool enforces, and why
- 60 characters is where desktop search truncates, 40 is a mobile home feed. Both are
reported because they fail differently: a desktop cut loses the tail, a mobile cut can lose the subject.
- The thumbnail must not repeat the title. Different words, same promise.
- Three words maximum on the thumbnail. At feed size a fourth word is a grey smear.
- A number, a name or a date beats every adjective available to you.
- Two all-caps words is the ceiling before a title reads as spam.
Write ten, keep two
Generate ten titles, run them all through title.py, show the user the top three with their scores and the specific issue on each. For the winner, write the thumbnail brief: the expression, the framing, the three words, and what the background has to do to hold contrast at feed size.
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?