← Back to Skills Marketplace
bin-huang

Youtube Data CLI

by Bin-Huang · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
116
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install youtube-data-cli
Description
Full YouTube Data API v3 CLI covering all 20 resources: search, channels, videos (upload/update/delete/rate), playlists, playlist items, comments, subscripti...
Usage Guidance
This skill's instructions legitimately require OAuth credentials and a credentials file, but the skill metadata does not declare those requirements or a source/homepage. Before installing or using it: (1) ask the publisher for the package source (npm package name, GitHub repo) and verify the code; (2) avoid placing long-lived refresh tokens in broadly writable locations — prefer short-lived or limited-scope credentials; (3) if you only need read-only operations, use an API key or restrict OAuth scopes (do not grant full https://www.googleapis.com/auth/youtube unless necessary); (4) inspect ~/.config/youtube-data-cli/credentials.json and any npm package contents for unexpected behavior; (5) rotate credentials after testing and consider running the CLI in an isolated environment. The mismatch between declared metadata and the runtime instructions is the main red flag — treat this skill as untrusted until you can verify its source and the npm package contents.
Capability Analysis
Type: OpenClaw Skill Name: youtube-data-cli Version: 1.0.0 The skill is a legitimate integration for the 'youtube-data-cli' tool (a known open-source project by Bin Huang) to interact with the YouTube Data API v3. The SKILL.md provides standard instructions for installation via npm and detailed usage for managing YouTube resources like videos, playlists, and comments. Credential handling (API keys and OAuth tokens) follows standard practices for CLI tools, and no evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Tags
requires-oauth-token
Capability Assessment
Purpose & Capability
The skill claims to implement the full YouTube Data API (including write/delete/upload operations), which legitimately requires API keys and OAuth client credentials/refresh tokens. However, the registry metadata lists no required env vars, no primary credential, and no required config paths. That omission is inconsistent with the described capabilities (uploads/deletes require OAuth refresh tokens and client secrets).
Instruction Scope
SKILL.md explicitly instructs the agent/user to resolve credentials from env vars (YOUTUBE_API_KEY, YOUTUBE_CLIENT_ID, YOUTUBE_CLIENT_SECRET, YOUTUBE_REFRESH_TOKEN) and from ~/.config/youtube-data-cli/credentials.json. Those paths and env vars are not declared in the skill metadata. The instructions otherwise focus on running the CLI and do not ask to read unrelated system files, but the implicit access to a home credentials file is material and should have been declared.
Install Mechanism
There is no install spec in the skill bundle, but SKILL.md recommends installing via `npm install -g youtube-data-cli`. Installing from the public npm registry is a common pattern, but the skill metadata not declaring an install method or a verified homepage/source means users cannot easily verify the package's provenance from the skill record — you should inspect the npm package/source before installing.
Credentials
SKILL.md expects sensitive credentials (OAuth client ID/secret and refresh token) and a credentials file in the user's home directory, yet the skill declares no required env vars or config paths. Requesting a refresh token with the recommended full YouTube scope grants broad privileges (upload/delete/manage) and is disproportionate to a metadata-free skill record; users must be warned and limit scopes or use read-only API keys where possible.
Persistence & Privilege
The skill does not request always:true, does not ask to modify other skills or system-wide settings, and does not declare autonomous-disable. Autonomous invocation is allowed (platform default) but is not combined here with 'always' or declared persistent privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install youtube-data-cli
  3. After installation, invoke the skill by name or use /youtube-data-cli
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of youtube-data-cli – a full-featured CLI for the YouTube Data API v3. - Covers all 20 API resources with 52 CLI commands, including search, channel, video, playlist, comment, subscription, caption, thumbnail, activities, and more management. - Supports both API key (for public data) and OAuth 2.0 (for all commands, private data, uploads, and writes); credentials can be provided by flag, env vars, or config. - Pretty-printed JSON output by default, with error reporting in JSON and global output/credentials configuration. - Includes detailed help, usage examples, and command reference for all supported operations. - Enables automation of YouTube management workflows directly from the CLI.
Metadata
Slug youtube-data-cli
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Youtube Data CLI?

Full YouTube Data API v3 CLI covering all 20 resources: search, channels, videos (upload/update/delete/rate), playlists, playlist items, comments, subscripti... It is an AI Agent Skill for Claude Code / OpenClaw, with 116 downloads so far.

How do I install Youtube Data CLI?

Run "/install youtube-data-cli" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Youtube Data CLI free?

Yes, Youtube Data CLI is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Youtube Data CLI support?

Youtube Data CLI is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Youtube Data CLI?

It is built and maintained by Bin-Huang (@bin-huang); the current version is v1.0.0.

💬 Comments