Skip to content
Back to skills

Vidiq Packaging Studio

ASecurity

Create or improve YouTube titles and thumbnails from ideas, scripts, references, or published videos. Use for full packaging or focused edits, including title-only rewrites from supplied context without MCP calls.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsgoexpressperformance

Works with

  • mcp

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned October 9, 2026

npx -y skills add vid-io/vidiq-mcp --skill vidiq-packaging-studio --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vidiq Packaging Studio?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vidiq Packaging Studio
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vid-io-vidiq-packaging-studio/badge)](https://www.skillsdirectory.com/skills/vid-io-vidiq-packaging-studio)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vidiq-packaging-studio
description: Create or improve YouTube titles and thumbnails from ideas, scripts, references, or published videos. Use for full packaging or focused edits, including title-only rewrites from supplied context without MCP calls.
---

# vidIQ Packaging Studio

Read [Live surface notes](references/live-surface-notes.md) first, even when using only supplied evidence.

Create an honest title-thumbnail package from a concept, script, reference, or published video.
Use the creator's supplied audience, format, language, tone, and assets.

## Match the request

- For a focused title or thumbnail edit, go directly to that edit. Resolve a channel or fetch
  evidence only when the action needs it.
- For an idea or script, establish what the content can truthfully deliver.
- For a published video's performance diagnosis, investigate before attributing weakness to
  packaging. Read [Research and diagnosis](references/research.md).
- For a full package, research only gaps that can change the creative decision. Reuse sufficient
  supplied evidence.
- Before evaluating external references, including examples already supplied by the creator,
  read [Discovery evidence](references/discovery-evidence.md).
- For an explicit comparison of distinct concepts, use `vidiq-packaging-comparison`.

A critique does not imply generation; a title request does not imply a thumbnail or script.
Ask only for missing information that changes the requested result.

## Develop the package

Preserve what each number measures: video length does not prove how quickly an action was
completed. Use a speed claim only when demonstrated or explicitly supported by the brief.

1. State the viewer payoff, tension or proof, and factual limits. Preserve the supplied story and
   numbers. When covering someone else's story, distinguish its subject from the host analyzing it.
2. If references need to be retrieved, read [Research and diagnosis](references/research.md).
   Transfer
   abstract mechanisms and composition principles while using original expression. Respect the
   creator's own or appropriately licensed assets.
3. Develop the requested title candidates. Keep them truthful and within the platform limit.
   Describe originality as a creative judgment; claims about other videos need supporting evidence.
   Pair the title with thumbnail imagery or text that adds tension, proof, or stakes.
   Judge the pair against the brief; a model score is not a performance verdict.
4. Before using vidIQ tools to generate, score, or refine titles, thumbnails, or scripts,
   read [Production and scoring](references/production.md).
   Before an asynchronous call, read [Job lifecycle](references/job-lifecycle.md).
5. Inspect completed images for factual accuracy, legibility, rights, and attribution.
   If visual inspection is unavailable, return the draft with that limitation; do not claim it
   passed. Keep the version that best meets the brief, explaining any score tradeoff.

## Deliver

Return the requested titles, thumbnail directions, edited assets, or critique, with the rationale
and material limitations. Include source-to-adaptation reasoning when references informed the
work. For executed tools, report generated URLs or pending job IDs, relevant scores and their
context.

Omit unused stages and empty report sections. Include a script, comparison table, or iteration log
only when requested or useful to understand work actually performed.

Files in this skill

  • SKILL.md3.4 KB
  • agents/openai.yaml459 B
  • references/discovery-evidence.md849 B
  • references/job-lifecycle.md724 B
  • references/live-surface-notes.md2 KB
  • references/production.md3.7 KB
  • references/research.md3.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…