ClawHub

Boring YouTube Publisher

v1.0.3

Upload videos and Shorts to YouTube using Boring. Use when the user says 'upload to YouTube', 'publish YouTube video', 'post a YouTube Short', 'upload video...

⭐ 0· 72·0 current·0 all-time
by@snoopyrain
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description (uploading to YouTube via Boring) matches the instructions. The declared single required config (MCP Connector link with embedded auth token) is exactly what the instructions use to call boring_* endpoints and publish to YouTube.
ℹ
Instruction Scope
Instructions are focused on uploads and metadata and do not ask the agent to read unrelated local files or env vars. They do, however, instruct uploading user media to Boring's Google Cloud Storage (public URLs) so Boring can call YouTube on the user's behalf — this is expected for this integration but has privacy implications (user media becomes hosted on the third party).
✓
Install Mechanism
No install spec or code files — instruction-only. Lowest installation risk (nothing written to disk by the skill itself).
ℹ
Credentials
No environment variables or local credentials requested. The single required credential is an MCP link containing embedded OAuth tokens (treated like a password). That is proportional to the stated function but grants Boring full delegated access to the user's YouTube account/channel — a sensitive, high-privilege credential that should be handled carefully.
✓
Persistence & Privilege
Skill is not always-enabled and contains no install hooks or instructions to modify other skills or system settings. It relies on the user adding the MCP link as a Connector (platform-level action) which is expected for this integration.
Assessment
This skill is coherent for publishing to YouTube via the Boring service, but before installing or using it: (1) only paste your MCP Connector link into the platform's secure Connector field — treat it like a password; (2) understand that media files will be uploaded to Boring's cloud and served from public URLs while being published to YouTube; (3) confirm the OAuth scopes requested (youtube.upload, youtube.readonly) and that you trust boring.aiagent-me.com; (4) if you have sensitive content, test with non-sensitive uploads first and consider creating a dedicated channel or account; (5) you may want to regenerate the MCP token after use and revoke access if you stop using the service. If you need higher assurance about provenance, request source code or a canonical release from the vendor before giving credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97d7bafc90htt5nmpamyqma3183qa4f

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🎬 Clawdis
ConfigMCP Connector link from boring.aiagent-me.com (contains embedded auth token)

Comments