YouTube Analytics

## Quick judgement A solid YouTube Data API v3 analytics toolkit that aligns well with common “analyze this channel/video” and “compare channels” use cases. It’s particularly well-suited when you need structured, programmatic YouTube stats plus saved artifacts (JSON + markdown summaries) for later analysis. The main dependencies and risks revolve around correct API key configuration, Google quota limits, and the constraints of the YouTube Data API itself. --- ## What this skill is good for - **Channel analytics:** End-to-end analysis of a channel’s basic profile, recent uploads, and average performance via `analyzeChannel()`. - **Video performance analysis:** Per-video engagement metrics (views, likes, comments, like rate, comment rate) via `analyzeVideo()`. - **Competition and benchmarking:** Side-by-side comparisons of multiple channels with `compareChannels()` for subscribers, views, and video counts. - **Search + insight workflows:** Use `searchAndAnalyze()` to find videos for a topic and automatically enrich them with stats, enabling “find strong performers in this niche” type queries. - **Result management and re-use:** Auto-saves JSON to `results/{channels|videos|search}/` and generates markdown summaries in `results/summaries/`, which is useful for reporting, audits, or re-running analyses. --- ## Key strengths - **Clear mapping from user intent to functions:** Phrases like *“Analyze this channel”*, *“Compare these two channels”*, or *“Search YouTube for [topic]”* are explicitly mapped to concrete functions (`analyzeChannel`, `compareChannels`, `searchAndAnalyze`, etc.). This is ideal for tool-calling agents. - **Reasonable coverage of analytics needs:** Includes channel stats, video stats, search (videos and channels), and comparison utilities. Batch endpoints (`getMultipleChannels`, `getMultipleVideos`) support higher-volume or multi-entity analysis use cases. - **Structured output and summaries:** Raw JSON results plus markdown table summaries give both machine-readable and human-readable views. This is helpful for follow-up questions, reporting, and iterating on insights. - **Good operational guidance:** Documentation clarifies how to obtain channel IDs, how results are named, and how to access the latest or specific results. --- ## Notable limitations & risks 1. **External dependency on YouTube Data API v3** - Requires a valid **API key** and a **Google Cloud project** with the YouTube Data API enabled. - Subject to **quota limits**, rate limits, and potential API changes or outages. 2. **Metrics scope is limited to the Data API** - Focused on basic public metrics (views, subscribers, likes, comments, etc.). - Does **not** appear to expose deeper YouTube Analytics metrics such as audience retention, watch time, CTR, or demographics. 3. **Environment and file system expectations** - Expects a `.env` file with `YOUTUBE_API_KEY` and writes to a `results/` directory on the filesystem. - In constrained or ephemeral environments, the auto-save behavior may be partially ineffective or require special configuration. 4. **Error handling and robustness not fully specified** - Docs don’t detail behavior on API errors, invalid IDs, or quota exhaustion. - Reliability may depend heavily on how the calling environment surfaces and handles these failure modes. 5. **Requires correct identifiers or queries** - For some operations, the caller must know channel IDs (typically starting with `UC`), which may add friction if not combined with search flows. --- ## Recommended scenarios Use this skill when: - A user explicitly asks to **analyze YouTube channels or videos**, including engagement and basic performance. - The task involves **comparing channels** (competitors or alternatives) on subscribers, total views, and output volume. - You need to **search YouTube for a topic** and then evaluate which videos or channels are performing best. - You want to **persist** analysis results as JSON and generate markdown **reports/summaries** that can be referenced in later conversations or external workflows. Be cautious or consider alternatives when: - You need **advanced analytics** not exposed by the YouTube Data API v3 (e.g., watch time, retention curves, per-traffic-source metrics). - You cannot safely or reliably provide a **YouTube API key** or persistent filesystem access. - You have very tight **quota** constraints and need extensive bulk analysis beyond what a single key reasonably supports.