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

video-content

Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video. For a YouTube channel specifically — idea selection, retention teardowns, and channel-level strategy — use `youtube-producer`.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.2 KB
  • references/sources.md1.7 KB

SKILL.md(原文)

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

Video content

This covers video as a format across platforms — short-form, long-form, and the packaging that decides whether either gets watched. youtube-producer covers one platform in depth: channel strategy, idea selection against a channel's history, and retention teardowns against YouTube's own curves. When the question is about a channel rather than a video, it belongs there.

Packaging is most of the outcome

A video nobody clicks has no retention curve. Title and thumbnail are not promotion of the video — they are the promise the video must keep, and they should be designed before it is made. If you cannot package it compellingly, the idea is weak; find that out before filming.

Titles — specific over clever. Curiosity that a real answer resolves, not a withheld one. Front-load the distinguishing word, since titles truncate.

Thumbnails — one subject, readable at thumbnail size on a phone. High contrast. Text under about four words, or none. Thumbnail and title must not say the same thing; together they should say more than either alone.

Openings

The first fifteen seconds decide the rest. Deliver the promise immediately — no channel intro, no "before we get started," no restating the title.

Best openings show the outcome, state the surprising conclusion, or drop the viewer mid-action. Then say what the video will cover, briefly, so they know the shape of the commitment.

Structure by length

Short-form — one idea, opening frame that reads as motion, and a payoff before attention decays. No setup. The loop matters: end where the beginning makes sense again.

Long-form — chapters that each work standalone, with an explicit reason to continue at every seam. Retention is lost at transitions, not in the middle of sections. Vary pace deliberately; a uniformly intense video is as tiring as a flat one.

Diagnosing underperformance

  • Low click-through — packaging problem. Title and thumbnail, not content.
  • High click-through, early drop — the opening did not pay the promise. Or the promise was unpayable.
  • Steady mid-video decline — normal. Look at the slope against your own baseline, not absolutes.
  • Sharp mid-video cliff — find the timestamp and watch it. It is almost always a transition, a tangent, or a sponsor read placed badly.

Repurposing

Plan derivatives before filming, not after. Segments intended to stand alone get shot to stand alone. Extracting short-form from a video not built for it produces clips that need context they do not have.

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.

Tooling

Editing: DaVinci Resolve, Adobe Premiere Pro, Final Cut Pro, CapCut, and similar; Descript for transcript-driven editing, which is faster for talking-head and interview formats than a timeline.

Recording remote: Riverside, Zoom, StreamYard, and similar — record local tracks per participant where the tool supports it, because the connection quality on the day decides the ceiling otherwise.

Repurposing and captions: Opus Clip, Submagic, and similar. Burned-in captions are not optional; most viewing is silent, and the caption is the packaging on every platform that autoplays.

Never

  • Produce before the title and thumbnail exist. Packaging decides whether anything you shot gets seen.
  • Open with a preamble. The first seconds are where an audience is lost, not where it is warmed up.
  • Diagnose a video on view count alone. Impressions, click-through, and retention fail differently and need different fixes.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

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 のスキルをすべて見る

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