Telecine Detect
This skill should be used when the user asks "is this interlaced", "detect telecine", "video has combing", "should I deinterlace", "3:2 pulldown", "inverse telecine", or sees horizontal lines/combing artifacts in video and wants to understand if the content is truly interlaced or telecined.
Install
/plugin marketplace add robbyt/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add robbyt/claude-skills --skill telecine-detectgit clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/multimedia/skills/telecine-detect ~/.claude/skills/telecine-detectPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Telecine and Interlacing Detection Detect whether video content is telecined (reversible) or truly interlaced (not reversible), and advise on proper handling. Getting this wrong destroys video quality. ## Critical Distinction **Telecine (3:2 Pulldown)**: - 24fps film content converted to 30fps for NTSC broadcast - Creates repeating pattern of combing across frames - Can be reversed nearly losslessly via IVTC (inverse telecine) - Original 24fps frames can be recovered **True Interlacing**: - Content actually captured at 60 interlaced fields per second - Each field is unique temporal information - Cannot be reversed without quality loss - Deinterlacing merges or discards fields ## The Common Mistake Seeing combing → Immediately running a deinterlacer **Why this is wrong for telecined content**: - Deinterlacers throw away half the vertical resolution - They cannot distinguish telecine from true interlacing - The original 24 progressive frames are lost - Result is a blurry, lower-quality video **Correct approach**: 1. First detect if content is telecined or truly interlaced 2. If telecined → use IVTC to recover original frames 3. If truly interlaced → only then consider deinterlacing ## Detection Workflow ### Step 1: Check MediaInfo Look for these fields: ``` Scan type: Interlaced or Progressive Scan order: Top Field First (TFF) or Bottom Field First (BFF) ```
Details
- Skill name
telecine-detect- Repository
- robbyt/claude-skills
- Path
plugins/multimedia/skills/telecine-detect/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Telecine Detect skill do?
This skill should be used when the user asks "is this interlaced", "detect telecine", "video has combing", "should I deinterlace", "3:2 pulldown", "inverse telecine", or sees horizontal lines/combing artifacts in video and wants to understand if the content is truly interlaced or telecined.
How do I install the Telecine Detect skill?
Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Telecine Detect popular?
It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.
Related skills
Actions
42robbyt/claude-skills
GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").
Adversarial Review
42robbyt/claude-skills
Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (
API Review
42robbyt/claude-skills
This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",
Video Audit
42robbyt/claude-skills
This skill should be used when the user asks to "audit this video", "analyze video quality", "check this video file", "is this video good quality", "should I reencode this", "what format is this video", or wants to understand a video file's technical properties and quality before working with it.
Source Compare
42robbyt/claude-skills
This skill should be used when the user asks "compare these videos", "which source is better", "compare blu-ray vs web", "which release should I use", "compare video quality", or needs to evaluate multiple versions of the same content to determine which has better quality.
Convo Mining
39ShawhinT/non-coding-skills
Mines Shaw's conversational records — meeting transcripts and client Slack channels — into structured Notion databases: what people asked, what they struggled with, and what results they reported. Load it whenever something someone said needs capturing, whenever a transcript or a channel needs mining, and before any read or write against them. Triggers: "log this Q&A", "log this objection", "log this pain point", "log this win", "mine the transcript", "pull the questions from today's call", "what came up in the workshop", "extract the Q&A", "what did X ask", "any repeats", "that quote was gold
Browse the most popular Claude skills, all images, video & audio skills, or write your own with the skills generator.