--- name: seek-and-analyze-video description: "Seek and Analyze Video workflow skill. Use this skill when the user needs Seek and analyze video content using Memories.ai Large Visual Memory Model for persistent video intelligence and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: data-ai tags: ["video", "ai", "memories", "social-media", "youtube", "tiktok", "analysis", "seek-and-analyze-video"] complexity: intermediate risk: safe tools: ["cursor", "codex-cli", "claude-code", "gemini-cli", "opencode"] source: community author: "kennyzheng-builds" date_added: "2026-04-15" date_updated: "2026-04-25" --- # Seek and Analyze Video ## Overview This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/seek-and-analyze-video` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Description, How It Works, Common Pitfalls, Limitations. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Use when analyzing or asking questions about a video from a URL - Use when searching for videos on TikTok, YouTube, or Instagram by topic, hashtag, or creator - Use when summarizing meetings, lectures, or webinars from recordings - Use when building a searchable knowledge base from video content and text memories - Use when researching social media content trends, influencers, or viral patterns - Use when analyzing or describing images with AI vision ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `SKILL.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `SKILL.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 2. Read the overview and provenance files before loading any copied upstream support files. 3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. 4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes. 5. Validate the result against the upstream expectations and the evidence you can point to in the copied files. 6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity. 7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify. ### Imported Workflow Notes #### Imported: Overview The skill wraps 21 API commands into workflow-oriented reference guides that agents load on demand. A routing table in SKILL.md maps user intent to the right workflow automatically. #### Imported: Description This skill enables AI agents to search, import, and analyze video content using Memories.ai's Large Visual Memory Model (LVMM). Unlike one-shot video analysis tools, it provides persistent video intelligence -- videos are indexed once and can be queried repeatedly across sessions. Supports social media import (TikTok, YouTube, Instagram), meeting summarization, knowledge base building, and cross-video Q&A via Memory Augmented Generation (MAG). ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @seek-and-analyze-video to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @seek-and-analyze-video against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @seek-and-analyze-video for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @seek-and-analyze-video using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ### Imported Usage Notes #### Imported: Examples ### Example 1: Video Q&A ``` User: "What are the key arguments in this video? https://youtube.com/watch?v=abc123" Agent: uploads video -> waits for processing -> uses chat_video to ask questions -> presents structured summary ``` ### Example 2: Social Media Research ``` User: "What's trending on TikTok about sustainable fashion?" Agent: uses search_public to find trending videos -> imports top results -> analyzes content patterns ``` ### Example 3: Meeting Notes ``` User: "Summarize this meeting recording and extract action items" Agent: uploads recording -> waits -> gets transcript -> uses chat_video for structured summary with action items ``` ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - Always wait for video processing to complete before querying - Use caption_video for quick analysis (no upload needed) - Use chat_video for deep, multi-turn analysis (requires upload) - Use search_audio to find specific moments or quotes in a video - Use memory_add to store important findings for later retrieval - Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support. - Prefer the smallest useful set of support files so the workflow stays auditable and fast to review. ### Imported Operating Notes #### Imported: Best Practices - Always wait for video processing to complete before querying - Use caption_video for quick analysis (no upload needed) - Use chat_video for deep, multi-turn analysis (requires upload) - Use search_audio to find specific moments or quotes in a video - Use memory_add to store important findings for later retrieval ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/seek-and-analyze-video`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/n/a` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | ### Imported Reference Notes #### Imported: How It Works ### Step 1: Intent Detection The agent reads the SKILL.md workflow router and matches the user's request to one of 6 intent categories. ### Step 2: Reference Loading The agent loads the appropriate reference file (e.g., video_qa.md for video questions, social_research.md for social media research). ### Step 3: Workflow Execution The agent follows the step-by-step workflow: upload/import -> wait for processing -> analyze/chat -> present results. #### Imported: Common Pitfalls - **Problem:** Querying a video before processing completes **Solution:** Always use the `wait` command after upload before any analysis - **Problem:** Uploading a video when only a quick caption is needed **Solution:** Use `caption_video` for one-off analysis; only upload for repeated queries #### Imported: Limitations - Video processing takes 1-5 minutes depending on length - Free tier limited to 100 credits - Social media import requires public content - Audio search only works on processed videos