Built a Daily YouTube → LinkedIn Pipeline with OpenClaw: Architecture, Gotchas, and Lessons Learned

A developer published a detailed breakdown of an OpenClaw skill that automates a daily YouTube-to-LinkedIn content pipeline. The skill checks ~30 AI YouTubers each morning, fetches transcripts via an Apify actor, runs LLM analysis through the OpenClaw Gateway, and writes 26 columns of data per video to a Google Sheet. Cost: ~$0.20/day on Apify, with no separate LLM key needed (uses existing Codex quota). 90% of transcripts come from native captions; Whisper rarely fires.

Key Architecture

Runs at 9am daily, pulls transcripts via Apify async (the sync endpoint returns BOT_DETECTION consistently). LLM output is nested inside outputs[0].text, not at the envelope top. Sheet writes must be batched in groups of 5 to avoid ARG_MAX silent failure — one creator drops 15+ videos/day.

Critical Gotchas

• Secrets in entries.X blocks get nuked on skill uninstall. The author lost a YouTube API key this way. Everything goes in env.vars now.
• Codex idle-turn watchdog kills Discord turns after 5-10 minutes. timeoutSeconds doesn't help. The fix: background long tasks with setsid bash and use a Proactivity cron to self-poll status.
• Python stdout is block-buffered when piped via nohup. Background runs produced 0-byte logs until completion. Use python3 -u or PYTHONUNBUFFERED=1.

LLM Tuning via Sheet

The LLM analysis is customized by 4 user-editable cells in the Google Sheet: linkedin_focus, audience_description, voice_and_tone, avoid. No code changes needed to adjust voice — edit a cell, and the skill adapts. The author seeks feedback on whether this pattern is optimal.

The author plans to publish the skill to ClawHub after a few weeks of production testing.