youtube-channel-analytics-dashboard — Claude Code skill
A skill that builds a YouTube channel dashboard: views, subscribers, revenue and audience demographics. Handy when you want the numbers without pulling them by hand.
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a claude-codeWhat youtube-channel-analytics-dashboard does
This skill covers a dashboard for YouTube channel analytics. It follows views, watch time, subscriber gains, estimated revenue and audience demographics, showing both live figures and past periods. You also get per-video breakdowns and report exports in CSV or PDF.
Under the hood it talks to YouTube Data API v3. You need a Google Cloud project with the API turned on, an API key or OAuth 2.0 credentials, and the youtube.readonly and yt-analytics.readonly scopes. Settings live in config.json: API key, channel ID, refresh interval, retention window and the export folder. The key and channel ID come from the YOUTUBE_API_KEY and YOUTUBE_CHANNEL_ID environment variables.
The dashboard targets Windows 10 or 11 (64-bit) and needs .NET Framework 4.8+ or the Visual C++ Redistributable. Without an API key and a channel ID there is nothing to chart, so line those up first.
What it helps with
- build a dashboard for YouTube channel metrics
- track subscriber growth across a date range
- export analytics to CSV or PDF
- review audience age, gender and geography
- find top videos by views or estimated revenue
Example prompts for the agent
- Analyze my YouTube channel performance and show view trends
- Chart subscriber growth for the last 30 days
- Export a channel analytics report as CSV
How to install youtube-channel-analytics-dashboard
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a claude-code2Manually: put the files in place
~/.claude/skills/youtube-channel-analytics-dashboard/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/youtube-channel-analytics-dashboard/
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a codex2Manually: put the files in place
.agents/skills/youtube-channel-analytics-dashboard/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a cursor2Manually: put the files in place
.cursor/skills/youtube-channel-analytics-dashboard/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/data-skills youtube-channel-analytics-dashboard2Manually: put the files in place
.github/skills/youtube-channel-analytics-dashboard/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/data-skills --path skills/youtube-channel-analytics-dashboardManually: put the files in place
.devin/skills/youtube-channel-analytics-dashboard/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about youtube-channel-analytics-dashboard
How do I install youtube-channel-analytics-dashboard in Claude Code?
Run npx skills add reason-machines/data-skills --skill youtube-channel-analytics-dashboard -a claude-code. The skill file lands at ~/.claude/skills/youtube-channel-analytics-dashboard/SKILL.md.
What does youtube-channel-analytics-dashboard do?
It produces a YouTube channel dashboard with views, watch time, subscribers, estimated revenue and audience demographics. Figures refresh live and history is kept for past periods.
What do I need before using it?
A YouTube Data API v3 key and a channel ID in the YOUTUBE_API_KEY and YOUTUBE_CHANNEL_ID environment variables, plus a Google Cloud project with the API enabled and the required scopes.