Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计提醒

keyapi-youtube-video-analysiskeyapi youtube 视频分析

Agent Skill

用于辅助视频生成、动画合成、脚本化剪辑或 Remotion 等视频项目开发。它适合让 Agent 组织镜头、生成素材说明、维护合成代码或排查渲染问题。使用时需要确认分辨率、时长、素材路径和导出格式;涉及外部素材、人物肖像或商业发布时,应先核对版权授权和内容审核要求。

总安装

1,999

周安装

85

GitHub Stars

公开资料未说明

下载量

510
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:keyapi-youtube-video-analysis(keyapi youtube 视频分析)
来源仓库:https://github.com/lycici/keyapi-youtube-video-analysis
安装命令:
openclaw skills install keyapi-youtube-video-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install keyapi-youtube-video-analysis

简介

用于深度分析 YouTube 视频完整元数据、评论层级结构与相关视频推荐列表。

  • 适合在 OpenClaw 中研究爆款视频要素、优化 SEO 标题或策划系列内容时使用。
  • 支持获取流格式信息与 Shorts 内容关联图谱,输出观看行为洞察。
  • 安装命令:openclaw skills install keyapi-youtube-video-analysis。
  • 视频数据量较大时响应较慢,建议分批处理以提高效率。

SKILL.md

name
keyapi-youtube-video-analysis
description
Analyze YouTube videos at depth — retrieve full metadata, comments, sub-comment threads, stream formats, related video recommendations, Shorts, search results, and trending content across categories.
metadata
{"openclaw":{"requires":{"env":["KEYAPI_TOKEN"],"bins":["node"]},"primaryEnv":"KEYAPI_TOKEN","emoji":"🎬"}}
author
KeyAPI
license
MIT
repository
https://github.com/EchoSell/keyapi-skills

keyapi-youtube-video-analysis

Analyze YouTube videos at depth — from full metadata and stream formats to comment threads, related recommendations, Shorts discovery, and trending video intelligence.

This skill provides comprehensive YouTube video intelligence using the KeyAPI MCP service. It enables detailed video inspection (metadata, views, engagement), layered comment analysis (top-level comments + nested replies), playback stream retrieval, related content discovery, Shorts-specific search, keyword-based video search, and trending video monitoring — all through a cache-first workflow.

Use this skill when you need to:

  • Retrieve complete metadata, engagement metrics, and raw player data for any YouTube video
  • Read and analyze top-level comments and their nested reply threads
  • Obtain all available playback stream URLs and quality levels for a video
  • Discover related and recommended videos as surfaced by the YouTube algorithm
  • Search YouTube Shorts by keyword with category and time-based filtering
  • Find videos by keyword with advanced sort and recency filters
  • Monitor trending videos globally or by category (Music, Gaming, Movies)

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Prerequisites

RequirementDetails
KEYAPI_TOKENA valid API token from keyapi.ai. If you don't have one, register at the site to obtain your free token. Set it as an environment variable: export KEYAPI_TOKEN=your_token_here
Node.jsv18 or higher
DependenciesRun npm install in the skill directory to install @modelcontextprotocol/sdk

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


MCP Server Configuration

All tool calls in this skill target the KeyAPI YouTube MCP server:

Server URL : https://mcp.keyapi.ai/youtube/mcp
Auth Header: Authorization: Bearer $KEYAPI_TOKEN

Setup (one-time):

# 1. Install dependencies
npm install

# 2. Set your API token (get one free at https://keyapi.ai/)
export KEYAPI_TOKEN=your_token_here

# 3. List all available tools to verify the connection
node scripts/run.js --platform youtube --list-tools

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Analysis Scenarios

Video Data Nodes

User NeedNode(s)Best For
Full video metadata, stats, and raw player dataget_video_informationComplete video audit — title, description, views, likes, tags, chapters, playerResponse + initialData
Video comments (top-level)get_video_commentsAudience sentiment, comment volume analysis — sortable by top or newest
Replies to a specific commentget_video_sub_commentsNested conversation thread analysis — requires reply_continuation_token from a comment
All playback stream URLs and quality levelsget_video_streams_infoDownload URL extraction, quality enumeration (standard merged + adaptive formats)
Related / recommended videosget_related_videosAlgorithm-surfaced content map — returns 20–30 recommendations in one call

Search & Discovery Nodes

User NeedNode(s)Best For
Search YouTube Shorts by keywordyoutube_shorts_searchShorts-specific content research — use continuation_token for pure Shorts after first call
Search regular videos by keywordsearch_videoGeneral video discovery with recency filter (this_week / this_month / this_year / last_hour / today)
Get trending videos by categoryget_trending_videosMarket pulse — categories: Now (default), Music, Gaming, Movies

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Workflow

Step 1 — Identify the Video Analysis Objective and Select Nodes

Clarify the research goal and map it to one or more nodes. Common patterns:

  • Video deep-dive: Start with get_video_information (set need_format: true for clean structured output), then layer get_video_comments and get_video_streams_info.
  • Comment thread analysis: get_video_comments → collect reply_continuation_token from comments with replies → get_video_sub_comments per thread.
  • Related content mapping: get_related_videos returns the full recommendation set in one call — no pagination needed.
  • Shorts research: youtube_shorts_search with keyword → use continuation_token for pure Shorts on subsequent pages.
  • Trend monitoring: get_trending_videos with section filter → cross-reference with search_video by keyword.
Video ID extraction Extract the video ID from the URL: - https://www.youtube.com/watch?v=oaSNBz4qMQYoaSNBz4qMQY Most endpoints accept either video_id (recommended) or video_url (full URL string) — use video_id where possible for reliability.

Step 2 — Retrieve API Schema

Before calling any node, inspect its input schema to confirm required parameters and available options:

node scripts/run.js --platform youtube --schema <tool_name>

# Examples
node scripts/run.js --platform youtube --schema get_video_information
node scripts/run.js --platform youtube --schema youtube_shorts_search

Step 3 — Call APIs and Cache Results Locally

Execute tool calls and persist responses to the local cache.

Calling a tool:

node scripts/run.js --platform youtube --tool <tool_name> \
  --params '<json_args>' --pretty

# Skip cache for fresh results
node scripts/run.js --platform youtube --tool <tool_name> \
  --params '<json_args>' --no-cache --pretty

Example — get full video information (formatted):

node scripts/run.js --platform youtube --tool get_video_information \
  --params '{"video_id":"oaSNBz4qMQY","need_format":true,"language_code":"en-US"}' --pretty

Example — get top comments:

node scripts/run.js --platform youtube --tool get_video_comments \
  --params '{"video_id":"oaSNBz4qMQY","sort_by":"top","language_code":"en-US","country_code":"US"}' --pretty

Example — paginate to next comment page:

node scripts/run.js --platform youtube --tool get_video_comments \
  --params '{"video_id":"oaSNBz4qMQY","continuation_token":"<token_from_previous_response>"}' --pretty

Example — get replies to a comment:

# Extract reply_continuation_token from a comment in get_video_comments response
node scripts/run.js --platform youtube --tool get_video_sub_comments \
  --params '{"continuation_token":"<reply_continuation_token>","language_code":"en-US"}' --pretty

Example — get related videos:

node scripts/run.js --platform youtube --tool get_related_videos \
  --params '{"video_id":"dQw4w9WgXcQ","need_format":true}' --pretty

Example — search Shorts:

# First call (may return mixed content)
node scripts/run.js --platform youtube --tool youtube_shorts_search \
  --params '{"search_query":"cooking tips","filter_mixed_content":true,"language_code":"en-US","country_code":"US"}' --pretty

# Subsequent pages (pure Shorts via continuation_token)
node scripts/run.js --platform youtube --tool youtube_shorts_search \
  --params '{"search_query":"cooking tips","continuation_token":"<token>"}' --pretty

Example — search videos with recency filter:

node scripts/run.js --platform youtube --tool search_video \
  --params '{"search_query":"AI tutorial","order_by":"this_month","country_code":"US","language_code":"en"}' --pretty

Example — get trending videos:

node scripts/run.js --platform youtube --tool get_trending_videos \
  --params '{"section":"Music","country_code":"US","language_code":"en"}' --pretty

Pagination:

EndpointPaginationNotes
get_video_commentscontinuation_tokenFrom previous response
get_video_sub_commentscontinuation_tokenMust use reply_continuation_token field from a comment — NOT the video comment pagination token
youtube_shorts_search, search_videocontinuation_tokenFrom previous response
get_video_information, get_video_streams_info, get_related_videos, get_trending_videosSingle-call; no pagination
get_video_sub_comments critical note: This endpoint requires the reply_continuation_token field extracted from a specific comment in the get_video_comments response — it is different from the comment-level continuation_token used to paginate comments. Do NOT pass the video_id to this endpoint.
get_video_streams_info time limit: Returned playback URLs are valid for approximately 6 hours. Use them promptly. HD video (720p+) streams require separate audio and video downloads that must be merged locally.
youtube_shorts_search mixed content: The first request may return a mix of Shorts and regular videos. Use continuation_token on subsequent calls for pure Shorts results. Set filter_mixed_content: true (default) to filter long videos from the first response.

Cache directory structure:

.keyapi-cache/
└── YYYY-MM-DD/
    ├── get_video_information/
    │   └── {params_hash}.json
    ├── get_video_comments/
    │   └── {params_hash}.json
    ├── get_video_sub_comments/
    │   └── {params_hash}.json
    ├── get_video_streams_info/
    │   └── {params_hash}.json
    ├── get_related_videos/
    │   └── {params_hash}.json
    ├── youtube_shorts_search/
    │   └── {params_hash}.json
    ├── search_video/
    │   └── {params_hash}.json
    └── get_trending_videos/
        └── {params_hash}.json

Cache-first policy:

Before every API call, check whether a cached result already exists. If valid, load from disk and skip the API call.

Step 4 — Synthesize and Report Findings

For video analysis:

  1. Video Overview — Title, channel, publish date, view count, like count, comment count, duration, tags, description summary.
  2. Engagement Quality — Like-to-view ratio, comment depth (replies per top-level comment), engagement rate estimate.
  3. Comment Intelligence — Top themes from most-liked comments, sentiment signals, key community questions or reactions.
  4. Related Content Map — Algorithm-recommended videos, common topics and channels in the recommendation cluster.
  5. Stream Quality Summary — Available resolutions, format types (merged vs. adaptive), playback URL validity window.

For search / discovery:

  1. Search Results Overview — Video count returned, top titles, channel distribution, view spread.
  2. Shorts Landscape — Trending Shorts topics, creator diversity, engagement patterns.
  3. Trending Signals — Top trending videos by category, creator names, view velocity indicators.

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Common Rules

RuleDetail
Video ID extractionExtract from URL: youtube.com/watch?v=VIDEO_ID. Use video_id parameter where available; video_url is also accepted by get_video_streams_info and get_related_videos.
get_video_sub_commentsRequires continuation_token from the reply_continuation_token field of a comment returned by get_video_comments — not the video-level pagination token and not the video ID.
Shorts first-call behaviorThe first youtube_shorts_search call may return mixed content. Use continuation_token for subsequent pages to receive pure Shorts. Use filter_mixed_content: true to auto-filter on the first call.
Stream URL validityget_video_streams_info returns time-limited URLs (~6 hours). Process immediately after retrieval.
need_format parameterAvailable on get_video_information, get_related_videos, and get_video_comments. Set to true for structured, cleaned output; false for raw YouTube API data useful for debugging.
Language / region paramslanguage_code and country_code influence result language and regional content bias. Use en-US / US for English-language global results.
Success checkcode = 0 → success. Any other value → failure. Always check the response code before processing data.
Retry on 500If code = 500, retry the identical request up to 3 times with a 2–3 second pause between attempts before reporting the error.
Cache firstAlways check the local .keyapi-cache/ directory before issuing a live API call.

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Error Handling

CodeMeaningAction
0SuccessContinue workflow normally
400Bad request — invalid or missing parametersValidate input against the tool schema; check video_id format, continuation_token source, and required fields
401Unauthorized — token missing or expiredConfirm KEYAPI_TOKEN is set correctly; visit keyapi.ai to renew
403Forbidden — plan quota exceeded or feature restrictedReview plan limits at keyapi.ai
404Resource not found — video may be deleted, private, or region-restrictedVerify the video ID; the content may no longer be available
429Rate limit exceededWait 60 seconds, then retry
500Internal server errorRetry up to 3 times with a 2–3 second pause; if it persists, log the full request and response and skip this node
Other non-0Unexpected errorLog the full response body and surface the error message to the user

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

70.77%
按下载量换算361

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills