Communitygithub.com

Pluviobyte/rnskill

A skill for creating finished talking-head videos. It turns articles, scripts, SRT subtitles, edited videos, and HTML/image assets into storyboards, timeline previews, and a final MP4. Output aspect ratio and animation style are read from user configuration; animations default to the 'xiaohei' style. Trigger phrases: 口播成片, 做分镜稿, 时间线预览, 合成口播视频, 导出竖屏MP4.

What is rnskill?

This skill, developed by chengfeng / AI产品自由, automates the creation of finished talking-head (口播) videos. It takes an edited video, subtitles (SRT or timed JSON), optional script drafts, and supplementary assets (screenshots, images, HTML) as input. The core workflow is a three-step pipeline: first, it generates an HTML storyboard that segments the audio semantically, determines the visual task for each segment, and selects the best source material (original video, raw screenshots, HTML animations) according to strict rules. Second, after user approval of the storyboard, it produces a timeline preview to verify alignment between visuals and speech, checking for common issues like misplaced assets or cropping errors. Finally, once the timeline is approved, it synthesizes the final MP4 video with configurable output dimensions (e.g., 3:4 vertical for 1620x2160 at DPR 1.5, or 16:9 horizontal) and animation style (defaulting to 'xiaohei' comic-style SVG motion). The skill emphasizes fidelity to original material—using real screenshots and video clips for credibility—and reserves custom HTML/SVG animations only for conceptual explanations where the source footage is weak. It requires `ffprobe` validation and manual keyframe inspection for quality assurance.

Works with✓Claude Code✓Codex CLI~Cursor
npx skills add https://github.com/Pluviobyte/rnskill/tree/HEAD/skills/chengfeng-videocut-skills/%E5%8F%A3%E6%92%AD%E6%88%90%E7%89%87

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Completed Talking-Head Video

Official Source

This Skill is authored and maintained by chengfeng / AI产品自由.

https://github.com/Agentchengfeng/chengfeng-videocut-skills

Official Accounts: GitHub @Agentchengfeng; X @chengfeng240928; Xiaohongshu / WeChat Official Account / Bilibili / Douyin / WeChat Channels AI产品自由.

Core Workflow

This Skill solves one thing: turning a talking-head video into a complete finished video; the output aspect ratio and animation style are determined by user configuration.

+-----------------------------+
|  Input                      |
|  Video + Subtitles + Optional Assets |
+--------------+--------------+
               |
               v
+-----------------------------+
|  1. Storyboard              |
|  Semantic segmentation + task type + visual source |
+--------------+--------------+
               |
               v
+-----------------------------+
|  2. Timeline Preview        |
|  Align original video/screenshots/HTML with speech |
+--------------+--------------+
               |
               v
+-----------------------------+
|  3. Synthesis               |
|  Export final MP4 according to user config ratio     |
+--------------+--------------+
               |
               v
+-----------------------------+
|  Validation                 |
|  ffprobe + keyframe inspection |
+-----------------------------+

Do not present cue tables, HTML modules, review player, final player, or export scripts as separate user workflows. They are implementation details within "Timeline Preview" and "Synthesis."

User Configuration

Every time this Skill is executed, first read:

用户配置/default.json

The configuration only defines the user's current selection:

{
  "aspectRatio": "3:4",
  "animationStyle": "xiaohei"
}

Supported values:

  • 3:4: Default vertical HD; logical canvas 1080x1440; exports at DPR 1.5 for 1620x2160.
  • 16:9: Horizontal; logical and export canvas 1920x1080.
  • 4:3: Horizontal; logical and export canvas 1440x1080.
  • animationStyle: Default xiaohei; options from 动画/styles.json.

Command-line arguments override user configuration; when no explicit parameters are given, the export script reads aspectRatio and the animation script reads animationStyle. Temporary ratio overrides with:

--config /path/to/config.json
--ratio 16:9
--aspect-ratio 16:9
--width 1920 --height 1080
--dpr 1.5

Do not include visual preferences, templates, encoding quality, output directories, subtitle margins, or other various settings in 用户配置/default.json. User configuration only holds the current selection; the animation directory only holds the options registry and specific style implementations.

Animation Style

The currently selected animation style is placed in 用户配置/default.json:

animationStyle

The animation directory only registers options:

动画/styles.json

xiaohei maps to:

动画/ian-xiaohei-svg-motion/

When a storyboard or HTML module needs explanatory animations, flow animations, or hand-drawn-style highlights, default to the xiaohei comic-style SVG motion effects. Do not invent new animation styles on the fly unless the user explicitly specifies otherwise.

Input

First locate these files:

  • Main video: source_cut.mp4, *_cut.mp4, or a user-specified edited video.
  • Subtitles: subtitles.srt, video.srt, or subtitles_with_time.json.
  • Optional script: article, voiceover script, body draft; only used to understand intent.
  • Optional assets: screenshots, product pages, comment images, result pages, proof pages in assets/.
  • Project rules: if the current project has AGENTS.md or README.md, read it first.

Truth source priority:

Actual audio / subtitles > Edited video visuals > Asset files > Script draft

If the script and actual subtitles differ, defer to the subtitles and audio.

Step 1: Storyboard

Default to creating an HTML storyboard review page first; do not start with a Markdown table.

The pre-storyboard workflow must follow this order:

  1. Segment by speech semantics: combine one, two, or three sentences that discuss the same concept, action, or evidence into one segment; do not mechanically split by subtitle number.
  2. Determine the visual task for each segment: is it a workflow demonstration, original image explanation, result proof, conceptual organization, or pure text expression.
  3. Decide the visual source: for segments that can use real screen recordings, original screenshots, or original images for proof, prioritize the original material; only design HTML / xiaohei animations for conceptual explanations where the current screen is mainly text, white space, or weakly related visuals.
  4. Only then proceed to specific visual design: for each HTML / xiaohei animation segment, first write down its independent metaphor and action, then implement the module.

Common path:

review/storyboard-audit-vN.html

Default template:

templates/storyboard-audit.html

The storyboard should answer the user's question:

When this sentence is spoken, what should the audience see?

At minimum, clearly specify for each segment:

  • Time range
  • Subtitle number
  • Full spoken text
  • Semantic segmentation rationale
  • Visual task
  • Visual type: Original Video, Operation Screen Recording, Original Screenshot, Original Image, Infographic Focus, HTML Animation, Text + Animation
  • Asset source
  • Camera action

Visual selection rules:

  • Operation demonstrations: use the original video / original screen recording; do not convert to abstract animations.
  • When explaining image content, chart content, error screenshots, product screenshots: use the original image or original screenshot directly; animations only for circling, annotating, and local focus.
  • Real operations, proof pages, result pages, segments requiring credibility: retain original video or original screenshot.
  • Screen recordings / original video segments default to full original display; only if segmentation explicitly needs to avoid subsequent unified subtitles, mark that segment as a screen-recording small window and leave subtitle-safe space at the bottom. Do not batch-apply the small-window rule to all screen recording segments.
  • Conceptual organization, mechanism relationships, system division, opinion summarization where the current screen is mainly text, white space, or weakly related visuals: create HTML / xiaohei animations.
  • Abstract segments that can be understood with brief text: use text + animation; text handles naming, animations handle relationships and actions.
  • Existing screenshots or infographics: reuse them first; do not redraw.
  • When the same image appears multiple times, each occurrence must serve a different purpose: overview, local focus, comparison, result re-examination.
  • Do not make all animations use the same dynamics. Each animation segment must first design its action metaphor independently, then implement.

Hard storyboard standards:

  • One page presents only one concept, one action, or one case. If the same speech segment contains two independent cases, it must be split into two pages; do not cram two cases into the same table or same animation to save pages.
  • For each HTML / xiaohei animation segment, first write down "When this sentence is spoken, what changes on screen," then implement. Actions must be bound to specific spoken sentences or subtitles; do not apply the same entrance/flash/zoom effect uniformly to all segments.
  • When explaining original images, screenshots, or result pages, the main visual must be the original asset. HTML is only responsible for cropping, zooming, circling, annotating, and focus switching; do not replace the original image with screen recording frames or redrawn graphics.
  • For long images and web result pages, default to cropping out blank non-informative areas, prioritizing exposure of the region the audience is hearing about; when the speech mentions a corresponding object, you may zoom into that image or part, pushing the rest to the background.
  • Do not include asset paths, internal notes, action explanations, or workbench text like "original image asset · img/xxx.png" in the video frame. Storyboards may include sources; the final video only retains content the audience needs to see.
  • Do not add titles unless necessary. Result pages, table pages, and original image comparison pages should let the main visual speak for itself; only keep short labels, model names, metric names, or necessary annotations.
  • Data comparison pages should prioritize clear tables, column alignment, short labels, and minimal highlighting. Font size must serve readability; do not cram text into tiny boxes. If a simple table explains it clearly, do not build complex card stacks.
  • In vertical short videos, tables should not be reduced to a narrow horizontal strip in the middle. During data phases, make the table the main visual, occupying the primary safe zone; task descriptions, case labels, and summary phrases appear only during the corresponding speech phase and must disappear or recede to non-space-consuming positions during the final data comparison phase.
  • Evaluation terms should only include positive/neutral results explicitly stated in the speech or required by editing emphasis. Comparison columns can be left blank or show only data; do not add negative words like "slow and expensive" unless the original speech reaches that conclusion.
  • Icons must be found from the animation library index. Existing icons for ChatGPT, Claude, Flash lightning, Step, DeepSeek, Qwen, etc., must not be replaced with abstract shapes; when a user provides a new SVG, first store it in the animation library and update the index.

Do not proceed to timeline preview before storyboard direction is confirmed.

Step 2: Timeline Preview

After storyboard direction is confirmed, proceed to timeline preview.

Common path:

review/timeline-preview.html

Default template:

templates/timeline-preview.html

Timeline preview checks:

  • Whether visual transitions align with speech sentences.
  • Whether the original video has been mistakenly replaced with HTML.
  • Whether segments marked as screen-recording small windows avoid the bottom subtitle safe zone; unmarked recording segments must not be automatically windowed.
  • Whether screenshots, pages, and proof assets are used correctly.
  • Image assets default to retaining left/right margins; do not fill the current screen entirely; only scale down when emphasizing a full screenshot is needed.
  • Whether the frame blocks text, crops improperly, or has black bars.
  • Whether HTML modules look fine alone but are still valid when placed in the full timeline.

When the preview page includes source video, it must be served via an HTTP Range-enabled service; otherwise, the browser cannot randomly seek, and the progress bar will reset to the beginning. Do not use plain python -m http.server to preview MP4 timelines. Default to:

node ~/.Codex/skills/chengfeng-videocut-skills/口播成片/scripts/serve_range_preview.cjs \
  --project-dir /absolute/path/to/project \
  --port 8767

Generate if necessary:

docs/08-动画cue表-vN.md
html-modules/module-*.html
html-modules/xiaohei-*.html

If a new explanatory animation is needed, first read animationStyle from 用户配置/default.json, then find the corresponding animation sub-skill in 动画/styles.json.

Each animation action must be bound to a specific spoken sentence; do not evenly distribute time. Multi-stage HTML animations must explicitly manage visibility states: when the next stage appears, information cards, labels, and annotations from the previous stage that no longer serve a purpose must be hidden; do not let the previous stage continue occupying main visual space, especially for vertical-screen data tables, screenshot focus areas, and result pages.

Step 3: Synthesis

Only proceed to synthesis after the user has confirmed the timeline preview.

Before synthesis, create or confirm:

final-player.html

Before writing a new final-player.html or HTML module, read:

references/artifact-contracts.md

If the project has HTML modules, first inject the render mode:

node ~/.claude/skills/chengfeng-videocut-skills/口播成片/scripts/write_render_mode.cjs \
  --project-dir /absolute/path/to/project

Timeline preview and final export must use the same HTML rendering context. HTML modules in both the preview page and final-player.html must include ?timeline=1&render=1; the preview page only scales the final canvas proportionally inside the window; modules must not re-layout responsively based on the preview window.

High-definition delivery must not simply scale the CSS logical canvas. Default 3:4 must maintain the 1080x1440 logical canvas, then use screenshot DPR 1.5 to output 1620x2160; otherwise, tables, CSS cards, and screenshot annotations will appear relatively smaller in the export compared to the preview.

If preview and export sizes differ, first check the HTML module's internal CSS, render-mode.js, and export DPR to confirm the preview page and final-player have the same logical canvas; do not re-export the entire video first. Common causes are that the preview iframe is smaller and looks fine, but the final HD canvas triggers constraints like .photo-frame { max-width: ... }, .stage { width: min(...) }, .wrap { max-height: ... }, clamp(...), causing the export to become a "small image." Fix order:

  1. Regenerate html-modules/render-mode.js with write_render_mode.cjs.
  2. Confirm in the timeline preview that the HTML module URL has become ?timeline=1&render=1.
  3. Confirm that viewport in export_final_video.cjs is the logical canvas size, and dpr is the HD multiplier.
  4. Use final-player to capture a keyframe of that module under the actual export viewport; if necessary, use getBoundingClientRect() to compare the main visual container size.

When handling horizontal xiaohei SVG / 16:9 SVG modules in a vertical screen, do not use overall scaling like .wrap { transform: scale(...) } to solve "small horizontal bar" problems. Overall scaling in a 3:4 canvas will crop the left and right edges, especially model cards, arrows, and explanatory labels distributed left-to-right. Either rearrange into a vertical composition or maintain a complete safe zone; after changes, must capture the left and right boundary frames of that module, not just the center keyframe.

Export the final video:

node ~/.claude/skills/chengfeng-videocut-skills/口播成片/scripts/export_final_video.cjs \
  --project-dir /absolute/path/to/project \
  --input-video /absolute/path/to/source_cut.mp4 \
  --duration 173.03

Default to HD delivery: lossless PNG intermediate frames, H.264 crf=14, preset=slow. This avoids the scenario where the browser preview is clear but the export has soft small text and thin lines:

node ~/.claude/skills/chengfeng-videocut-skills/口播成片/scripts/export_final_video.cjs \
  --project-dir /absolute/path/to/project \
  --input-video /absolute/path/to/source_cut.mp4 \
  --duration 173.03 \
  --frame-format png \
  --crf 14 \
  --preset slow

Only when temporarily reviewing rhythm or needing a fast draft, explicitly downgrade:

node ~/.claude/skills/chengfeng-videocut-skills/口播成片/scripts/export_final_video.cjs \
  --project-dir /absolute/path/to/project \
  --input-video /absolute/path/to/source_cut.mp4 \
  --duration 173.03 \
  --frame-format jpeg \
  --quality 92 \
  --crf 18 \
  --preset medium

Ratio reading rules are under "User Configuration." When the project differs from user configuration, pass:

--config
--ratio
--aspect-ratio
--fps
--player
--stage
--frames-dir
--width
--height
--frame-format png|jpeg
--quality 100
--crf 14
--dpr 1.5
--device-scale-factor 1.5

Validation

A successful export does not mean the final video is correct. Two steps are mandatory:

  1. Use ffprobe to check resolution, frame rate, duration, and audio.
  2. Extract 3+ keyframes and manually verify the visuals are correct.
  3. For each HTML module, extract at least 1 frame from final-player at the corresponding speech timepoint and compare with the timeline preview at the same timepoint; size, position, cropping, and visibility must be consistent; do not rely solely on ffprobe as the completion criterion.

Check resolution according to the current ratio; other expectations come from script defaults and actual project input. Current default configuration:

1620x2160
Logical canvas 1080x1440, DPR 1.5
3:4
30fps
Duration matches edited source video
Has audio
No HUD, buttons, review timeline, or browser UI

Boundaries

Suitable for:

  • Chinese language talking-head videos
  • Tutorials, product demos, result showcases, knowledge explanations
  • Existing edited video and subtitles; assets can be added later
  • Mixed output using original video + screenshots + HTML explanation visuals

Not prioritized:

  • Generating a finished video from a script alone without any video input
  • Complex multi-camera live-action editing
  • Fine color grading and multi-track mixing requiring NLE project files
  • User requesting final publishing without reviewing storyboard and timeline preview

Project Hygiene

If adding or modifying files in the user's working directory, must synchronously update the project README index.

Local activity logs are placed uniformly at:

log/

log/ only records local experiments, user preferences, temporary conclusions, and unpublished work-in-progress; it must not be uploaded to GitHub. This directory is ignored by .claude/skills/.gitignore.

Do not add a new README in this Skill's directory. The core files of this Skill only retain:

SKILL.md
templates/
references/
scripts/
用户配置/
动画/

动画/ is used to accumulate reusable HTML/SVG/GSAP animation sub-skills, templates, and rules for talking-head video production; optional styles are in 动画/styles.json, current selection is in 用户配置/default.json.

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Pluviobyte/rnskill

将法天象地、同源巨大法相或角色力量显现的视觉参考制作成连续关键帧,再使用用户选择或可用的图生视频工具分段生成、检查和合成动作视频,不绑定成片平台。适用于本体与法相同框、领域展开、凝实与同步出招;不负责整部小说改编或普通图片轮播。

Pluviobyte/rnskill

口播基础素材包生成。转录口播、识别口误、生成审核页;用户确认后剪出新视频,Agent 再基于剪后视频重新转写、AI 校对字幕,输出后续口播成片可用的 source_cut.mp4 和 subtitles.srt。触发词:剪口播、处理口播素材、准备口播素材、识别口误、基础素材包

Pluviobyte/rnskill

Create Ian Xiaohei-style HTML/SVG motion illustrations for Chinese articles, scripts, storyboard scenes, workflow explanations, concept metaphors, and short video visual aids. Use when the user asks for 小黑 SVG、漫画感 HTML、分层 SVG 动效、把小黑生图做成 HTML/SVG、可编辑矢量动效、口播流程动画、手绘漫画动效、正文配图动画, or wants a Xiaohei illustration style adapted into controllable HTML/SVG/GSAP output instead of raster image generation.

Pluviobyte/rnskill

自进化 skills。记录用户反馈,更新方法论和规则。触发词:更新规则、记录反馈、改进skill

Pluviobyte/rnskill

dontbesilent 目标清晰化。用维特根斯坦的语言哲学把模糊的目标审计成可检查的交付物。 触发方式:/dbs-goal、/目标、「帮我搞清楚目标」「我想做个人 IP」「我的目标是成为...」「我想变得更...」 Goal clarification using Wittgenstein's philosophy of language. Audits fuzzy goals into checkable deliverables. Trigger: /dbs-goal, "help me clarify my goal", "I want to become...", "my goal is...

Pluviobyte/rnskill

dontbesilent 短视频开头优化。诊断开头问题 + 生成优化方案。 触发方式:/dbs-hook、/hook、「帮我优化开头」「开头怎么写」 Short video opening optimization with diagnosis and solutions. Trigger: /dbs-hook, "optimize my opening", "how to write opening

Pluviobyte/rnskill

把当前诊断的关键状态存到本地,下次回来可以接着用。 触发方式:/dbs-save、/存档、「保存这次诊断」「记下来」「这个结论留着」 Save the current diagnosis state to disk for cross-session recall. Trigger: /dbs-save, "save this diagnosis", "remember this

Pluviobyte/rnskill

dontbesilent 商业工具箱主入口。双模式:任务前路由(你的问题该用哪个 skill)+ 任务后导航(刚做完诊断,下一步该干什么)。 触发方式:/dbs、/商业、「帮我看看」、「下一步怎么走」 Main entry point for dontbesilent business toolkit. Dual mode: pre-task routing + post-task navigation. Trigger: /dbs, "help me with my business", "what's next

Pluviobyte/rnskill

孙宇晨.skill 的别名。触发后立刻读取并执行 `../孙宇晨/SKILL.md`,不单独维护内容。 触发:孙割.skill、/孙割、"用孙割视角看"、"孙割会怎么处理"、"切换到孙割"。

Pluviobyte/rnskill

蒸馏孙宇晨(孙割)公开可查的决策模式,做成一套非扮演的决策分析工具:拆解他如何把注意力、身份、叙事当成可购买、可叠加、可兑换的资产来经营,用来给你自己的选题/发布/公关/危机决策做沙盘推演,不用于替他或任何真实人物发声、编造言论。 触发:孙宇晨.skill、孙割.skill、/孙宇晨、/孙割、"用孙割视角看"、"孙宇晨会怎么做"、"孙割会怎么处理"、"注意力收割模型"、"蒸馏孙宇晨"。

Pluviobyte/rnskill

将参考图或简要描述解码为可编辑的半色调纸张拼贴规范,默认使用 Codex 内置 image_gen 生成品牌一致的静帧和透明图层,再用本地 FFmpeg 或 HyperFrames 制作“从空背景逐件组装”的确定性动态视频。用户提到半色调拼贴、纸张拼贴、剪纸拼贴、编辑式拼贴、杂志拼贴、复古印刷拼贴、拼贴动效、拼贴动画、剪纸动画、纸片组装、逐层组装、从无到有、元素飞入拼装、定格拼贴、定格动画、Arcads 风格、参考图拆解、风格拆解、反向拆解视觉、照这个风格做、做类似的、生成拼贴静帧、让这张图动起来、让这些元素组装起来、制作拼贴广告或拼贴解释视频时使用。英文触发语义包括 editorial collage、halftone collage、paper collage、paper-cut motion、stop-motion graphic、assemble from empty、build-on motion、analyze this、break this down、reverse-engineer this look、generate the stills、animate this、make these move。默认不调用 Arcads、Nano Banana、Seedance 或 Kling;只有用户明确要求且对应连接器可用时才进入外部生成路径。

Pluviobyte/rnskill

Create deterministic editorial-style cover images with a warm paper-gray background, oversized black slab-serif/Chinese display typography, generous whitespace, and a dotted vector analysis icon. Use when the user asks for a “点阵编辑风封面”, “暖灰杂志风封面”, “Codex + Hyperframes 同款封面”, or wants to reproduce/adapt the specific minimal left-text/right-icon banner style. Produce editable SVG and a rendered PNG; do not use this skill for generic covers without this visual direction.

Pluviobyte/rnskill

Chinese AI/tech writing de-AI editor for posts, X/Twitter threads, technical essays, product notes, model reviews, and public-writing drafts. Use when the user asks to 去AI味, 改得像本人, 写推特post, 精修中文AI技术文章, or complains about AI-flavored shells such as 不是A而是B, 真正/其实/本质上, 更重要的是, 冒号讲义腔, 空泛总结, 顺滑但没作者判断的稿子.

Pluviobyte/rnskill

内容复盘工作流:取数 → 爆款分级(R/M/Tier)→ 按需拉取内容本体 → 归因 → 沉淀(方法论/金句库/案例库/概念库/课程灵感)+ 选题卡回写。 Use when the user says 复盘xx, 内容复盘, xx数据怎么样, xx表现如何, 复盘一下这条, 为什么这条爆了, 为什么这条没爆. 沉淀铁律:复盘不沉淀,等于白复盘——每次至少一条资产入库,或写明为什么没有。

Pluviobyte/rnskill

实操长片策划工作流(B站/YouTube 新赛道,实操+真人出镜)。产出可直接照着录的策划稿:测试题组(含可粘贴 prompt)、 结构时间轴(全身出镜段 vs PiP 段)、出镜口播稿、录屏操作清单、悬念与彩蛋设计。 Use when the user says 做实操长片, 实操视频, 实测视频, 对比实测, xx做成实操, 出个实测策划, 这个选题拍实操, or ra-选题 routes a 实操长片 立项 here. 策划稿落 `01-内容生产/视频工作台/制作中/<日期-主题>/策划稿.md`,frontmatter status 是与制作端交接的唯一状态机。

Pluviobyte/rnskill

视频脚本洗稿和二创脚本工作流。Use when the user provides an existing transcript, oral draft, viral script, competitor video text, rough topic notes, or wants 洗稿, 二创改写, 爆款视频脚本重写, 逐字稿改成短视频脚本, rewrite with ra-人话, and queue the approved script into 01-内容生产/视频工作台/待制作/ as the handoff contract for video production. If the user provides a video URL or local video file and asks 视频洗稿、视频二创、洗稿并制作视频, use ra-video-wash-pipeline first.

Pluviobyte/rnskill

选题全生命周期调度:记录选题、深化选题、选题推荐、立项分发(视频/图文/文章/实操长片/多形态)、发布归档。 Use when the user says 灵感xx, 想法xx, 记录选题, 这个可以做个选题, 先存着这个链接, 深化选题/深化一下xx, 给我N个选题, 帮我出选题, 选题推荐, 立项, 做成视频, 制作视频, 做成文章, 制作文章, 做成图文, 制作图文, 做成实操长片, 图文视频文章都做/都分发, 我要自己出镜讲, xx发布了, xx要改; or when the user gives a link plus a target form (链接+制作视频/文章/图文). Owns the 00-选题池 card system: one topic = one card; user never moves files — this skill does.

Pluviobyte/rnskill

短视频钩子(开头)类型选择与写法,中文名「钩子」。Use when 起钩子、写钩子、钩子怎么写、钩子没思路、设计前5秒钩子、写视频开头/口播稿开头, or when the user asks 视频开头怎么做、开头模板、hook 类型、帮我起个钩子, including during ra-洗稿 script rewriting and 选题深化. Provides a scenario-based taxonomy of 7 hook types with decision flow, prerequisites, sentence templates, and common mistakes. For diagnosing and optimizing an existing hook draft, use dbs-hook instead; this skill chooses the type, dbs-hook polishes the execution.

Pluviobyte/rnskill

End-to-end video production orchestration for the content-creation workspace. Use when the user asks to make, recreate, package, render, QC, or archive a video; when the user says 制作待制作队列, 按交接稿制作, 制作队列视频, or points at a handoff project folder under 01-内容生产/视频工作台/待制作/ (contract file 交接稿.md inside) or an image-card handoff under 01-内容生产/图文工作台/待制作/ (its frontmatter is the binding production contract); when a request could route to HyperFrames, Remotion, captions, TTS, download/transcription, website/product videos, motion graphics, or reference replication; or when the user needs production planning before editing.

Pluviobyte/rnskill

Create dark cinematic SaaS/product motion videos in the Presenton-like "magic UI" style: black starfield stage, bottom purple glow, large kinetic type, cyan-to-magenta CTA buttons, prompt cards, floating UI templates, integration badges, model rings, export objects, speed-blur transitions, and short product capability arcs. Use when the user asks for "这种风格", "同款风格", dark SaaS promo, AI product demo, magic UI product video, or a style-level creation inspired by a reference video. Do not use for pixel-level or frame-accurate replication; use rn-replica-qc first for that.

Related Skills