Video Note Publishing

SkillDocs & knowledge

Transform Obsidian video notes from the Vault into published notes on joelclaw.com. Use when publishing video notes, converting vault video content to the site, or when asked to 'publish a video note,' 'turn this video into a note,' 'publish from vault/videos,' or any task involving /Vault/Resources/videos → joelclaw content. Triggers on references to video notes, vault video files, or publishing video content to the blog.

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Video Note Publishing skill

What this skill tells your AI

The instructions your AI receives, as published by joelhooks/joelclaw in skills/video-note/SKILL.md and read by ahel’s review.

Transform video notes from /Users/joel/Vault/Resources/videos/ into published MDX notes on the joelclaw.com site at apps/web/content/.

Source format

Vault video notes are Obsidian markdown with this frontmatter:

type: video
source: https://www.youtube.com/watch?v=ID
channel: Channel Name
published: YYYY-MM-DD
duration: "HH:MM:SS"
nas_path: /volume1/home/joel/video/...
transcribed: YYYY-MM-DD
tags:
  - video

Body contains: H1 title, > [!info] Source callout, Executive Summary, Key Points, Speaker Context, Notable Quotes, Related links, Tags, and a collapsible Full Transcript.

Output format

Publish as .mdx in apps/web/content/ with this frontmatter:

title: "Short descriptive title"
type: "note"
date: "YYYY-MM-DD"        # use today's date
description: "One-sentence hook in Joel's voice"
source: "YouTube URL"
channel: "Channel Name"
duration: "HH:MM:SS"

Transformation workflow

  1. Read the source vault note
  2. Extract YouTube video ID from the source URL
  3. Write the note in Joel's voice (read joel-writing-style skill — it's in the same .agents/skills/ directory). Key rules:
    • Open with a hook, not a summary
    • Use Joel’s supplied framing where relevant; never invent his experience, beliefs, or personal reaction
    • Use short paragraphs, strategic profanity, bold for emphasis
    • End abruptly — no forced wrap-up
  4. Embed the video with <YouTube id="VIDEO_ID" /> after the intro
  5. Select source-supported material appropriate for the publication audience. Exclude the full transcript, private context, customer information, and paid corpus material. Then adapt relevant sections:
    • Executive summary → rewrite as the intro (Joel's voice)
    • Key points → keep substance, tighten prose
    • Speaker context → "Who is [Speaker]" section
    • Notable quotes → curated "Quotes that stuck with me"
    • Related links → keep as "Related" section
  6. Strip Obsidian syntax: > [!info] callouts → plain text, [[wikilinks]] → markdown links
  7. Slug: kebab-case, concise (e.g., openclaw-peter-steinberger-lex-fridman)

Voice reference

For Joel's writing style details, read joel-writing-style SKILL.md and its voice examples. Key points:

  • Use first person only for Joel’s documented words or supplied experience. Address the reader directly when useful.
  • Contractions always
  • Bold for inline emphasis on key phrases
  • Emoji sparingly (1-2 per note max)
  • Headers as narrative beats, not outlines
  • Links woven into sentences, never "click here"
  • Credit people by name with links

Content system details

See content-system.md for the joelclaw.com content types, MDX components, and routing.

Example

See example-note.md for a complete published note showing the target format and voice.

Signals

GitHub stars
64
Forks
2
Last commit
Sep 2026
Advanced
Item type
skill
Key
video-note
Source
github.com/joelhooks/joelclaw