laniameda-youtube-digest
laniameda-youtube-digest
Purpose: Watch a YouTube video so Michael doesn't have to. Extract what's actionable — tools, prompts, workflows, "if X then Y" mappings — and save to KB. For AI creatorship tutorials: extract model-specific techniques, prompt structures, and optionally encode new knowledge into studio skills.
Engine: Supadata API (supadata skill). Full API reference: references/supadata.md. Key decision: use Transcript for narrated content; use Extract (vision) when prompts/settings are shown on screen but not spoken aloud (e.g. ComfyUI node graphs, Midjourney UI, on-screen prompt text).
Cross-reference: This is the skill that laniameda-x-post-digest calls when it encounters YouTube links in X posts.
Triggers
- YouTube URL pasted
- "digest this video"
- "watch this for me"
- "extract from this video"
- "what's useful in this"
- "learn from this"
- "what does this teach"
More from michailbul/laniameda-skills
notion-sync
>
14instagram-extract
Extract text, links, and key takeaways from Instagram/Threads posts (especially carousels) and LinkedIn posts using an already-logged-in Brave/Chrome tab via OpenClaw Browser Relay. Use when the user pastes an Instagram/Threads/LinkedIn URL (or forwards screenshots) and asks something generic like “save it”, “capture this”, “summarize and store”, or “put this in the vault” — you should decide what’s worth saving, classify it into the right pillar, save it to the local KB and/or ingest prompts via the laniameda-kb skill, and also emit a compact JSON payload into a media-agent inbox file for downstream reuse.
12carousel-designer
>
11andromeda-messages
>
10deepgram-transcribe
>
10repo-kanban-pm
Install and enforce a lightweight product-management workflow inside a code repo: feature-as-kanban boards, ROADMAP status tracking, branch/PR conventions, and an optional daily OpenClaw cron PM review. Use this skill when (1) starting work in a NEW repository/project that does not yet have a ROADMAP+feature-KANBAN system, (2) you are delegated to spin up a new project and want multi-agent coordination from day one, or (3) you are asked to fix/restructure an existing repo and introduce an organized backlog/feature tracking system. Also use when adding a daily PM audit loop (cron) to keep code + docs + PRs in sync.
10