[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV6MD26FCMMKAF9TP48MX8":3,"skill-same:01M7EV6MD26FCMMKAF9TP48MX8":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EV6MD26FCMMKAF9TP48MX8","check-youtube-description",null,"Check a proposed YouTube video description against the API's hard limits and against rules that keep it trustworthy, before it is uploaded. Use after drafting or generating a description and before publishing it.","tdupu\u002Fagent-skills-public","tdupu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3440403?v=4","01M7EV32X9J0EFE5T4P8TKQTCQ","Taylor Dupuy","01M7EV32XZ1Z4MDBYAFRCJD3BP",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fcheck-youtube-description\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: check-youtube-description\ndescription: >-\n  Check a proposed YouTube video description against the API's hard limits and\n  against rules that keep it trustworthy, before it is uploaded. Use after\n  drafting or generating a description and before publishing it.\n---\n\n# Check a description before it ships\n\nA description is rejected, silently truncated, or quietly ineffective for\nreasons that are easy to miss while composing it. This checks those and fails\nloudly, so the problem is caught locally rather than by an API error or by a\nreader.\n\nRun it on the exact bytes that will be uploaded. Note that most editors append\na trailing newline, which counts.\n\nExit status: `0` clean, `1` a description failure, `2` an input error (missing,\nunreadable, a directory, or not UTF-8), so a bad path is distinguishable from a\nbad description.\n\n## The hard limits\n\n| Rule | Why |\n|---|---|\n| **5000 bytes** | Not characters. Every `—`, `≅`, `ℚ`, `ε` costs 2-3 bytes, so a 4980-character description can be 5589 bytes and be refused |\n| No `\u003C` or `>` | The field forbids them and the update is rejected whole as `invalidDescription`; the message names no character. For an inequality, write it out or use a Unicode form |\n| No control or invisible characters | Zero-width spaces, non-breaking spaces, BOM and bidi overrides survive the round trip and are invisible while they break things |\n| At most 60 hashtags | Past that every hashtag on the video is ignored, and over-tagging risks removal. The platform counts the title's hashtags too; this sees only the description, so it can undercount |\n\nSources, checked 2026-09-27: `developers.google.com\u002Fyoutube\u002Fv3\u002Fdocs\u002Fvideos`\n(description: 5000 bytes, no `\u003C` or `>`),\n`...\u002Fvideos\u002Fupdate` (`invalidDescription`),\n`support.google.com\u002Fyoutube\u002Fanswer\u002F9884579` (chapters),\n`support.google.com\u002Fyoutube\u002Fanswer\u002F6390658` (hashtags). That `\u003C` specifically\ntriggers `invalidDescription` is an inference joining the field spec to the\nerror list; the docs do not say so in one place.\n\n## Chapters, if present\n\nChapters activate only if **all** of these hold, and fail as a group otherwise:\n\n1. the first timestamp is `0:00` (the docs write `00:00`),\n2. at least three timestamps, in ascending order,\n3. every chapter is at least ten seconds, including the last,\n4. each timestamp has a title, on the same line.\n\nConditions 1-3 are stated verbatim in the support article. **Condition 4 and\nthe rule that a timestamp is read only at the start of a line are inference**:\nthe article says to add \"a list of timestamps and titles\" and is silent on\nlayout. They are enforced here because the observed convention is\ntimestamp-first, but treat them as less certain than 1-3.\n\nA line whose timestamp comes *after* its label, such as `Intro - 0:00`, is\nreported - whether or not a chapter block is also present. Ordinary prose\ncontaining a clock time is not: the rule only fires on a line that is a label\nand a timestamp and nothing else.\n\nThe final chapter and a timestamp past the end of the video can only be checked\nif you pass `--duration SECONDS`. Without it, both go unchecked.\n\n## The trust rules\n\nNot platform rules - what keeps a description honest.\n\n- **Unverified-citation markers** (`PENDING VERIFICATION`, `TODO`, `TBD`,\n  `[cite]`) are refused. This catches text that self-incriminates; it cannot detect an\n  unverified citation that simply looks confident. `--allow-pending` permits\n  legitimate prose like \"next date: TBD\".\n- **Links** are parsed, and duplicates are detected after normalising scheme\n  and trailing slash. A link ending in punctuation is flagged as malformed.\n- **Attribution**: `--require-attribution` fails unless the text says it was\n  generated automatically. It is a keyword match, so it confirms a statement\n  exists, not that the statement is accurate.\n- **Referenced videos** must be in `--known-ids` when that is supplied; without\n  it the rule is inert. the `youtu.be`, `watch?v=`, `shorts`, `live` and\n  `embed` URL forms are recognised.\n\n## Procedure\n\n1. Write the description to a file, exactly as it will be uploaded.\n2. `scripts\u002Fcheck-description.py --file DESC.txt [--duration S]\n   [--known-ids IDS.txt] [--require-attribution] [--allow-pending]\n   [--max-bytes N]` - paths are relative to this skill directory.\n3. Fix what it reports and re-run until the exit status is 0.\n4. `correct-youtube-description` is the *builder* that produces the file and\n   then calls this checker; it is not a downstream step. Use it to assemble the\n   description in the first place.\n\nTests: `python3 tests\u002Ftest_check_description.py`.\n\n## Limitations\n\n- It checks link *form*, not whether a link resolves. That needs a network call\n  the caller should make deliberately.\n- It cannot judge whether a citation is correct, only whether the text admits\n  to being unverified.\n- Platform rules change. The sources above are dated; re-check them.\n","# Check a description before it ships\n\nA description is rejected, silently truncated, or quietly ineffective for\nreasons that are easy to miss while composing it. This checks those and fails\nloudly, so the problem is caught locally rather than by an API error or by a\nreader.\n\nRun it on the exact bytes that will be uploaded. Note that most editors append\na trailing newline, which counts.\n\nExit status: `0` clean, `1` a description failure, `2` an input error (missing,\nunreadable, a directory, or not UTF-8), so a bad path is distinguishable from a\nbad description.\n\n## The hard limits\n\n| Rule | Why |\n|---|---|\n| **5000 bytes** | Not characters. Every `—`, `≅`, `ℚ`, `ε` costs 2-3 bytes, so a 4980-character description can be 5589 bytes and be refused |\n| No `\u003C` or `>` | The field forbids them and the update is rejected whole as `invalidDescription`; the message names no character. For an inequality, write it out or use a Unicode form |\n| No control or invisible characters | Zero-width spaces, non-breaking spaces, BOM and bidi overrides survive the round trip and are invisible while they break things |\n| At most 60 hashtags | Past that every hashtag on the video is ignored, and over-tagging risks removal. The platform counts the title's hashtags too; this sees only the description, so it can undercount |\n\nSources, checked 2026-09-27: `developers.google.com\u002Fyoutube\u002Fv3\u002Fdocs\u002Fvideos`\n(description: 5000 bytes, no `\u003C` or `>`),\n`...\u002Fvideos\u002Fupdate` (`invalidDescription`),\n`support.google.com\u002Fyoutube\u002Fanswer\u002F9884579` (chapters),\n`support.google.com\u002Fyoutube\u002Fanswer\u002F6390658` (hashtags). That `\u003C` specifically\ntriggers `invalidDescription` is an inference joining the field spec to the\nerror list; the docs do not say so in one place.\n\n## Chapters, if present\n\nChapters activate only if **all** of these hold, and fail as a group otherwise:\n\n1. the first timestamp is `0:00` (the docs write `00:00`),\n2. at least three timestamps, in ascending order,\n3. every chapter is at least ten seconds, including the last,\n4. each timestamp has a title, on the same line.\n\nConditions 1-3 are stated verbatim in the support article. **Condition 4 and\nthe rule that a timestamp is read only at the start of a line are inference**:\nthe article says to add \"a list of timestamps and titles\" and is silent on\nlayout. They are enforced here because the observed convention is\ntimestamp-first, but treat them as less certain than 1-3.\n\nA line whose timestamp comes *after* its label, such as `Intro - 0:00`, is\nreported - whether or not a chapter block is also present. Ordinary prose\ncontaining a clock time is not: the rule only fires on a line that is a label\nand a timestamp and nothing else.\n\nThe final chapter and a timestamp past the end of the video can only be checked\nif you pass `--duration SECONDS`. Without it, both go unchecked.\n\n## The trust rules\n\nNot platform rules - what keeps a description honest.\n\n- **Unverified-citation markers** (`PENDING VERIFICATION`, `TODO`, `TBD`,\n  `[cite]`) are refused. This catches text that self-incriminates; it cannot detect an\n  unverified citation that simply looks confident. `--allow-pending` permits\n  legitimate prose like \"next date: TBD\".\n- **Links** are parsed, and duplicates are detected after normalising scheme\n  and trailing slash. A link ending in punctuation is flagged as malformed.\n- **Attribution**: `--require-attribution` fails unless the text says it was\n  generated automatically. It is a keyword match, so it confirms a statement\n  exists, not that the statement is accurate.\n- **Referenced videos** must be in `--known-ids` when that is supplied; without\n  it the rule is inert. the `youtu.be`, `watch?v=`, `shorts`, `live` and\n  `embed` URL forms are recognised.\n\n## Procedure\n\n1. Write the description to a file, exactly as it will be uploaded.\n2. `scripts\u002Fcheck-description.py --file DESC.txt [--duration S]\n   [--known-ids IDS.txt] [--require-attribution] [--allow-pending]\n   [--max-bytes N]` - paths are relative to this skill directory.\n3. Fix what it reports and re-run until the exit status is 0.\n4. `correct-youtube-description` is the *builder* that produces the file and\n   then calls this checker; it is not a downstream step. Use it to assemble the\n   description in the first place.\n\nTests: `python3 tests\u002Ftest_check_description.py`.\n\n## Limitations\n\n- It checks link *form*, not whether a link resolves. That needs a network call\n  the caller should make deliberately.\n- It cannot judge whether a citation is correct, only whether the text admits\n  to being unverified.\n- Platform rules change. The sources above are dated; re-check them.\n",{"name":5,"description":7},"main","8d13efb5e66306aeae6e3b948bc463e7e2db1b65","skills\u002Fcheck-youtube-description","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public","https:\u002F\u002Fgithub.com\u002Ftdupu","https:\u002F\u002Ftdupu.github.io\u002Findex.html","Associate Professor, Department of Mathematics and Statistics, University of Vermont --- last updated Fall 2019","2026-11-13 09:07:19",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tdupu\u002Fagent-skills-public --skill check-youtube-description",{"tool":38,"command":39},"bunx","bunx skills add tdupu\u002Fagent-skills-public --skill check-youtube-description",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tdupu\u002Fagent-skills-public --skill check-youtube-description","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fcheck-youtube-description\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"scripts\u002Fcheck-description.py","SCRIPT","脚本",9138,"https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fcheck-youtube-description\u002Fscripts\u002Fcheck-description.py",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"tests\u002Ftest_check_description.py",5760,"https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fskills\u002Fcheck-youtube-description\u002Ftests\u002Ftest_check_description.py",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EW4PT586KKE7VRCAD80Z9K","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EW4HV5V74AF3PTV8N4T0PS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EW4DNKGP5CR1RAJP2J9PHA","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EW4BA2QP88VBFVXDVJM7XQ","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EW47F2JG5FBESDJNP3PKMV","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7EW44N8556Y556NX9HJT4KP","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Ftdupu\u002Fagent-skills-public\u002Fblob\u002Fmain\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]