ericrisco/rsc-harness / skills/youtube-packaging
youtube-packaging
VerifiedUse when writing or fixing the text that ships with a YouTube upload — title, description, tags, hashtags and chapters — when click-through is weak and the words are the suspect, or when closing the loop on what last performed. NOT designing the thumbnail image (that is `youtube-thumbnails`), NOT inventing the idea or angle (that is `youtube-ideation`), NOT the channel growth plan (that is `youtube-strategy`), NOT pushing the fields via the Data API (that is `youtube-api`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 3.1 KB |
| references/description-and-chapters.md | markdown | 7.2 KB |
| scripts/verify.shexecutable | script | 9.6 KB |
evals/README.md
View on GitHub# Evals — youtube-packaging
These cases are read by the repo's skill-eval harness. `should_trigger` and
`should_not_trigger` check routing precision: each prompt is matched against this
skill's description versus its siblings, and the `route_to` ids
(`youtube-thumbnails`, `youtube-ideation`, `youtube-api`, `youtube-strategy`,
`seo-geo`) must win their own cases — the thumbnail, the idea, the API call, the
channel plan, and non-YouTube SEO all belong elsewhere. The `capability` case is
scored by a judge against its `must_include` rubric: it checks that a generated
package grounds in `02-DOCS` first, emits a 2-3 title A/B set within the char
budget, an above-the-fold description line plus a natural ~200-350 word body and a
3-5 hashtag line, chapters obeying all four rules, 5-8 tags with the right first
tag, a feedback-log update, correct handoffs, and the watched-time-per-impression
framing. Run them through the repo's eval runner; no live YouTube account, upload,
or network access is required — the capability run is a dry-run producing text
artifacts and a feedback-log row only.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |