Agent skill

Youtube Packaging

by hassancs91 in hassancs91/claude-youtube-editor

Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the…

MITAuto-check passedMedia & Creative

Install Youtube Packaging

skills CLI
$ npx skills add hassancs91/claude-youtube-editor --skill youtube-packaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hassancs91/claude-youtube-editor youtube-packaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hassancs91/claude-youtube-editor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/packaging .claude/skills/youtube-packaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
youtube-packaging
GitHub stars
328
Token cost
~3.7k tokens
SKILL.md length
2,098 words
Files
3 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the…

  • Works in 5 steps: Intake → Ceiling + promise (checkpoint before… → Generate the packaging → …
  • Include how would you package this
  • SKILL.md covers Where these rules come from,…, The core model — read this first, The flow and Title Checklist, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Youtube Packaging is an agent skill from hassancs91/claude-youtube-editor. Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the thumbnails as real images. Use this whenever you want to package a long-form video or turn a video idea into titles and thumbnails. Triggers include how would you package this, title ideas for, thumbnail concept, package this video, A/B variations, and make this clickable. Calibrates to your channel's own CTR data if you…

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/channel-calibration.md` and `references/thumbnail-generation.md`).

It sits in Media & Creative, covering Video scripts and shorts, Copywriting and Video production. It works with YouTube. The repository describes itself as: Record the talking head, Claude Code does the rest: the cut, the visuals, the voice, the sound effects, the thumbnail, and the YouTube upload. Every screen moment is built as… The licence is MIT.

When your agent uses it

  • Include how would you package this
  • Title ideas for
  • Thumbnail concept
  • Package this video

Example prompts

  • “Use the youtube-packaging skill to generate click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's…”
  • “/youtube-packaging”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Intake
  2. Ceiling + promise (checkpoint before generating)
  3. Generate the packaging
  4. Refine
  5. Render the thumbnails (Nano Banana Pro)

What it can do on your machine

Read from SKILL.md and the folder at commit a6ac742. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Youtube Packaging loads about 3.7k tokens when it runs, and up to ~8.3k if it reads all its reference files. Until then it costs about 151 tokens; SKILL.md has 2,098 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~151
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hassancs91/claude-youtube-editor at commit a6ac742, republished under its MIT licence (© hassancs91). 2,098 words, ~3,688 tokens.

Download SKILL.mdSave it as .claude/skills/youtube-packaging/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
youtube-packaging
description
Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the thumbnails as real images. Use this whenever you want to package a long-form video or turn a video idea into titles and thumbnails. Triggers include how would you package this, title ideas for, thumbnail concept, package this video, A/B variations, and make this clickable. Calibrates to your channel's own CTR data if you have it. Long-form only, never Shorts. Not for non-YouTube copywriting.

YouTube Packaging (Title + Thumbnail)

Turns a video idea into one locked title + 3 distinct thumbnail bets built for YouTube's native A/B/C thumbnail test, plus one value-forward description — then renders the three thumbnails as real images with Nano Banana Pro.

The whole skill optimizes for one number: CTR (click-through rate). It's the metric YouTube Studio reports per thumbnail, and the only one that isolates packaging from topic and algorithm.

Where these rules come from, and what to do about it

The rules below are not generic YouTube advice — they were derived from Studio CTR data across 20 long-form videos on a real ~1M-subscriber beginner/AI channel, read in CTR order. That dataset isn't shipped (it's another channel's numbers, and its absolutes wouldn't transfer). The patterns do transfer, and they're a much better prior than guessing.

But an inherited rule is a bet, not a fact — about YOUR audience. So:

  • Cold start (no channel data yet). Use these rules as-is. Say so when you package: "these are uncalibrated defaults — your own CTR data will beat them." Then tell the creator to start logging CTR from video 1.
  • Calibrated (~10+ long-form videos with CTR). Run references/channel-calibration.md first, then follow that file's numbers wherever it disagrees with this one. Their data wins over anything written here.

Ask which mode you're in if it isn't obvious. Never quote a target CTR the creator hasn't measured.

The core model — read this first

Views = Reach × CTR. Two different levers, driven by two different things.

  • Reach (how many people YouTube serves it to) comes from the topic and from riding known discovery waves — a tool everyone's searching, a real news moment, a broad money/free promise. Packaging cannot fix a low-ceiling topic.
  • CTR comes from packaging craft — concrete promise, magnet word, barrier-drop, one bold thumbnail hook. This is the only lever this skill controls.

Good packaging on a narrow topic produces good CTR and low views. That is correct behavior, not a packaging failure. Never blame a title when CTR is healthy and views are small — and never expect a title to rescue a topic nobody wants.

The one guardrail that stops this becoming hollow clickbait: the promise must be one the video actually keeps. Overpromise → the viewer bounces in 30 seconds → retention craters → YouTube chokes the exact reach you were chasing. The widest promise that also holds is what makes YouTube widen distribution. Reality beats expectations.

The flow

Run it in order. Stages 1–2 are fast; the value is getting the promise right before generating, because a wrong promise wastes all three bets.


Stage 1 — Intake

Ask in one message:

  1. Core idea — what's the video about / the rabbit hole.
  2. The concrete takeaway — the one clear thing the viewer walks away with. This becomes the promise. If you can't say it in a sentence, the packaging will be vague — push to name it.
  3. Audience — who clicks this: beginners, practitioners, or a mixed/wide audience? This sets how much jargon a title can carry. (A wide/beginner channel should package for the widest clickable promise and do its segmentation inside the video, never by narrowing the title.)
  4. Locked angle or term? — any angle already committed to, especially a coined/branded phrase.
  5. Conversion target — what the video pitches (a course, a tool, a repo, a newsletter, nothing). Needed for the description. "Nothing" is a valid answer.
  6. Channel data? — do they have ~10+ long-form videos with Studio CTR? Sets calibrated vs cold start. If calibrated and references/channel-calibration.md is still empty, offer to run it first.

Stage 2 — Ceiling + promise (checkpoint before generating)

Gate 1 — Topic ceiling. Classify honestly:

  • HIGH = broad demand riding a known wave (money / save-money, a broadly useful free capability, a major tool everyone knows).
  • NARROW = niche format, niche tool, or an insider flex.

If narrow, say so plainly and reset the view expectation before generating: packaging will still maximize CTR, but views are capped by demand. Then decide whether the topic is worth making for conversion even if reach is low. That's a real strategy, but it should be a choice.

Gate 2 — The promise. Draft the core promise as the clearest concrete takeaway, stated plainly — NOT a withheld-drama curiosity gap.

  • Spell out the takeaway: name the number, the tool, the saving, the outcome.
  • Don't withhold or moralize. "X Can Do More Than You Think" and "X Is Dead" are the classic floor.
  • If the video is built on a mechanism — an experiment, a build-off, a comparison — the lesson is the headline; the mechanism is only how the lesson surfaces. Never lead with the mechanism.

CHECKPOINT: State the ceiling classification and the one-line promise. Confirm or fix the promise before generating. Do not skip — three bets off a wrong promise is wasted work.


Stage 3 — Generate the packaging

Structure this correctly, it's the thing people get wrong: YouTube's Test & Compare is thumbnail-only. The title is FIXED across all three variants. So the deliverable is ONE primary title × 3 thumbnail bets, not 3 independent title+thumbnail pairs.

First, lock ONE title. It must pass most of the Title Checklist below. Output with it:

  • Implied expectation — one line: what the viewer expects walking in. The intro must pay this off. Carry it into the script.

Then 3 thumbnail bets under that fixed title. Each pulls a different lever, so YouTube compares real alternatives rather than three flavors of one idea. For each:

  • Thumbnail concept — composition per the Thumbnail Checklist: face + expression, the one dominant hook (word or number), color pop, any object.
  • Thumbnail text — a 1–3 word fragment that combines with the title, never repeats it.
  • Lever — which lever it tests, one line on the bet.
  • Honesty check — does this frame stay true under the fixed title, and does the video keep it? A thumbnail promising a beat the video doesn't have must be pulled or the beat must be built.

Lever menu — pick 3 different ones:

  • Magnet-word lead — Free / Unlimited / 100% / $0
  • Number/$ lead — a specific figure as the hook
  • Barrier-drop lead — for beginners / no coding / without [skill]
  • Object / curiosity-anchored lead — a tangible thing + a value contrast, or a named valuable thing the viewer wants ("the one skill")
  • News / "Now" lead — only if something genuinely changed
  • Own-term / brand-fit lead — a coined term. Lower reach (rides no wave) but strong identity — good as one of three, rarely all three.

Then close Stage 3 with:

  • One description (one per video). Save to videos/<project>/packaging/description.txt:
    1. 2-line value hook — the concrete payoff in plain words; name the specific things they'll learn (the real number, the free tool, the exact capability). The title sells the takeaway; these two lines make it specific and undeniable.
    2. CTAs — lead with the one matching the Stage 1 conversion target, then any others (repo, free resources, newsletter). If something is free, say so plainly.
    3. Timestamps / chapters — first chapter at 0:00, keyword-rich labels. Derive from the edit plan / final cut; re-confirm if the cut length changed.
    4. Short like/subscribe nudge.
  • Self-check — run the title and each thumbnail against both checklists; flag any rule bent and why it's worth it.
  • Baseline note — if calibrated, restate their measured median + stretch target. If cold start, say plainly that there's no baseline yet and this is the first data point. You may predict which bet lands highest and why — but the test decides. Never crown a winner; the deliverable is 3 worth shipping.

Stage 4 — Refine

Iterate — tighten the title, swap a lever, adjust a hook. All 3 run live in the A/B/C test, so the goal is 3 you're willing to ship, not one.


Show full SKILL.md (845 more words)Show less
Stage 5 — Render the thumbnails (Nano Banana Pro)

Turn the 3 locked concepts into actual images. The dedicated /thumbnail skill is the interactive render engine for this stage — it interviews for style elements (environment, text budget, extras) with the creator's calibrated defaults (minimal text) and owns the verify/iterate loop; use it whenever the creator is in the loop. Mechanics, prompt template, and model details live in references/thumbnail-generation.md — load it before generating. The flow:

  1. Build a prompt per concept from its Stage 3 fields using the template in the reference doc. Nano Banana Pro renders the hook word itself (deliberate), so state the exact word, spell it letter-by-letter, and forbid all other text.
  2. Generate into videos/<project>/packaging/thumbs/A|B|C.png with tools/gen_thumbnail.py, passing the media/library/faces/ kit as reference so the face stays consistent. (You supply that kit — see its README. No face kit, no face renders.)
  3. Verify every render before showing it — run the verify checklist in the reference doc (text spelled right + legible, face reads as the creator, one dominant hook, bright/saturated/positive, sane hands, 16:9 <2MB). Regenerate any that fail; only surface passes. This catches the one real risk of model-rendered text: a garbled word.
  4. Iterate — review A/B/C together; change one thing at a time, holding --seed to keep composition steady. Keep each prompt in thumbs/A.txt so refinements are diffs.
  5. Deliver the 3 finals to YouTube spec (--jpg, ≤2MB) plus prompts/seeds, so any winner is re-renderable later.

Remember the loud-vs-calm rule: the thumbnail is intentionally louder than the calm in-video brand (brand.md) — never tone it down to match. See the reference doc.


Title Checklist

A strong title passes most of these. Use as a generator and a filter.

  1. Concrete promise — quantified ($ / count) or absolute (Unlimited / 100% / Free)? Vague = dead.
  2. At least one magnet word — Free, Unlimited, 100%, Money, Easiest.
  3. Outcome-framed, not feature-framed — the viewer's gain, not what the tool does. Selling a tool's capability instead of the viewer's outcome is a reliable floor.
  4. Zero unknown / own-product names — see the self-brand rule below.
  5. Barrier-drop or authenticity rider where the topic invites skepticism — "for beginners," "no coding," "without [skill]," "(No BS)."
  6. News / "Now / New" hook if something genuinely changed — borrows the discovery wave.
  7. A specific noun, not vague curiosity — "the one skill," never "WAY more" / "you won't believe."
  8. No hot-take / "DEAD" / negative framing — make/save/build outperforms opinions. (Test this against your own data; it's one of the most channel-dependent rules here.)
  9. Leads with the takeaway, not the mechanism.

Thumbnail Checklist

Ranked by signal strength. Re-rank against your own data once calibrated.

  1. One dominant hook — never a busy frame. One magnet word OR one big number as the focal element. This is the top-tier device. The multi-logo "kill the competitors" graveyard splits attention and reliably lands only mid-tier — even when the enemy-kill works in the title, render the thumbnail as one clean hook.
  2. Lead with a number/$ when the topic has one — huge, bright. Strong but not sufficient: a number in a busy frame on a narrow topic still sinks.
  3. Big, high-energy positive face. Kill negative emotion. Wide-eyed / excited / shocked, looking at camera, large in frame. Facepalms and flat smiles are the floor.
  4. Bright saturated color pop — green (money), yellow (highlight), red (FREE). Dark and muted frames underperform.
  5. Tangible object in hand for curiosity, especially a value contrast (a small price pointing at something that looks expensive, or vice versa).
  6. No DEAD / negative framing visually — mirrors title rule 8.
  7. Thumbnail text ≠ title — a 1–3 word fragment that combines with the title, never repeats it. Title and thumbnail are two halves of one message.

Hard rules

  • Long-form only. If asked to package a Short, decline and note this skill is long-form; Shorts are a different packaging game.
  • One title, three thumbnails. Test & Compare is thumbnail-only. Never ship "3 title+thumbnail pairs" — the test can't measure that.
  • Clear takeaway over withheld drama — always. Curiosity is allowed only when anchored to a named, valuable thing ("the one skill you need"), never pure mystery.
  • The self-brand rule: unknown / own-product names stay OUT of titles. They don't kill clicks — they kill reach, because an unknown name rides no discovery wave, so YouTube serves it less. Known brands help and are fine. Own products belong in the thumbnail and the video, never the title.
  • No hot-take / "DEAD" / negative framing.
  • 3 distinct bets, never 3 flavors of one frame.
  • Never quote a CTR target the creator hasn't measured. Their median or nothing.
  • The creator's data beats this file. When references/channel-calibration.md has real numbers that contradict a rule here, the rule is wrong for that channel. Update it.

References

  • references/channel-calibration.md — how to pull your own CTR from Studio (it is not in the API), build the dataset, derive your baseline and your real levers, and reconcile them back into this file. Run it once you have ~10+ long-form videos.
  • references/thumbnail-generation.md — Stage 5 render engine: the Nano Banana Pro model/tool (tools/gen_thumbnail.py), the media/library/faces/ reference kit, the prompt template, the per-render verify loop, the loud-vs-calm brand rule, and failure-mode fixes. Load before rendering.

© hassancs91, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .claude/skills/packaging of hassancs91/claude-youtube-editor.

  • SKILL.md
  • references/channel-calibration.md
  • references/thumbnail-generation.md

Open the folder on GitHubat commit a6ac742

Compare with similar skills

Youtube Packaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Youtube Packaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Youtube Packaging this skillhassancs91/claude-youtube-editor328—~3.7kAutomated safety check: PassMIT
Short Form Scriptmohitagw15856/pm-claude-skills1.4k—~755Automated safety check: PassMIT
Youtube Viral Optimizerinfranodus/skills119—~3.6kAutomated safety check: PassNone
Video Content Strategistalirezarezvani/claude-skills28k—~2.9kAutomated safety check: PassMIT
Youtubenpc-live/clawfirm156—~1.4kAutomated safety check: PassNone
Faceless Explainer Videoheygen-com/hyperframes60k3 repos~7.7kAutomated safety check: NotesApache-2.0

Similar skills

  • Short Form Script

    mohitagw15856/pm-claude-skills

    Write a short-form video script for TikTok, Instagram Reels, or YouTube Shorts — built on the hook→retention→payoff structure that drives watch-time.

    1.4k GitHub stars~755 tokensUpdated yesterday
    Media & CreativeAuto-check passed
  • Youtube Viral Optimizer

    infranodus/skills

    Generate high-CTR YouTube thumbnails, titles, and video scripts optimized for virality.

    119 GitHub stars~3.6k tokensUpdated 20 days ago
    Media & CreativeAuto-check passed
  • Video Content Strategist

    alirezarezvani/claude-skills

    A skill your agent uses when planning video content strategy, writing video scripts, optimizing YouTube channels, building short-form video pipelines (Reels, TikTok, Shorts), or repurposing…

    28k GitHub stars~2.9k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Youtube

    npc-live/clawfirm

    YouTube 内容创作全套。包括视频标题/描述/标签写作、Shorts 文案、 社区帖子(Community Post)写作、缩略图文案策略、SEO 优化、 推荐算法适配、频道增长策略、平台合规规则。

    156 GitHub stars~1.4k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Faceless Explainer Video

    heygen-com/hyperframes

    Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.

    60k GitHub starsUsed in 3 repos~7.7k tokens
    Media & CreativeAuto-check: notes
  • Yt Dlp Downloader

    MapleShaw/yt-dlp-downloader-skill

    Download videos from YouTube, Bilibili, Twitter, and thousands of other sites using yt-dlp.

    209 GitHub starsUsed in 1 repo~1.5k tokens
    Media & CreativeAuto-check passed

More from hassancs91/claude-youtube-editor

All 8 skills in this repo
  • Youtube Thumbnail

    hassancs91/claude-youtube-editor

    Dedicated YouTube thumbnail generator — interviews you for exactly the style elements you want (environment, text budget, extras, accent color), then renders high-contrast, vibrant, face-consistent…

    328 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check: notes
  • Brand Setup

    hassancs91/claude-youtube-editor

    Makes this repo's videos look like YOUR channel instead of the house default — interviews you for palette, fonts, wordmark, motion energy, delivery specs and SFX taste, then rewrites brand.md +…

    328 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Clean Cut

    hassancs91/claude-youtube-editor

    Step 1 of the AI Video Editor pipeline — turn raw talking-head footage into a clean master cut.

    328 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Fake Screencast

    hassancs91/claude-youtube-editor

    Turn static SCREENSHOTS into a simulated screen recording (TSX) — a fake screencast with an animated cursor that eases to targets and clicks, a browser URL bar that updates per page, hard-cut…

    328 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Make Tsx

    hassancs91/claude-youtube-editor

    Step 2 of the AI Video Editor pipeline — build the visual beats (Remotion TSX shots) over a project's master cut and bake a composited preview.

    328 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • Suggest Sfx

    hassancs91/claude-youtube-editor

    Step 4 of the AI Video Editor pipeline — the SFX pass. An agent skill from hassancs91/claude-youtube-editor.

    328 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Youtube Packaging

What does Youtube Packaging do?

Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the…. Youtube Packaging is an agent skill from hassancs91/claude-youtube-editor. Generates click-optimized YouTube packaging — 3 thumbnail bets under one fixed title, engineered for YouTube's built-in A/B/C thumbnail test, plus a value-forward description, then renders the thumbnails as real images.

When should I use Youtube Packaging?

Youtube Packaging fits situations like: include how would you package this; title ideas for; thumbnail concept; package this video.

How do I install Youtube Packaging in Claude Code?

Run `npx skills add hassancs91/claude-youtube-editor --skill youtube-packaging -a claude-code`. Or copy the skill folder (.claude/skills/packaging in hassancs91/claude-youtube-editor) into .claude/skills/youtube-packaging in your project. Claude Code loads it when a task matches its description.

How do I install Youtube Packaging in Codex?

Run `npx skills add hassancs91/claude-youtube-editor --skill youtube-packaging -a codex`. Or copy the skill folder (.claude/skills/packaging in hassancs91/claude-youtube-editor) into .agents/skills/youtube-packaging in your project. Codex loads it when a task matches its description.

Can I use Youtube Packaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hassancs91/claude-youtube-editor --skill youtube-packaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/youtube-packaging, .gemini/skills/youtube-packaging, .github/skills/youtube-packaging and .opencode/skills/youtube-packaging in your project.

What does Youtube Packaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Youtube Packaging is instructions for the agent only.

Does Youtube Packaging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Youtube Packaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Youtube Packaging use?

Youtube Packaging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Youtube Packaging use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.6k tokens, read only when the agent opens those files.

What are the alternatives to Youtube Packaging?

Skills that share tags, products or a category with Youtube Packaging: Short Form Script (mohitagw15856/pm-claude-skills, 1.4k stars), Youtube Viral Optimizer (infranodus/skills, 119 stars), Video Content Strategist (alirezarezvani/claude-skills, 28k stars) and Youtube (npc-live/clawfirm, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Youtube Packaging?

hassancs91 (a GitHub user) maintains it in hassancs91/claude-youtube-editor, which has 328 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 18, 2026.

Source: hassancs91/claude-youtube-editor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.