OpenClaw YouTube Publisher

OpenClaw YouTube Publisher is a public ClawHub YouTube publishing skill. Use it when the user says "youtube creator ops", "youtube publisher", "YouTube Studi...

Security Scan

The skill's files, instructions, and requirements are consistent with a local YouTube Studio publishing helper that records steps and renders a redacted report; it does not request unrelated credentials or install remote code.

Purpose & Capability

Name/description, SKILL.md instructions, and the four bundled Python scripts all align: they create a run manifest, append steps, validate the bundle, and render a redacted markdown report. The only binaries requested are python/python3, which is appropriate for running the included scripts. No environment variables, cloud credentials, or unrelated tools are required.

Instruction Scope

Runtime instructions are narrowly scoped to opening YouTube Studio in an already-authenticated browser profile, recording actions, capturing screenshots, and producing a bundle and report. The guide explicitly instructs pausing for manual auth (CAPTCHA/2FA) and warns not to store secrets in notes/artifacts. The instructions do not ask the agent to read unrelated system files, environment variables, or transmit data to external endpoints other than public URLs recorded in the manifest.

Install Mechanism

There is no install spec and the skill is instruction-plus-scripts only. All code is bundled in the repository; nothing is downloaded or executed from external URLs, and no archives are extracted at install time. This is low-risk from an install mechanism perspective.

Credentials

The skill declares no required environment variables or credentials. It relies on a pre-authenticated browser profile (a reasonable operational assumption) but does not attempt to access or request cookies, tokens, or other secrets. The bundled validation and rendering scripts include secret-detection and redaction logic to reduce accidental disclosure.

Persistence & Privilege

always:false and user-invocable:true. The skill does not request persistent system privileges, modify other skills, or write to system-wide configuration. The skill can be invoked autonomously by the agent (default behavior), but that is expected and not combined with any broad credential access or always:true privileges.

Assessment

This skill appears to be what it says: a local YouTube Studio run recorder and report generator. Before installing/using: (1) review the bundled scripts yourself or run them in a sandboxed environment if you don't trust the source; (2) ensure the browser profile you point the run at is the intended one (do not embed cookies or tokens into manifests); (3) run check_youtube_creator_bundle.py before sharing any bundle to surface secret-like text or absolute/private paths; (4) be cautious about allowing any agent to autonomously run these scripts against profiles with sensitive sessions—the skill recommends manual pause for 2FA/CAPTCHA, which you should follow. If you want higher assurance, verify the repository origin and commit history on the project's homepage before use.

Search intent: youtube creator ops, youtube publisher, youtube studio publish, shorts publisher

Goal

Use OpenClaw to publish a YouTube Short in a logged-in browser session and save a reusable record of the run:

• one machine-readable run manifest
• one structured provenance block for sources such as Midjourney, Suno, or local editors
• one ordered publish log with screenshots and URLs
• one structural bundle check
• one shareable markdown report

This skill is for YouTube Studio publishing through OpenClaw. It assumes the browser profile is already authenticated.

Use This Skill When

• the user wants to publish a YouTube Short through OpenClaw
• the short was assembled from Midjourney visuals, Suno audio, or local edits and that provenance should stay in the same bundle
• you need one clean record of upload, checks, visibility, and final URL
• the same YouTube Studio workflow keeps getting repeated from memory
• a failed publish needs screenshots, expected-versus-actual steps, and a reusable report
• the run should stay visible instead of hidden background automation

Quick Start

1. Initialize the run manifest.

   • Use python3 {baseDir}/scripts/init_youtube_creator_run.py --out <json> --run-id <id> --channel <channel> --goal <goal>.
   • Add --browser-profile, --stage dry_run|live, --visibility, --video-file, --title, repeatable --asset-source, repeatable --provenance, and repeatable --surface fields.
   • Recommended asset source labels:
     • visual:midjourney:<job-or-board>
     • audio:suno:<track-or-project>
     • edit:<tool>:<timeline-or-export>
   • Recommended structured provenance JSON:
     • {"role":"visual","provider":"midjourney","asset_id":"job-123","source_url":"https://midjourney.com/jobs/job-123","prompt_ref":"board-a","model":"v7","license":"internal-review","public_credits_required":false}
     • {"role":"audio","provider":"suno","asset_id":"track-04","source_url":"https://suno.com/song/track-04","prompt_ref":"chorus-a","model":"v4","license":"creator-plan","attribution_text":"Music draft from Suno.","public_credits_required":true}

2. Execute the YouTube Studio flow through OpenClaw.

   • Open the Studio page in a logged-in profile.
   • Record each meaningful step with append_youtube_creator_step.py.
   • Capture screenshots and public URLs as the run progresses.

3. Default to dry_run.

   • Keep the manifest in dry_run stage until the final publish click is intentionally approved.
   • Switch to live only when the user wants the run to reach a public or unlisted post.

4. Pause for manual auth if needed.

   • If YouTube shows CAPTCHA, passkey, login, or 2FA, stop the automated step log and let the user complete it in the same browser profile.
   • Resume only after the authenticated Studio session is back.

5. Check the bundle before sharing it.

   • Use python3 {baseDir}/scripts/check_youtube_creator_bundle.py --manifest <json> --repo-root <repo> --out <json>.
   • Fix missing screenshots, incomplete failed steps, or private/absolute asset paths before sharing the bundle.

6. Render the report.

   • Use python3 {baseDir}/scripts/render_youtube_creator_report.py --manifest <json> --out <md>.
   • The default report keeps only public YouTube, Midjourney, and Suno URLs and redacts browser profile labels, private artifact paths, and non-public URLs found inside step text or provenance notes.
   • Share the report instead of loose screenshots and chat fragments.

Operating Rules

Profile rules

• Use a logged-in browser profile dedicated to the publishing context when possible.
• Do not claim a run is autonomous if login, CAPTCHA, passkey, or 2FA still requires a manual step.
• Keep the publish run in one visible browser session.
• Treat the final publish click as a deliberate user-approved action, even when the earlier steps are automated.

Publish rules

• Record expected result and actual result for every step that matters.
• Capture a screenshot for failed or blocked steps and important checkpoints.
• Store final published URL when the run succeeds.
• Record upstream asset provenance when Midjourney, Suno, CapCut, or another editor was part of the content chain.
• If public credits or attribution are required for Midjourney, Suno, or another provider, keep that text in provenance and make sure the publish metadata includes it where needed.
• Prefer relative artifact paths so the bundle can move between machines.

Safety rules

• Do not store cookies, secrets, or access tokens in notes or artifacts.
• Do not use private absolute filesystem paths in the final bundle.
• Treat moderation delays and post-processing lag as publish outcomes to record, not as silent success.

Bundled Scripts

• scripts/init_youtube_creator_run.py
  • Create a machine-readable manifest for one YouTube publish run.
• scripts/append_youtube_creator_step.py
  • Append one publish step to the manifest.
• scripts/check_youtube_creator_bundle.py
  • Validate the resulting run bundle before sharing or final review.
• scripts/render_youtube_creator_report.py
  • Render a concise markdown report from the publish manifest.