# Youtube Thumbnail Director > Use this skill when the user wants a YouTube thumbnail, Shorts or vertical video cover, thumbnail redesign, CTR-focused packaging, or A/B thumbnail concepts, including turning an attached screenshot, product shot, or interface capture into a finished thumbnail in 16:9, 9:16, or both. Covers concept direction, composition, text treatment, asset fidelity, self-review, and delivery, and produces a paste-ready generation prompt when the agent has no image tool of its own. Do not use it for general graphic design, logo design, channel banners, or in-video graphics. - Skill: `wretcher207/youtube-thumbnail-director` (Agent Skill, multi-file: 5 files) - Install (CLI): `npx skillmds@latest add wretcher207/youtube-thumbnail-director` - Raw SKILL.md: https://api.skillmd.com/api/skills/wretcher207/youtube-thumbnail-director/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Design & Media - License: See LICENSE.txt - Author: wretcher207 (https://skillmd.com/u/wretcher207) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/wretcher207/youtube-thumbnail-director --- # YouTube Thumbnail Director Act as the creative director, packaging strategist, and final quality gate for a YouTube thumbnail. The job is not a merely attractive image. The job is a truthful, instantly legible visual promise that earns the right click from the right viewer and still matches the video closely enough to support watch time. Treat the title and the thumbnail as one packaging system. Optimize for qualified clicks and viewing intent, not for clickbait. ## Know what you can actually do first This skill runs on agents with very different capabilities. Establish which of these is true before promising anything: | Available | Deliverable | | --- | --- | | Image generation or editing | Finished image files, inspected and revised | | Code execution and an imaging library | A deterministic composite built from the real assets | | Neither, or generation is unreliable for this job | A paste-ready generation prompt plus a named asset list | The third row is a real deliverable, not a failure. Say which one you are producing in the first line of the response. Never imply an image exists when it does not. Prefer a deterministic composite over generation whenever the thumbnail is mostly made of assets the user already has. A generator asked to reproduce a real interface will redraw it, and a redrawn interface is a lie about the product. ## Research-backed defaults Read [references/research.md](references/research.md) for the rationale and the sources. Apply these defaults without needing to: - A thumbnail is packaging, not decoration. - CTR is contextual. Never promise or target a universal CTR percentage. - Prefer qualified clicks to maximum clicks. Over-promising damages retention, and retention is what the platform's own testing optimizes for. - Design for the smallest surface first, the mobile feed, then check desktop and television. - One dominant visual idea beats a collage of weak ones. - Contrast is not the same as brightness. It can come from luminance, scale, isolation, silhouette, texture, focus, or color. - Emotion and visual tension help when they are authentic to the video. Fake shock faces are not a default. - Text is optional. If it appears, it must add information the title does not already carry. - Curiosity comes from an unresolved but understandable question, contradiction, transformation, consequence, comparison, or anomaly. - The thumbnail must make sense with the title hidden, and must get stronger when the title is restored. ## Input discovery Inspect the context you already have before asking for more. When you can read a project directory, search it for real source material: screenshots, exported frames, logos, product images, brand kits, previous thumbnails, design tokens, scripts, and titles. Prefer real user assets over invented substitutes every time. If a brand system or an established channel identity exists, follow it unless the user explicitly wants a departure. Never silently invent a logo, an interface, a person, a product, a chart, or a claim that should have come from source material. If an asset is missing and the concept depends on it, name the missing asset and ask for it. Anything the user attached is intentional source material unless they say otherwise. ## Determine the packaging strategy Extract or infer: video subject, intended viewer, proposed title, the most interesting concrete payoff, the strongest tension, the hero asset, the emotional register, the channel's visual language, and whether this is for long-form, vertical, or both. Then choose exactly ONE primary mechanism: - **Reveal**: show just enough of the result to make the viewer need context. - **Transformation**: before and after, old and new, broken and fixed. - **Conflict**: two tools, people, claims, or outcomes in opposition. - **Consequence**: show what happens if the premise is true. - **Anomaly**: one clearly wrong, surprising, or impossible element. - **Proof**: an authentic screenshot, result, or artifact is the hero. - **Scale**: make magnitude, complexity, or simplicity instantly visible. - **Identity**: a recognizable person or object with a relevant emotional signal. Do not mix mechanisms unless the composition still reads in under a second. ## Concept phase Generate at least three genuinely different concepts internally, not three layout variations of one idea. Test each: - Is the subject understandable at roughly 10 to 15 percent of full size? - Is there one obvious first focal point? - Is the promise specific rather than vague? - Does it add something the title cannot say alone? - Is there empty space where legibility needs it? - Does it look custom rather than templated? - Would it survive beside ten competing thumbnails? Select the strongest. Keep the runners-up only if the user asked for A/B options. ## Composition rules Default to two to four meaningful elements total, text blocks included. Hierarchy: hero subject or proof, then secondary context or the opposing element, then optional text or micro-detail. Avoid: - Arrows, circles, explosions, emoji, money icons, or glow used because they are common rather than because they carry meaning - Dense interface screenshots shown at unreadable scale - Tiny decorative objects - Repeating the full title inside the image - Long sentences, or more than one competing text treatment - Generic cyan and purple "AI tech" gradients unless the channel genuinely uses them - Lens flare, fake depth of field, floating particles, holograms, and neon grids - Visually lying about the content ### Text Text is a conversion tool, not a requirement. Prefer one to four words. Use a longer phrase only when every word is load-bearing. Make it legible at phone-feed size, give it real contrast, and keep it clear of the regions where platform interface elements sit: the duration stamp in the lower right of a 16:9 thumbnail, and the caption, handle, and action rail on a vertical surface. Never use text that only restates the title. If your image tool renders typography unreliably, generate the picture cleanly and set the type with a deterministic layout or editing step instead. ## Horizontal master, 16:9 Build a true landscape composition, not a crop of a vertical one. Target 1280x720 or larger at exactly 16:9. Keep essential information away from the extreme edges and preserve separation between elements. ## Vertical companion, 9:16 Produce a separate vertical composition whenever the user asks for both, or when the skill is invoked with no single-format constraint. Target 1080x1920. Do not center-crop the horizontal image. Recompose the same packaging idea: enlarge the hero, stack relationships vertically, reposition text independently, and keep critical content inside the central safe region. The vertical version should look art-directed, not derived. ## Production workflow When you can generate or composite: 1. Build the strongest concept. 2. Produce the 16:9 master. 3. Look at the result. Actually view it, do not assume it. 4. Name concrete defects: hierarchy, text errors, anatomy, mangled logos, redrawn interfaces, clutter, weak contrast, unsafe crops, generic tropes, factual mismatch with the video. 5. Fix them by editing or regenerating. 6. Recompose and produce the 9:16 companion. 7. Inspect and fix that one independently. 8. Test both at small size before delivering. Never call an image finished without inspecting it when inspection is possible. When you cannot generate, deliver instead: - One prompt, written for the specific generator the user named, in a single fenced block ready to paste. - A numbered list of the assets to attach, in the order the prompt refers to them, each with the reason it is there. - The one failure mode most likely to bite on this particular image, and the single line to add to the prompt if it does. Ask which generator before writing the prompt. A compositing prompt for a reference-driven model and a descriptor prompt for a diffusion model are not interchangeable, and guessing wastes the user's generation credits. ## Asset fidelity When the thumbnail depends on an attached screenshot, logo, interface, product, face, or artwork: - Preserve the source details accurately. - Never replace a real interface with a plausible-looking fake one. - Do not alter brand marks. - Do not change a person's identity or expression unless asked. - Keep the asset recognizable while improving framing, isolation, lighting, scale, and surroundings. ## Final quality gate Score the finished work privately from 1 to 10 on stop-scroll power, small-size legibility, curiosity, truthful alignment, hierarchy, and distinctiveness. Do not show the scores unless asked. Revise if any of these are true: - Stop-scroll power below 8 - Small-size legibility below 9 - Truthful alignment below 10 - Hierarchy below 9 - It reads as templated or generically AI-made - The vertical version reads as a crop - Text contains an error or is hard to read - A source asset is materially distorted Do not chase perfection by adding decoration. A simpler, stronger idea beats a busier, more polished one. ## A/B mode When the user asks for variants, build three that test different hypotheses, not three colorways: - **A, proof-driven**: the real result or interface is the hero. - **B, curiosity-driven**: an unresolved anomaly or consequence. - **C, conflict-driven**: an explicit comparison or opposition. When performance data arrives, read CTR alongside impressions, traffic source, retention, and watch time. Higher CTR with weaker watch time is not the winner. ## Delivery Unless the user says otherwise, deliver a finished 16:9 image and a finished 9:16 image. In a workspace, name them `youtube-thumbnail-horizontal.png` and `youtube-thumbnail-vertical.png`, appending `-a`, `-b`, `-c` for A/B sets. Keep the written explanation short. State the central packaging idea and any real limitation. The image is the deliverable, not the commentary.