youtube
/youtube
Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights — views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos.
- Author
- windsor-ai ↗
- Repository
- claude-windsor-ai-plugin ↗
- Licence
- MIT
- Last repository change
- 09.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights — views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos.
Original author description
Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights — views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos.
How it works
- 1. Ground yourself first
- 2. Reading YouTube data
- 3. Reference real data, don't fabricate
SKILL.md preview
--- name: youtube description: Analyze YouTube channel, playlist, and video performance through Windsor.ai. Use when the user asks about their YouTube channel's organic insights — views, watch time, average view duration, subscribers gained and lost, likes, comments, shares, or traffic sources, at the channel, playlist, or video level (including comparing Shorts vs. regular videos). Do not use for YouTube Ads, other platforms, or publishing or editing videos. --- # YouTube via Windsor.ai Windsor.ai pulls YouTube channel, playlist, and video analytics from the YouTube Analytics API. The connector id is `youtube`. Pass `youtube` as the connector on every tool call; the Windsor.ai server serves all connectors, so it is never implied. This connector is **read-only** YouTube analytics. It has **no ad or cost data** (YouTube Ads run through Google Ads, so route ad-spend questions there), and it does **not** publish or edit videos or change channel settings — there are no write actions. If asked to upload, edit, or manage videos, say that's out of scope here. Golden rules: - **Never guess field, account, or option names** — get them from `get_fields`, `get_connectors`, and `get_options`. Call those first. - Read-only connector; there are no live write actions to run. - Report what the user asked for, concisely. ## 1. Ground yourself first Call `get_connectors` to see which YouTube channels are connected (each has an id and usually a channel name). If none is connected, help the user connect: call `get_connector_authorization_url` (or `get_connector_connect_info` for the auth type and steps) and give them the setup link — don't describe manual dashboard navigation. If several channels are connected and the request is ambiguous, ask which one. ## 2. Reading YouTube data 1. Call `get_fields` for `youtube` to get valid field ids — channel, playlist, and video metrics (views, watch time, average view duration, subscribers gained and lost, likes, comments, shares) and dimensions (e.g. video title, content type, traffic source). Use the exact ids returned, not these examples. 2. If the analysis needs segmentation controls, call `get_options` to see the connector's options and valid values. 3. Call `get_data` with `fields`, the target `account`(s) (channel), and a date range (`date_from`/`date_to` or a `date_preset` like `last_7d`, `last_30d`, `last_Xd`/`last_Xw`/`last_Xm`, `this_month`, `this_year`, `last_year`; append `T` to include today, e.g. `last_30dT`). For ranges without a preset (e.g. "this quarter"), compute explicit `date_from`/ `date_to`. Add `filters` as needed, e.g. to isolate Shorts vs. regular videos. Common requests → recipe: - **Channel overview / trend:** fields `date` + the metrics, over a preset range. - **Top / worst videos:** fields `video` (or video title) + the metric (e.g. watch time), then rank; return only what was asked. - **Shorts vs. regular videos:** fields for content type/format + the metric (e.g. average view percentage), grouped by format. - **Traffic sources:** fields for traffic source + views, over the requested range. If a metric the user wants isn't in `get_fields`, say so rather than substituting a different one. There is no cost/spend data here, and YouTube Ads questions belong in the Google Ads connector. ## 3. Reference real data, don't fabricate On an error (unknown field/connector/account), call the relevant discovery tool and retry with correct ids, or report the specific error. Never invent view counts, subscriber numbers, watch-time figures, or video ids.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · windsor-ai/claude-windsor-ai-plugin | 100 | MIT |
| AceDataCloud/Skills | 100 | Apache-2.0 |
| PhiDuyAnh/learning-with-ai-kit | 100 | MIT |
| cowork-os/cowork-os | 100 | MIT |
| hackers-reality/youtube-skillbox | 100 | MIT |
| hyperfx-ai/marketing-skills | 100 | MIT |
| baofeng-tech/agent-skills | 100 | MIT |
| teenxgrailed/needt-plugin | 100 | MIT |
| tikhub/tikhub-plugin | 100 | MIT |
Database snapshot: 13.11.2026 · package version e1bdd5b2471a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100youtube-stats
How published videos are doing on YouTube, and what to learn from it. Views, likes, comments and subscribers per video, plus watch time, retention and traffic sources (Shorts feed, search, external) with the Analytics scope, saved as snapshots so trends show; GitHub traffic… - 100youtube-analytics
Analyze YouTube channel and video performance using the YouTube Data API. Use when the user says "YouTube analytics", "check my channel", "video performance", "YouTube stats", "channel analysis", "compare YouTube channels", "YouTube SEO", or asks about YouTube metrics, views,… - 100tiktok-organic
Analyze TikTok account (organic) performance through Windsor.ai. Use when the user asks about their TikTok personal or business account's organic insights — video views, likes, comments, shares, followers, profile views, or audience breakdowns by country, age, gender, or active… - 100youtube-full
Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request… - 100scraping-youtube-playlist
Extracts all videos from a YouTube playlist using apidojo's YouTube Playlist Scraper on Apify. Triggers when the user asks to: get all videos from a YouTube playlist, scrape a YouTube playlist for video data, export playlist video metadata, fetch video stats from a YouTube… - 90youtube-channel-review
Analyze the user's own YouTube channel with CreatorOS. Use when the user asks how their YouTube channel or a video is performing, why views or subscribers changed, what is holding a video back, which videos are rising or declining, when to publish, what viewers ask in comments,…