intro-video-brief

intro-video-brief is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 75 tokens per session (4,477 once invoked), scanned A, original, MIT.

A workflow for researching a product and preparing a structured brief for an introductory or demonstration video. It can also review an existing Remotion video project and suggest improvements to its scenes, timing, animation, and wording.

In plain words
What is it for?
Use it to prepare a video brief from a GitHub link, website, or description, or to audit and refine a Remotion-based video.
Why use it?
It turns scattered product information or an existing video project into a focused plan for producing or improving a product video.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ../lib/content.ts → product copy, features, stats, comparison data.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit Use it to prepare a video brief from a GitHub link, website, or description, or to audit and refine a Remotion-based video.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai
agentmods
npx agentmods add skills/hamzapixl/pixl-ai/intro-video-brief

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for intro-video-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/intro-video-brief/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/intro-video-brief)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/intro-video-brief"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/intro-video-brief/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for intro-video-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/intro-video-brief"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/intro-video-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,477 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.04477
Opus 5.5 $0.00030 $0.01791
Sonnet 5.5 $0.00015 $0.00895
Haiku 4.5 $0.00007 $0.00448

Measured 1mo ago against content hash c6a557bc5276, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

intro-video-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/crew/skills/intro-video-brief/SKILL.md · 421 lines

How it starts

The opening of the file, as written. The whole thing — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Two modes:

  • Create mode (default): Research product → interview user → generate video-brief.json → pass to /remotion
  • Enhance mode (--enhance or when a Remotion project path is provided): Audit existing Remotion composition → identify issues → produce an improved video-brief.json + inline code suggestions

Design principle: Every video must feel like real motion design — varied scene types, distinct atmospheres per scene, kinetic typography, and intentional hard cuts alongside smooth transitions. Never let every scene use the same layout, same entry animation, or same background treatment.


Mode Detection

Detect which mode to run:

  1. Enhance mode if any of:

    • Argument contains --enhance
    • Argument is a directory path containing remotion.config.ts, src/Root.tsx, or src/compositions/
    • User says "improve", "enhance", "fix", "audit", or "update" the video
  2. Create mode otherwise (GitHub URL, website URL, or free-form description)


Read references/video-vocabulary.md for scene type, animation, and atmosphere vocabulary.


CREATE MODE

Step 1: Gather Inputs

  1. Parse the argument to identify:

    • Directory path → read content files directly (README, content.ts, globals.css, package.json)
    • GitHub URL (github.com/org/repo) → fetch README + repo metadata
    • Website URL → fetch homepage content
    • Free-form description → use as product context directly
  2. Ask missing essentials (only ask what cannot be inferred):

    Quick questions to shape your intro video:
    
    1. Target platform? [16:9 YouTube/Web | 9:16 TikTok/Reels | 1:1 Instagram]
    2. Video duration? [15s | 30s | 60s]
    3. Visual tone? [minimal | energetic | bold | corporate | playful]
    4. Primary brand color? (hex or "I don't know — pick from the product")
    5. Should I include a voiceover script? [yes | no]
    

    Skip any question the user already answered via arguments or description.

Step 2: Research the Product

Read the full file on GitHub · 421 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 421 lines · 75 tokens per session scan A c6a557bc5276

Subscribe to this mod's changes

intro-video-brief is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 75 tokens to every session and 4,477 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens