agentleFS
lorena-bordonaba-paulorena-bordonaba-pau/youtube-agent/.claude/skills/packaging/SKILL.md

packaging

Skill2 starsChanged 47 days agoMITView on GitHub

A video's titles, thumbnail and description, scored with the channel's calibrated rubric. Triggered by "give me titles", "score this title", "review my thumbnail", "improve the packaging". In Spanish, "dame títulos", "puntúa este título", "revisa mi miniatura", "mejora el packaging".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not chase the score: If an honest title scores 78 and an exaggerated one scores 95, recommend the 78 and say why.

    line 23
  2. Distinctive:

    Look at how the niche's live outliers are titling right now.

    line 44
  3. Very specific:

    Check that title and thumbnail are not communicating the same concept.

    line 65
  4. Distinctive:

    Never say a title "is going to work".

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Packaging: titles and thumbnails

WHEN

Generating or evaluating titles, diagnosing a thumbnail, reviewing the title+thumbnail pair, writing the description and tags.

EXECUTION ORDER

  1. Score the titles — mandatory, never opine first python3 tools/score_titles.py --title "A || B || C" Returns 0-100 with a per-axis breakdown and the memory justifying each point. It is heuristic: you must declare it is an own rubric, not a CTR prediction, and that it is unvalidated until the Studio CSV is ingested.

1b. Two rules about the number, before you look at it

Do not chase the score. If an honest title scores 78 and an exaggerated one scores 95, recommend the 78 and say why. The rubric measures resemblance to what worked, not whether the title is true; well-built clickbait scores high and damages the channel.

Scores are only comparable within the same call. Score the current title ALONGSIDE the candidates, in one run (--title "current || A || B || C"). Comparing today's number with another session's is not valid. And only propose a candidate that beats the current one strictly: a tie is not an improvement.

  1. Demand backing
    python3 tools/yt_search_terms.py --days 90        # REAL demand, first
    python3 tools/kw_research.py --kw "candidate 1; candidate 2"
    The first one wins: those are terms people already reached the channel with. The second is a proxy and only ranks candidates against each other.
  2. Real references, not intuition python3 tools/yt_outliers_channels.py --min-ratio 2.5 Look at how the niche's live outliers are titling right now.
  3. The thumbnail
    python3 tools/yt_thumbnails.py --video ID
    python3 tools/score_thumbnail.py --video ID --title "the chosen title"
    score_thumbnail only scores the automatic 40%. It returns the other 60% as unanswered questions, and you must answer them by opening the JPG with vision. Inventing that 60% is the failure this tool is designed to prevent.
  4. If the thumbnail has to be CREATED, not just judged This skill scores what exists. To generate it: image-generation-core (base rules) + thumbnail-best-practices (design), and likeness-preservation if a face appears. If there is a specific reference to work from, thumbnail-inspiration. A generated image comes back as source: generated: you cannot score it and then present that score as a CTR forecast.
  5. Anti-redundancy contrast — the step most often skipped Check that title and thumbnail are not communicating the same concept. If the hard number is in the title, the thumbnail shows the visual result. If memory/sop/niche_bend_sop.md exists, its lessons outrank any general rule.

SOURCES

Steps 1 and 2b heuristic — always declare it. Step 2a youtube_api. Steps 3 and 4a derived. Step 4b is mixed: derived in the pixels, the agent's judgement for the rest.

OUTPUT

  1. The titles ranked by score, with the per-axis breakdown.
  2. One line per title explaining which axis lifts or sinks it, citing the memory.
  3. The thumbnail diagnosis with the judgement axes already answered after looking at the image.
  4. The title-thumbnail contrast: which angle each one covers.

Never say a title "is going to work". Say which real video it resembles, and why.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.