Claude Skill

tutorial-steps

Tutorial Steps video-editing style for Claude: Screen tutorial: your screen recording fills the frame, your face in a round bubble, numbered step banners. Use for software tutorials, how-tos, app walkthroughs, trading platform guides. Turns a raw clip into a finished 16:9 edit wi

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download viprasol-tech-claude-video-editing-skills-plugins_video-studio_skills_tutorial-steps-0293497.zip · 2 KB

Install

skills CLI npx skills add https://github.com/Viprasol-Tech/claude-video-editing-skills/tree/main/plugins/video-studio/skills/tutorial-steps
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install viprasol-tech-claude-video-editing-skills@llmmart
Git git clone https://github.com/Viprasol-Tech/claude-video-editing-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole viprasol-tech/claude-video-editing-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Tutorial Steps

Screen tutorial: your screen recording fills the frame, your face in a round bubble, numbered step banners.

  • Best for: software tutorials, how-tos, app walkthroughs, trading platform guides
  • Category: YouTube explainer
  • Default format: 16:9 (change with --format 9:16 | 1:1 | 4:5 | 16:9)
  • Needs camera footage: yes, a raw talking clip
  • Text behind the speaker: no

Before you start

This style runs on the video-studio-core skill, which must be installed in the same skills folder.

  • CORE = the video-studio-core folder next to this one (e.g. ~/.claude/skills/video-studio-core).
  • STYLE = this skill's folder (it holds theme.json and theme.css).
  • First time on a machine: python CORE/scripts/check_env.py, and fix anything it reports.
  • If CORE is missing, tell the user to install video-studio-core from the same pack.

Make the edit

python CORE/scripts/run.py clip.mp4 --style STYLE --work edit-tutorial-steps --stop-after plan --clip screen.mp4
# refine edit-*/plan.json (see below), then check stills:
python CORE/scripts/render.py edit-tutorial-steps/plan.json --frames 1,3,6,9
python CORE/scripts/render.py edit-tutorial-steps/plan.json
python CORE/scripts/finish.py edit-tutorial-steps/plan.json

Open contact_sheet.png and look at it before the full render. The final video is final.mp4 in the work folder. Use --formats 1:1,16:9 on finish.py for extra sizes. Add music with "music": {"src": "track.mp3", "volume": 0.12} in the plan.

The look

  • Screen recording is the main picture; face bubble bottom-right. Step banner top-left changes with each step.
  • Zoom into the part of the screen being discussed using a bigger clip with an offset if needed.

Refine the plan

The draft from make_plan.py is automatic. Make it good:

  • Read words.json and rewrite the hook (first 2-3 s) into a short, specific promise.
  • Replace weak auto-picked key words with the words that carry the meaning (numbers, results, names, contrasts).
  • Fix any mis-heard words in the words array (keep their times).
  • Run with the face-cam clip as the input and --clip screen.mp4 (make_plan option) for the screen recording. Both must start together.
  • Steps are detected from 'first / step two / next'. Otherwise add chip elements with class ts-step ('Step 1 · Open settings') at each step start.
  • Add scribble circles (kind box or circle) around buttons the user clicks.
  • Element types and fields: CORE/references/plan-schema.md.

Check before delivering

  • Contact sheet: text readable, nothing cut off, nothing covering the face unless intended, safe zones respected (9:16: keep text between 10% and 85% of the height).
  • Watch for timing: overlays land with the spoken word, not after it.
  • ffprobe the final file: right size, duration and audio.
  • Tell the user what you cut (seconds removed), what the look adds, and where the file is.

Change the look

Colours and fonts live in theme.json (vars, fontsUrl) and theme.css. For a one-off change, edit plan.json (theme.vars, element style) instead of the skill files.

Example requests

  • "Tutorial edit: my screen with my face in a bubble."
  • "Add step numbers to my software tutorial."
  • "Make a clean how-to video from my screen recording."
Files (claude-video-editing-skills)
  • SKILL.md 3.7 KB
    ---
    name: tutorial-steps
    description: "Tutorial Steps video-editing style for Claude: Screen tutorial: your screen recording fills the frame, your face in a round bubble, numbered step banners. Use for software tutorials, how-tos, app walkthroughs, trading platform guides. Turns a raw clip into a finished 16:9 edit with the video-studio-core engine (transcribe, auto-cut, motion graphics, sound, grade)."
    license: MIT
    ---
    
    # Tutorial Steps
    
    Screen tutorial: your screen recording fills the frame, your face in a round bubble, numbered step banners.
    
    - **Best for:** software tutorials, how-tos, app walkthroughs, trading platform guides
    - **Category:** YouTube explainer
    - **Default format:** 16:9 (change with `--format 9:16 | 1:1 | 4:5 | 16:9`)
    - **Needs camera footage:** yes, a raw talking clip
    - **Text behind the speaker:** no
    
    ## Before you start
    
    This style runs on the **video-studio-core** skill, which must be installed in the same skills folder.
    
    - `CORE` = the `video-studio-core` folder next to this one (e.g. `~/.claude/skills/video-studio-core`).
    - `STYLE` = this skill's folder (it holds `theme.json` and `theme.css`).
    - First time on a machine: `python CORE/scripts/check_env.py`, and fix anything it reports.
    - If `CORE` is missing, tell the user to install `video-studio-core` from the same pack.
    
    ## Make the edit
    
    ```bash
    python CORE/scripts/run.py clip.mp4 --style STYLE --work edit-tutorial-steps --stop-after plan --clip screen.mp4
    # refine edit-*/plan.json (see below), then check stills:
    python CORE/scripts/render.py edit-tutorial-steps/plan.json --frames 1,3,6,9
    python CORE/scripts/render.py edit-tutorial-steps/plan.json
    python CORE/scripts/finish.py edit-tutorial-steps/plan.json
    ```
    
    Open `contact_sheet.png` and look at it before the full render. The final video is `final.mp4` in the work folder.
    Use `--formats 1:1,16:9` on `finish.py` for extra sizes. Add music with `"music": {"src": "track.mp3", "volume": 0.12}` in the plan.
    
    ## The look
    
    - Screen recording is the main picture; face bubble bottom-right. Step banner top-left changes with each step.
    - Zoom into the part of the screen being discussed using a bigger `clip` with an offset if needed.
    
    ## Refine the plan
    
    The draft from `make_plan.py` is automatic. Make it good:
    
    - Read `words.json` and rewrite the hook (first 2-3 s) into a short, specific promise.
    - Replace weak auto-picked key words with the words that carry the meaning (numbers, results, names, contrasts).
    - Fix any mis-heard words in the `words` array (keep their times).
    - Run with the face-cam clip as the input and `--clip screen.mp4` (make_plan option) for the screen recording. Both must start together.
    - Steps are detected from 'first / step two / next'. Otherwise add `chip` elements with class `ts-step` ('Step 1 · Open settings') at each step start.
    - Add `scribble` circles (kind `box` or `circle`) around buttons the user clicks.
    - Element types and fields: `CORE/references/plan-schema.md`.
    
    ## Check before delivering
    
    - Contact sheet: text readable, nothing cut off, nothing covering the face unless intended, safe zones respected (9:16: keep text between 10% and 85% of the height).
    - Watch for timing: overlays land with the spoken word, not after it.
    - `ffprobe` the final file: right size, duration and audio.
    - Tell the user what you cut (seconds removed), what the look adds, and where the file is.
    
    ## Change the look
    
    Colours and fonts live in `theme.json` (`vars`, `fontsUrl`) and `theme.css`. For a one-off change, edit `plan.json` (`theme.vars`, element `style`) instead of the skill files.
    
    ## Example requests
    
    - "Tutorial edit: my screen with my face in a bubble."
    - "Add step numbers to my software tutorial."
    - "Make a clean how-to video from my screen recording."
    
  • theme.css 250 B · in bundle
  • theme.json 1.2 KB
    Loading…

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.