사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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?