{"id":70658,"plugin_id":"plugins_6ae2cf5ebfac8191aae15710d22d105b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:08:06.078Z","digest":"a45c8080cc6ac6d7c97cdd3dc6d793e79de0d9eda69c58b3cf580ffb9da369a4","against":null,"payload":{"description":"Audit a YouTube channel end to end - packaging, consistency, the first fifteen seconds, and what to fix first. Use for \"audit my channel\", \"why isn't my channel growing\", \"review my videos\", or a pasted channel URL.","included_files":[],"name":"yt-audit","skill_md_contents":"---\nname: yt-audit\ndescription: >-\n  Audit a YouTube channel end to end - packaging, consistency, the first\n  fifteen seconds, and what to fix first. Use for \"audit my channel\", \"why\n  isn't my channel growing\", \"review my videos\", or a pasted channel URL.\n---\n\n# yt-audit\n\nUse scripts relative to this skill directory, not the user’s working directory. If local execution or inputs are unavailable, explain the limitation and provide a clearly labeled manual alternative; do not claim a tool ran. Scores and thresholds are heuristics, not guarantees or causal proof. Use only accessible or user-provided data; never invent analytics.\n\nAn audit that lists twenty problems is a way of avoiding the one that matters. This ends in ONE fix.\n\n## Before you write\n\n1. Use a voice profile or samples the user provides; otherwise ask for a short style description and continue with stated assumptions. Save a profile only when the user requests it.\n2. Never invent a number, a result or a source. If a figure would strengthen it and you do not have\n   one, ask for it or write the line without it.\n\n## What to look at, in this order\n\n1. **The last ten titles, as a set.** Read them as a list, the way the channel page shows them. Do\n   they promise different things? Run them through `../yt-package/title.py`. A channel where every\n   title is the same shape has a format problem, not a title problem.\n2. **The thumbnails, at feed size.** Shrink them. What survives? If three of them are unreadable at\n   that size, that is the fix and nothing else matters yet.\n3. **The first fifteen seconds of the three most recent.** Transcribe them and score with\n   `../yt-script/hookscore.py`. This is where most channels lose.\n4. **Upload rhythm.** Not frequency - CONSISTENCY. Six videos in one week and then nothing for a\n   month is worse than one a fortnight forever.\n5. **The retention shape**, if they can export it. `/yt-retention`.\n\n## What to hand back\n\n- The single biggest fix, named, with what to do this week.\n- Three things that are already working, so they do not break them. Be specific; \"your energy is\n  good\" is not an observation.\n- What NOT to do yet, and why.\n\nNever open an audit with praise you do not mean, and never end one with a list of twenty things.\n\n## The gate\n\nNothing here publishes. This skill writes and you publish. Every output ends in a block the user\ncopies, and the last line of every run is the question: **ship it, or change it?**\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}