CommunityWriting & Editinggithub.com

title

Writes and checks the YouTube title and the thumbnail text of an episode, before the script. Delivers five candidates with a hook and a reason each, one recommendation, and three variants for the A/B test; skills/title/scripts/title_check.py checks every candidate against the style pack. Use when: \"title\", \"video title\", \"YouTube title\", \"what should the video be called\", \"check this title\", \"shorten the title\", \"better title\", \"thumbnail text\". Not for the blog's search title and not for the thumbnail image.

What is title?

title is a Claude Code agent skill that writes and checks the YouTube title and the thumbnail text of an episode, before the script. Delivers five candidates with a hook and a reason each, one recommendation, and three variants for the A/B test; skills/title/scripts/title_check.py checks every candidate against the style pack. Use when: \"title\", \"video title\", \"YouTube title\", \"what should the video be called\", \"check this title\", \"shorten the title\", \"better title\", \"thumbnail text\". Not for the blog's search title and not for the thumbnail image.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/marcopatzelt/crewcut/tree/HEAD/skills/title

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does title do?

The title comes before the script. Title and thumbnail set what the viewer expects; the video must deliver exactly that. The Scout writes the title after the idea step and before the proof and the script.

Not here: the thumbnail image (skills/thumbnail/), the first sentence of the video (skills/script/).

Method

  1. Read the input. From the idea step: topic, tool, planned test, the numbers it will measure, proof videos. Read brand/rules/title.md and the title limits in channel.json (crewcut brand show). If a number is not measured yet, write [N] and mark the title as provisional.
  2. Write five candidates, each with a different hook. A hook is the reason to click: free or money, a time promise, something new, excitement, an explanation for beginners. The click words that work in the user's language are in voice.md (## Title hooks) when the Brand identity found them; otherwise judge by the proof videos.
    • The best-known name early. The thing the title is about is the best-known thing of its class (the famous product, not the category word), and it starts within the first characters (title.name_within). Phones cut long titles.
    • A number only when it is real. It comes from the own test and matches what the video shows.
    • A price ladder ("for 1, 10 and 100") or a contrast ("cheap beats expensive") only when the video measures every step or shows the contrast. If the measurement turns out differently, the title changes before the upload.
    • Plain words and a promise. No category jargon, no business words in the title: the title speaks to everyone, the business case sits inside the video.
  3. Check. python3 skills/title/scripts/title_check.py "Title 1" … "Title 5" --name "<tool>". A candidate with an error does not go to the user; rewrite until all five pass. A hint "No hook" means: sharpen the reason to click. The script ranks with points; the points are a ranking aid, not a forecast.
  4. Thumbnail text. At most thumbnail.max_words words: one key word of the title and the verdict. Never the whole title. Check it with --thumbnail "<text>".
  5. Three variants for the A/B test (channel.json title.variants): place 1 the recommended title; place 2 the same title with exactly one change (the hypothesis: without the number, or with one click word); place 3 a calmer variant, or for an old video its current title as control. Check all three.
  6. Write brief/TITLE-vNNN.md: chosen title, characters, the promise, the hook, the number and where it comes from, the thumbnail text, the three test variants, rejected candidates with the reason. Never overwrite a version.
  7. Humanizer pass on the words. Before the card, run the Humanizer skill over the five titles and the thumbnail text (write them first to work/titles-draft-vNNN.md), the same way as the script (skills/script, "Humanizer pass"): look for advertising language, inflated meaning and staged run-ups; the click words of voice.md (## Title hooks) and every number stay. Record it: crewcut humanize record --draft work/titles-draft-vNNN.md --final brief/TITLE-vNNN.md. The card then shows what changed.
  8. Card. crewcut card propose --episode <id> --step title --kind title --title "Pick a title" --file brief/TITLE-vNNN.md --body "Recommendation: option 1. <one sentence why>" --option "<1>" … --option "<5>", then crewcut card wait.
  9. Hand over. To the proof step: the promise and the number to measure. To the script: promise, tool, number. To the Designer: title, thumbnail text, verdict, the three variants.
  10. After the proof, check again. Do the number and the hook still hold? If not, write a new version and a new card before the script starts.

A title change after the upload needs a card and goes through skills/upload/.

What the check cannot see

Whether the number is real, whether the video keeps the hook, which name is better known, whether every step of a ladder is measured. That is reading work in steps 2 and 9.

Card format

Title (recommendation first)
1. <title>  (<N> characters) · hook: <…> · reason: <proof video or rule>   <- recommendation
2. …
Thumbnail: <key word + verdict>
All five pass title_check.py (points: 64, 61, …).

Planned

  • A results table from the 48-hour checks (review/results-48h.json of past episodes) that the title step reads to weigh hooks by the user's own data.
  • Language data packs: hook words with measured effects per language, built from public title studies (the studio had a German one; its raw data is not part of Crewcut).

Sources

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

edit

Builds a video version from the user's recording: the speaker cut, then one edit plan with all inserts (2D scenes, 3D scenes, recordings, keywords), sound and music, built with one command (crewcut render). Use for: edit the video, build the cut, speaker cut, rough cut, insert, b-roll, 2D scene, 3D insert, counter, keyword, music bed, sound, assemble, render the preview, new plan version, short from the long video.

script

Writes the spoken script of an episode in the user's own voice (voice.md), in teleprompter form, after title and proof are fixed: opening that delivers the title's promise, small stories with rising stakes, the critical side, a verdict in its own form, the channel's closing line. skills/script/scripts/script_check.py checks form, sentences, opening, ending, numbers against the proof, and length. Delivered through the web teleprompter (crewcut prompter). Use when: \"write the script\", \"teleprompter text\", \"rewrite the script\", \"shorten the script\", \"make it sound natural\", \"script for the episode\". Not for titles or thumbnails. Short scripts: the `--short` mode of the check and skills/shorts.

shorts

Makes YouTube Shorts in two modes: Clip (cut from a finished episode: candidates from the transcript and retention, a 9:16 rough cut from the original recording around the face, portrait graphics, music with clear rights, the Critic's own Short check) and Original (a Short recorded for itself: three ideas with a proof from the user's real work, the user talks freely, the Writer shortens, only the speaker is recorded, the crew brings the B-roll). Publishing: one card per Short, or the user's own standing approval for Shorts; at most two a day. Use when: \"make shorts\", \"make a short about …\", \"clip this episode\", \"short from episode N\", \"publish shorts without asking\", \"how are my shorts doing\". Not for long videos (skills/episode, skills/edit).

Related Skills