Install any skill in seconds. Free to start, no credit card required.
Get Started Free →動画ファイルからキーフレームを抽出し、重複除去・最適化した上で内容を分析するスキル。 「動画の中身を見て」「キーフレームを抽出」「この動画を分析して」等で発動。
.claude/skills/minicoohei-video-frame-reader/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-18 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -23% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 29% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -9% | 0% |
Extract keyframes from video, present token cost, then analyze.
Clearly understand why the user wants the video analyzed:
This intent becomes important context for the analysis.
bash# uv で依存関係をインストール uv add Pillow numpy --quiet
bashuv run python skills/video-frame-reader/scripts/extract_keyframes.py "<video_path>"
Output example (JSON):
json{ "keyframe_count": 52, "image_size": "266x576", "total_tokens": 10400, "cost_usd_opus": 0.156, "cost_usd_sonnet": 0.031, "cost_usd_haiku": 0.0104, "files": ["/.../key_0001.jpg", ...] }
After extraction, present the following to the user:
Keyframe extraction complete:
- Frames extracted: {keyframe_count}
- Image size: {image_size}
- Estimated tokens: {total_tokens}
- Cost estimate: Haiku ${cost_usd_haiku} / Sonnet ${cost_usd_sonnet} / Opus ${cost_usd_opus}
Proceed with frame analysis?After user approval, invoke subagent using Task tool:
Task(
subagent_type="general-purpose",
model="haiku",
description="Frame analysis",
prompt="""
[User Intent]
{Intent captured in Step 1}
[Frame Image Files]
{List of paths from files array}
Analyze the above frame images and identify issues/behaviors according to the user's intent.
"""
)Benefits of this approach:
| Option | Default | Description | |--------|---------|-------------| | -t, --threshold | 0.85 | Similarity threshold (higher = more frames kept) | | -q, --quality | 30 | JPEG quality (1-100) | | -s, --scale | 0.3 | Resize scale | | -o, --output | <video_name>_keyframes/ | Output directory |
bash# More aggressive reduction (lower threshold, quality, and size) python3 extract_keyframes.py video.mp4 -t 0.75 -q 20 -s 0.2
動画ファイルからキーフレームを自動抽出し、重複除去・最適化した上で内容を分析するスキルです。トークンコストを事前提示し、ユーザー承認後にサブエージェントで分析を実行します。
| エラー | 解決方法 | |--------|---------| | ffmpeg not found | brew install ffmpeg(Mac)または apt install ffmpeg(Linux)でインストール | | No keyframes extracted | --threshold を下げる(例: 0.75)ことでより多くのフレームを抽出 |
上記「Workflow」セクションを参照。基本例:
bash# キーフレーム抽出 python3 skills/video-frame-reader/scripts/extract_keyframes.py "video.mp4" # トークン削減オプション付き python3 skills/video-frame-reader/scripts/extract_keyframes.py "video.mp4" -t 0.75 -q 20 -s 0.2
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 6,741 | 5,293 | -21% | 1 | 1 | 0% | 434 | 1,309 | +202% | 0 | 0 | — |
case-02 | fail→fail | 2,877 | 5,513 | +92% | 1 | 1 | 0% | 433 | 1,288 | +197% | 0 | 0 | — |
case-03 | fail→fail | 3,193 | 6,409 | +101% | 1 | 1 | 0% | 388 | 1,347 | +247% | 0 | 0 | — |
case-04 | pass→pass | 10,585 | 11,963 | +13% | 1 | 1 | 0% | 2,030 | 3,162 | +56% | 0 | 0 | — |
case-05 | pass→fail | 9,171 | 6,756 | -26% | 1 | 1 | 0% | 1,616 | 1,305 | -19% | 0 | 0 | — |
case-18 | fail→pass | 11,524 | 2,151 | -81% | 1 | 1 | 0% | 1,886 | 1,357 | -28% | 0 | 0 | — |
case-06 | pass→fail | 7,079 | 9,032 | +28% | 1 | 1 | 0% | 1,370 | 1,399 | +2% | 0 | 0 | — |
case-07 | fail→pass | 12,961 | 5,237 | -60% | 1 | 1 | 0% | 2,482 | 1,907 | -23% | 0 | 0 | — |
case-08 | fail→pass | 8,834 | 1,737 | -80% | 1 | 1 | 0% | 1,519 | 1,275 | -16% | 0 | 0 | — |
case-09 | pass→pass | 9,158 | 2,340 | -74% | 1 | 1 | 0% | 1,667 | 1,326 | -20% | 0 | 0 | — |
case-10 | pass→pass | 3,088 | 2,417 | -22% | 1 | 1 | 0% | 506 | 1,331 | +163% | 0 | 0 | — |
case-11 | pass→pass | 11,917 | 4,997 | -58% | 1 | 1 | 0% | 1,902 | 1,756 | -8% | 0 | 0 | — |
case-12 | fail→pass | 5,864 | 1,382 | -76% | 1 | 1 | 0% | 905 | 1,164 | +29% | 0 | 0 | — |
case-13 | fail→pass | 7,957 | 1,615 | -80% | 1 | 1 | 0% | 1,365 | 1,240 | -9% | 0 | 0 | — |
case-14 | pass→pass | 8,562 | 1,630 | -81% | 1 | 1 | 0% | 1,403 | 1,190 | -15% | 0 | 0 | — |
case-15 | pass→pass | 10,501 | 2,547 | -76% | 1 | 1 | 0% | 1,661 | 1,416 | -15% | 0 | 0 | — |
case-16 | fail→pass | 8,260 | 3,317 | -60% | 1 | 1 | 0% | 1,265 | 1,536 | +21% | 0 | 0 | — |
case-17 | pass→pass | 8,845 | 1,837 | -79% | 1 | 1 | 0% | 1,549 | 1,281 | -17% | 0 | 0 | — |
case-19 | pass→pass | 7,292 | 2,244 | -69% | 1 | 1 | 0% | 1,296 | 1,345 | +4% | 0 | 0 | — |
case-20 | fail→pass | 4,316 | 1,549 | -64% | 1 | 1 | 0% | 695 | 1,180 | +70% | 0 | 0 | — |
case-21 | fail→pass | 8,024 | 2,040 | -75% | 1 | 1 | 0% | 1,376 | 1,254 | -9% | 0 | 0 | — |
case-22 | fail→pass | 5,857 | 2,061 | -65% | 1 | 1 | 0% | 996 | 1,359 | +36% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 17 counted toward the lift figure. The other 5 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +32 percentage points is the difference between those two pass rates over the 17 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.