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.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/mohammedsadeghi/youtube-agent-skill --skill yt-plan

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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?

du même dépôt

Autres Skills

Tous les Skills