Skip to content
Skills Library
Management & product · Analysis

video-notes

/video-notes

Turn a narrated screen recording, a product demo or any video the user points at into a timestamped, numbered punch list with stills, all on this machine. Use when the user says "check the video file", "I left feedback as a video", "I recorded feedback", "watch this video", "analyze this demo", or drops a .mov, .mp4 or .webm path.

Repository
video-notes ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: video-notes.py

What it does and when to use it

Turn a narrated screen recording, a product demo or any video the user points at into a timestamped, numbered punch list with stills, all on this machine. Use when the user says "check the video file", "I left feedback as a video", "I recorded feedback", "watch this video", "analyze this demo", or drops a .mov, .mp4 or .webm path.

Triggers from the description

check the video fileI left feedback as a videoI recorded feedbackwatch this videoanalyze this demo
Original author description

Turn a narrated screen recording, a product demo or any video the user points at into a timestamped, numbered punch list with stills, all on this machine. Use when the user says "check the video file", "I left feedback as a video", "I recorded feedback", "watch this video", "analyze this demo", or drops a .mov, .mp4 or .webm path.

How it works

  1. Steps
  2. Rules
  3. Done check
Original SKILL.md headings · 67 lines, 607 words
SKILL.md preview
---
name: video-notes
description: Turn a narrated screen recording, a product demo or any video the user points at into a timestamped, numbered punch list with stills, all on this machine. Use when the user says "check the video file", "I left feedback as a video", "I recorded feedback", "watch this video", "analyze this demo", or drops a .mov, .mp4 or .webm path.
---

# Video Notes

The user records feedback as a screen recording while talking through it: one pass, a few
minutes, often repeating a point when the cursor lags. The deliverable is a punch list another
session can execute without watching the video. Whisper and ffmpeg run locally; no video or
audio is sent to a cloud speech or vision API.

## Steps

1. **Run the helper** (it sits next to this file).
   ```bash
   python3 "<this skill's folder>/video-notes.py" "<video>"
   ```
   It reuses `<video>.srt` when one sits next to the file, otherwise runs `whisper --model base.en`
   on CPU (about 2.5 min per 5 min of video on an Apple Silicon laptop). Output lands in
   `<stem>.notes/`: `transcript.md` (one row per merged segment with a frame name) and 1600px
   stills. When `<stem>.notes/` is already newer than the video it is reused as is; `--force`
   rebuilds, `--model turbo` when the base transcript is garbled, `--every 10` for a demo with no
   narration, `--sheet` for 2x2 contact sheets, `--max-row 5` for more frames when talk and
   screen move fast (rows are capped at 8 s, one frame per row), `--max-frames 40` default.
2. **Read `transcript.md`, then the frames.** With `--sheet`, skim `sheet_NN.jpg` first (four frames
   per read; tiles run left to right, top to bottom, in frame order, so sheet 01 holds frames 1 to 4
   and its top-left tile is the earliest), then read the single frame for every row whose words point
   at the screen ("this area", "here", "these two icons") or whose text must be read. A sheet
   locates; only a single frame is evidence for a label or a size.
3. **Write `<stem>.notes.md` next to the video**, by absolute path, whatever the session's working
   directory is. Shape:
   ```
   # <video name> · <recorded date> · <duration> · <app or URL visible in the frames>

   ## Punch list
   ### <screen region, named as it reads on screen: Left rail, Header, Settings panel>
   1. [mm:ss] <imperative fix in one sentence>. Said: "<short verbatim>". Frame: frame_mmss.jpg
   2. ...

   ## Parked
   <items marked "later", "eventually", "not now", same line shape>

   ## Unclear
   <one line per item that needs the user's answer>
   ```
   Numbering runs through the whole list, so the user can reply "3 and 7". Regions follow the
   order they were visited. A repeated note is one item, with "said 3 times" appended when the
   repetition is the point.
4. **Reply with** the file path, the region headers with item counts, and the first three items.
   Ask nothing unless Unclear has entries.
5. **When the repo that renders the screen is open**, add `## Where in code`: item number to
   file path, found by grepping the component names and labels visible in the frames. Skip the
   section when there is no repo; never guess a path.

## Rules

- Unreadable text in a still is re-grabbed, never inferred: `--width 2400`, or an ffmpeg crop of
  the region.
- The `.notes/` folder and `.notes.md` stay next to the video. Inside a repo that folder must be
  ignored (`.git/info/exclude`), so a large recording never enters git.
- Competitor or product demo: same steps, and the list reads "what they do" instead of "fix".
- Transcription runs with the local Whisper models in `~/.cache/whisper`. No cloud speech API,
  no vision API; the session model reads the stills.

## Done check
- [ ] `transcript.md` produced and every frame read before an item was written
- [ ] `<stem>.notes.md` written: global numbering, regions in visit order, timestamp and frame on every item
- [ ] Repeats collapsed, Parked and Unclear separated from the punch list
- [ ] No video or audio sent off the machine
Files in this package (2)
  • SKILL.md 4 KB
  • video-notes.py 9 KB

Versions

RepositoryScoreLicence
This page · weeeha/video-notes100MIT
endgame302/video-notes100MIT
kyoukawa/agent-system100MIT

Database snapshot: 13.11.2026 · package version d1848974d686 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90recorded-feedback-analysis
    Use when asked to analyze a screen recording, voice capture, or meeting notes artifact for product feedback. Not for credential, publish, deploy, or irreversible changes.
  • 95app-demo-agent
    Use this skill to turn screen recordings into polished app demo videos with AI voiceover and music. Triggers: "app demo", "demo video from recording", "screen recording demo", "narrate this recording", "add voiceover to screen recording", "make a demo from this recording",…
  • 100watch-video
    Use when the user asks Claude to watch, understand, summarise, break down, or answer questions about a video or screen recording (local file or URL, e.g. mp4/mov/webm, YouTube, Zoom/Meet/Loom recordings, demos, tutorials), or to find what was shown or said at a moment in one.
  • 100transcribe-audio
    Transcribe an audio or video file to text locally, on this machine, using whisper.cpp. Use whenever the user points at a recording and wants words out of it. Triggers include: 'transcribe this', 'transcribe this interview', 'what does this recording say', 'turn this audio into…
  • 100feature-demo-recording
    Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user…
  • 100product-demo-video
    Workflow for product demo and feature walkthrough videos: preparing a clean demo environment, recording the screen (manually or with scripted Playwright browser recordings), editing the recording, and adding motion overlays such as zooms, callouts, titles, and captions. Use this…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.