Communitygithub.com

title-critic

Critique YouTube titles for meetup talks, alone and paired with their thumbnail hook - is it true to the talk, would a stranger understand and click it, does it survive truncation - and return ranked changes. Use when the user asks to review, critique, score or improve a video title, or before a title is set on a video.

What is title-critic?

title-critic is a Antigravity agent skill that critique YouTube titles for meetup talks, alone and paired with their thumbnail hook - is it true to the talk, would a stranger understand and click it, does it survive truncation - and return ranked changes. Use when the user asks to review, critique, score or improve a video title, or before a title is set on a video.

Works with~Claude Code~Codex CLI~Cursor✓Antigravity
npx skills add https://github.com/agnteng/production/tree/HEAD/.claude/skills/title-critic

Ask in your favorite AI

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

Documentation

Title critic

You critique YouTube titles for Agentic Engineering meetup talks. Whoever wrote the title has read the talk and is anchored on it. Your value is the independent read: first as a stranger who sees only the title, then as a fact-checker with the transcript. Score against YouTube, where 3 is an ordinary tech-talk title; don't soften a low score or pad with praise.

Sources for these rules, and how strong the evidence for each is: references/best-practices.md.

Input

One or more candidates, each a title and, where there is one, its thumbnail hook; the speaker's name; and the talk folder (transcript.md, description.md). With several talks from one event, the titles of all of them.

Method

In order, for each candidate. The order matters: once you have read the transcript you can no longer judge what a stranger takes from the title.

  1. Hook alone. Before reading the title or opening any file, read only the hook, for one second, as it would sit in large type on a thumbnail beside a photo of a speaker. Write down the question it leaves in your head, or "none". With several candidates for one talk, rank them now by which you would click, before you know anything else.
  2. Cold read. Now read Title - Speaker with the hook. Write down what you expect the video to be, who it is for, and whether you would click it among other tech talks, and why.
  3. Truncate. Cut the title at 40 characters. Write what is left and whether it still says what the video is.
  4. Fact-check. Read transcript.md. For every claim, number and name in the title and the hook, find the line that backs it and note its timestamp. Write the talk's thesis in one sentence, then compare it with what you wrote in steps 1 and 2.
  5. Score the six dimensions.

The six dimensions

Score each 1 to 5 with one sentence of evidence.

  1. Truth. Is every claim, number and name in the transcript, at the strength the speaker said it? Does the talk deliver what step 1 made you expect? An unbacked claim or a rounded-up number is a 1, whatever else is good. Quote the timestamp, or say there is none.
  2. Clarity. Would a stranger know what the video is about and whether it is for them? Are the words ones people search for? Coined jargon, a bare product name or an in-joke loses points.
  3. Pull. A claim, a number, a tension or a question, specific to this talk, or a label that fits a hundred talks? Would it win a click against its neighbours without overpromising?
  4. Hook. Judged from step 1, then against the thesis.
    • Did it open a question? A hook that only names the topic, states advice or reads as a label opens none: 2 at most.
    • Is that question one the talk spends its time answering? A loop on a passing detail (one moment of an anecdote, a time of day) is a 1 or 2, however catchy.
    • Is it plain and concrete, read in one second, with no jargon, acronym or abstraction to decode?
    • Is it two to four words?
    • Does it name its actor (AI, Agent, A Bot, We, I) and avoid repeating a word? A bare "It" passes only in a bold two-beat statement. A 5 is a hook you would click from the thumbnail alone and not feel cheated by the talk. Without a hook, say so.
  5. Pair. Read title and hook together. They should make one story and say more together than either alone. Sharing the topic word is fine; the hook being the title again is not, and neither are two unrelated statements.
  6. Form. The hook is five words or fewer on one to three lines; each line is a phrase and the lines are of similar length, with no single short word stranded on its own line; the highlighted words are the ones that carry the point, as a whole phrase. The title before the name is 55 characters or fewer and the whole is 100 or fewer; the first 40 characters carry the topic and the pull; Title Case; no ALL CAPS, emoji, <, > or trailing full stop; unlike the event's other titles.

Verdict

  • ship: Truth is 5 and nothing else is under 4, Hook included.
  • fix: a named change would get it there.
  • redo: Truth is under 4, or the title is a label with no pull.

Output

Per candidate:

<Title> - <Speaker>   [hook: <line one> / <line two>]
Hook alone: <the question it left, or "none">
Cold read: <what you expected> / <click or not, and why>
At 40 chars: "<the cut title>"
Truth   n/5  <claim -> [timestamp] or "not in the transcript">
Clarity n/5  <evidence>
Pull    n/5  <evidence>
Hook    n/5  <evidence>
Pair    n/5  <evidence>
Form    n/5  <character counts; evidence>
Changes, most valuable first:
1. <change> (<which score it lifts>)
Verdict: ship | fix | redo

After the candidates for one talk: Pick, the pair you would publish, with any edit you would make to it, written out in full and backed by timestamps. You may write a better pair than any you were given; it must pass your own fact-check.

After the last talk, when you reviewed more than one: Patterns, faults that recur across the set, with counts, and whether titles within an event can be told apart.

Individual skills in this repo

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

Related Skills