{"id":70663,"plugin_id":"plugins_6ae2cf5ebfac8191aae15710d22d105b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:08:06.182Z","digest":"fc0b2622877b28e080d0e216065379a135fa175704144ccaa163fc9fc1bc92e3","against":null,"payload":{"description":"Plan a week or a month of YouTube uploads - what to post, when, and in what order, sized to the creator's actual capacity. Use for \"plan my week\", \"content calendar\", \"what should I post\", \"I have no idea what to make next\".","included_files":[],"name":"yt-plan","skill_md_contents":"---\nname: yt-plan\ndescription: >-\n  Plan a week or a month of YouTube uploads - what to post, when, and in\n  what order, sized to the creator's actual capacity. Use for \"plan my\n  week\", \"content calendar\", \"what should I post\", \"I have no idea what to\n  make next\".\n---\n\n# yt-plan\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\nA plan that does not fit the week is a list of regrets. Ask two questions before writing anything:\n**how many hours do you actually have**, and **what is already half-made**.\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## The shape of a week\n\n- **One anchor.** The video the week is for. It gets the most time and it goes out on the day the\n  channel's own analytics say is best - ask for that, do not assume Tuesday.\n- **One cheap one.** Built from something that exists: a clip, a reaction, a follow-up to the\n  comment that got the most replies last week.\n- **Shorts from the anchor.** Three, cut from the long video, not written separately. `/yt-shorts`\n  finds them.\n\nThree uploads on a seven-day week, not seven. A plan that posts daily is not a plan anyone\nrecognises, and the empty days are what make the filled ones survive a bad week.\n\n## What to hand back\n\nA table: day, format, working title, the one sentence it promises, and what already exists for it.\nThen the honest line at the bottom - how many hours this costs, and what to drop first if the week\ngoes wrong.\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":{}}