本文へ移動
cccskills
無料GitHub で公開

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.2 KB
  • references/sources.md1.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

YouTube producer

Package before you produce

Title and thumbnail decide whether a video is watched at all. Design them first, as a test of the idea: if you cannot package it compellingly, the idea is weak and you have found that out before spending a week filming.

Titles. Specific over clever. Front-load the distinguishing word — titles truncate, and the distinguishing word is usually last in a natural sentence. Curiosity only where the video genuinely resolves it; unresolved curiosity trains people not to click next time.

Thumbnails. One subject, readable at phone-thumbnail size. High contrast, minimal text, real faces outperform objects for most channels. Title and thumbnail must not say the same thing — together they should say more than either alone.

Make three packaging options per idea and pick the one that would make you click while scrolling past something else.

Idea selection

The best ideas sit where audience demand, your unusual knowledge, and a packageable hook overlap. Missing any one produces a predictable failure: no demand means nobody searches, no unusual knowledge means it is generic, no hook means nobody clicks.

Check what already exists on the topic. Not to avoid it — a crowded topic proves demand — but to find the angle nobody took.

The first thirty seconds

Deliver the promise immediately. No channel intro, no "before we get started," no restating the title. Show the outcome, state the surprising conclusion, or drop the viewer mid-action.

Then briefly say what the video covers, so the viewer knows the shape of the commitment they are making.

Retention structure

Retention is lost at seams, not in the middle of sections. Every transition needs an explicit reason to continue — an open question, a promised payoff, a stated next step.

  • Chapter it. Each section should work standalone and end pointing forward.
  • Vary pace deliberately. A uniformly intense video is as tiring as a flat one.
  • Front-load value. Withholding the good part until the end optimizes for a viewer who is no longer watching.
  • Place sponsor reads after the first payoff, never before it.

Visual direction and editing

Retention is as much editing as writing. The script sets what is said; the edit sets whether it is watched.

  • Cut on the beat of meaning, not on a timer. Rhythmic cutting for its own sake reads as noise.
  • Show, then say. Where footage can carry the point, let it, and cut the sentence explaining it.
  • B-roll earns its place by showing something the words cannot. Decorative b-roll is dead air with pictures.
  • Text on screen for anything numeric or named. Viewers do not retain spoken numbers.
  • Remove every pause, restart, and filler word in the first thirty seconds without exception. Later in the video, some breathing room is worth keeping — an unrelentingly tight edit is exhausting.
  • Change something visually at each chapter transition. Transitions are where viewers leave, and a visual change is a cheap reason to stay.

Write editing notes into the script as you go — the shot, the on-screen text, the moment to cut away. Deciding this in the edit costs far more time than deciding it while writing.

Diagnosing

  • Low click-through — packaging. Title and thumbnail, not content.
  • High click-through, immediate drop — the opening did not pay the promise, or the promise was unpayable.
  • Gradual decline — normal. Judge the slope against your own baseline, not against absolutes.
  • A sharp cliff mid-video — find the timestamp and watch it. Almost always a transition, a tangent, or a badly placed sponsor read.
  • Good retention, no growth — the videos work but the packaging is not earning impressions, or the topics have no audience beyond existing subscribers.

Channel level

Consistency of promise matters more than consistency of schedule. A channel whose videos deliver different kinds of value teaches the audience nothing about whether to click the next one.

Plan repurposing before filming — segments meant to stand alone as short-form get shot to stand alone.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Produce an idea whose title you cannot write. If the title is hard, the idea is not yet clear.
  • Judge a video on its first day. The signal that matters accrues over weeks.
  • Change what the channel is about because one video underperformed.
  • Fix retention by cutting faster when the problem is that the promise was wrong.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する