agentleFS
sharon-laiccsharon-laicc/viral-video-decomposer/SKILL.md

video-structure-analyzer

Skill4 starsChanged 5 months agoMITView on GitHub

拆解爆款短视频、Vlog、小红书/抖音/B站视频、广告素材或竞品视频时使用。用于把视频链接、截图、录屏、字幕、逐字稿或参考视频拆成镜头级拉片表、爆款机制、可复用结构、批量选题变量、脚本/分镜/prompt,以及给后续视频生成 agent 使用的 JSON brief。也适用于用户说“分析爆款视频”“拆视频”“拉片”“拆解短视频”“复刻这种视频结构但不要抄”“根据爆款批量产出视频方案”等场景。

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. F0rger123/claude-video-editing-god-mode★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill as the pre-production researcher for video-generation agents.

    line 10
  2. Distinctive:

    If a platform blocks direct download, use browser inspection, screenshots, transcript/OCR, page metadata, or manually sampled keyframes.

    line 24
  3. Very specific:

    Prefer direct transcript/subtitles and frame sampling.

    line 32
  4. Distinctive:

    Use this table unless the user asks for another format:

    line 76
  5. Distinctive:

    Treat empty shots as meaningful: B-roll, pauses, object close-ups, and transition shots often carry rhythm and emotion.

    line 108
  6. Distinctive:

    If evidence is incomplete, mark confidence and avoid pretending exact frame timing is known.

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Video Structure Analyzer

Use this skill as the pre-production researcher for video-generation agents. The goal is not only to explain why a video works, but to produce reusable, original, machine-readable production specs.

Core Rule

Analyze methods, structure, rhythm, and production logic. Do not copy protected expression. Avoid reproducing exact scripts, distinctive shot sequences, watermarks, creator identity, brand identity, or proprietary assets unless the user owns them or explicitly asks for analysis-only commentary.

Input Modes

Accept any available source:

  • Video URL from Xiaohongshu, Douyin, Bilibili, YouTube, Kuaishou, TikTok, Instagram, or an ad library.
  • Local video, screen recording, screenshots, contact sheet, transcript, SRT/VTT, OCR text, or existing notes.
  • Multiple videos when the user wants a pattern library or batch production template.

If a platform blocks direct download, use browser inspection, screenshots, transcript/OCR, page metadata, or manually sampled keyframes. State the limitation in the output.

Workflow

  1. Capture source facts: Title, creator/account, platform, URL, duration, visible engagement metrics, publish date if available, product/category, and any extraction limitations.
  2. Extract usable evidence: Prefer direct transcript/subtitles and frame sampling. If available, use ffmpeg/ffprobe for duration and keyframes. For blocked web video, sample screenshots at meaningful timestamps and record the method.
  3. Build the shot-level table: The table is the main output. Include timecode, duration, visual, shot size, action, subtitle/dialogue summary, sound, camera angle, camera movement, transition, emotional function, narrative function, and generation prompt.
  4. Segment the narrative: Group shots into sections such as Hook, setup, proof, reveal, contrast, routine block, escalation, payoff, summary, CTA. Name the section by its job, not by vague labels.
  5. Explain the viral mechanism: Identify hook type, curiosity gap, emotional driver, information density, rhythm, visual density, trust signals, audience fantasy/pain, repeatable meme or comment trigger, and conversion move.
  6. Convert analysis into production assets: Produce reusable templates, variables, batch variants, script options, shot prompts, caption rules, BGM/SFX guidance, platform adaptations, and a video_generation_brief.json-style object.
  7. Add originality guardrails: List what can be reused at the pattern level and what must be changed to avoid copying.

Required Outputs

For quick requests, answer inline with these sections:

  • Source facts
  • One-paragraph thesis
  • Shot-level table or compressed shot table
  • Viral mechanism
  • Reusable production template
  • Batch variants or next-video ideas
  • JSON brief

For substantial requests, create files in the working project:

  • *_拆解报告.html or *_拆解报告.md
  • *_拉片拆解.md
  • *_video_generation_brief.json
  • Optional contact_sheet.jpg and sampled frame images

When producing HTML reports, read references/report-style.md and follow that style contract. Prefer a dense professional analysis surface, not a marketing landing page. The accepted default is a Viral Video Lab report with source facts, stats, contact sheet, shot cards, production table, AI blueprint, variable slots, prompt template, and an A/B visual style toggle.

The AI 生产蓝图 module should use the same module/card styling as adjacent sections in both A and B themes unless the user explicitly asks for a special treatment.

For key-shot overviews, generate a compact contact sheet with tight gutters. Do not use large screenshot row gaps that make the report excessively long.

Shot Table Schema

Use this table unless the user asks for another format:

排序镜号时间码时长秒画面景别内容/动作台词/字幕声音摄像机角度镜头运动转场情绪功能叙事功能生成提示词

For fast analysis, compress to:

镜号时间码画面/动作台词/字幕摘要情绪功能叙事功能可复用生成提示

JSON Brief

For the complete JSON contract and detailed heuristics, read references/output-contract.md when generating machine-readable assets.

Minimum JSON object:

{
  "source": {},
  "analysis_summary": "",
  "viral_pattern": {},
  "shots": [],
  "production_template": {},
  "batch_variants": [],
  "originality_guardrails": []
}

Quality Bar

  • Be concrete: prefer "0-3s close-up of messy desk, abrupt zoom, anxiety hook" over "strong opening".
  • Preserve timing: timecodes and durations matter because later agents need executable pacing.
  • Treat empty shots as meaningful: B-roll, pauses, object close-ups, and transition shots often carry rhythm and emotion.
  • Separate human-readable insight from machine-readable production specs.
  • If evidence is incomplete, mark confidence and avoid pretending exact frame timing is known.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.