From twelvelabs
Index video files or URLs for AI search and analysis. Use when user wants to add a video for processing, says "index this video", "add this video for analysis", or mentions a video file they want to work with.
npx claudepluginhub twelvelabs-io/twelve-labs-claude-code-pluginThis skill uses the workspace's default tool permissions.
Index local video files or remote URLs for AI search and analysis using TwelveLabs. Once indexed, videos can be searched with natural language and analyzed to generate summaries, chapters, highlights, and more.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.
Index local video files or remote URLs for AI search and analysis using TwelveLabs. Once indexed, videos can be searched with natural language and analyzed to generate summaries, chapters, highlights, and more.
Use this skill when the user:
Extract the video path or URL from the user's message:
/path/to/video.mp4, ./video.mp4, ~/Videos/demo.movhttps://example.com/video.mp4https://drive.google.com/file/d/FILE_ID/viewIf no path/URL is provided, ask the user:
Please provide the video file path or URL you'd like to index.
Examples:
- Local file: /path/to/video.mp4 or ./video.mp4
- Remote URL: https://example.com/video.mp4
- Google Drive: https://drive.google.com/file/d/FILE_ID/view
For Local Files:
.mp4, .mov, .avi, .mkv, .webmValidation errors:
<path>. Please check the path and try again."<extension>. Supported formats: mp4, mov, avi, mkv, webm"For URLs:
http:// or https://Use the mcp__twelvelabs-mcp__start-video-indexing-task tool:
For Local Files:
Tool: mcp__twelvelabs-mcp__start-video-indexing-task
Parameters:
videoFilePath: "<absolute-path-to-video>"
For URLs (including Google Drive):
Tool: mcp__twelvelabs-mcp__start-video-indexing-task
Parameters:
videoUrl: "<url>"
Google Drive Notes:
On success (single video):
Video indexing started!
Source: <filename-or-url>
Task ID: <task_id>
Indexing runs in the background and may take several minutes depending on video length.
Ask "is my video ready?" to check the indexing progress.
On success (Google Drive folder):
Video indexing started for Google Drive folder!
Multiple indexing tasks started:
- Task ID: <task_id_1> - <filename_1>
- Task ID: <task_id_2> - <filename_2>
Ask "is my video ready?" to check indexing progress for all tasks.
On failure: Report the error message from the API with helpful context.
User: "Index this video: /Users/me/Videos/demo.mp4" Action: Validate file exists → call start-video-indexing-task with videoFilePath
User: "I want to search this video https://example.com/video.mp4" Action: Call start-video-indexing-task with videoUrl
User: "Add this Google Drive folder for analysis: https://drive.google.com/drive/folders/ABC123" Action: Call start-video-indexing-task with videoUrl (handles folder automatically)
User: "Process my meeting recording" Action: Ask for the file path or URL