{"id":70660,"plugin_id":"plugins_6ae2cf5ebfac8191aae15710d22d105b","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:08:06.127Z","digest":"49bdd2bd0334686f8fc8f7afc93ee4161a9bc76041443e6c2c138a724539f7f4","against":null,"payload":{"description":"Draft replies to YouTube comments in the creator's voice, triaged by which ones are worth answering. Use for \"reply to my comments\", \"handle the comment section\", \"someone asked X\", or a pasted comment thread.","included_files":[],"name":"yt-comment","skill_md_contents":"---\nname: yt-comment\ndescription: >-\n  Draft replies to YouTube comments in the creator's voice, triaged by which\n  ones are worth answering. Use for \"reply to my comments\", \"handle the\n  comment section\", \"someone asked X\", or a pasted comment thread.\n---\n\n# yt-comment\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\nThe comment section is a retention surface, not a chore. Replies in the first few hours are what\ndecide whether a thread becomes a conversation other people read.\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## Triage first, always\n\nSort what the user pastes into four piles and say how many are in each before writing anything:\n\n1. **Questions** - answer them. These are your next video's topics, so note the repeats.\n2. **Corrections** - if they are right, say so plainly and thank them. Never argue a fact you\n   cannot check.\n3. **Praise** - reply to a few, briefly, with something specific from their comment. A wall of\n   identical \"thank you!\" replies reads as automated because it is.\n4. **Bait** - do not reply. Say so and move on. Never write a comeback, however deserved.\n\n## Writing the reply\n\n- Under 30 words. A long reply in a comment thread is a blog post nobody asked for.\n- Answer the actual question in the first sentence.\n- One question back, only when it is real.\n- No emoji unless the user's own replies use them. Check their voice file.\n- Never promise a video you have not agreed to make.\n\n## The heart and the pin\n\nSay which ONE comment to pin and why. Pin the question the most people also have, not the nicest\none. Heart generously - it costs nothing and it is visible.\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":{}}