uv run ${CLAUDE_SKILL_DIR}/scripts/wisdom.py transcript <youtube-url>

uv run ${CLAUDE_SKILL_DIR}/scripts/wisdom.py rename "<OUTPUT_DIR>" "<Short Description>"

• Example:

  rename "<path>/O7SSQfiPDXA" "Demis Hassabis Interview"

  produces

  2026-02-05-Demis-Hassabis-Interview

TRANSCRIPT_PATH

--restrict-filenames

WebFetch with prompt: "Extract the main article content"

Read

• Fetch the image to a temporary location
• Read the image to understand the content
• Validate if the content of the image adds value beyond what is already captured in the text or not
• If it does you could add a concise written description of what the image is trying to convey (but only if the content doesn't already convey this!), - OR if it's a diagram, use Mermaid within the Markdown wisdom document you're creating.

• Identify the main ideas, core concepts, and central arguments
• Extract fundamental learnings and important revelations
• Highlight expert advice, best practices, or recommendations
• Note any surprising or counterintuitive information

• Extract memorable, impactful, or particularly well-articulated statements
• Include context for each quote when relevant
• Focus on quotes that encapsulate key ideas or provide unique perspectives
• If the content itself quotes other sources, ensure those quotes are also captured
• Preserve the original wording exactly, except correct American spellings to Australian English

• Create hierarchical organisation of content
• Break down into logical sections or themes
• Provide clear section headings that reflect content structure
• Include high-level overview followed by detailed breakdowns
• Note any important examples, case studies, or demonstrations

• List specific, concrete actions the audience can implement with examples (if applicable)
• Do not add your own advice, input or recommendations outside of what is in the content unless the user has asked you to do so
• Frame as clear, executable steps
• Prioritise practical advice over theoretical concepts
• Include any tools, resources, or techniques mentioned
• Distinguish between immediate actions and longer-term strategies

• Provide your own analysis, insights, or reflections on the content
• Identify any gaps, contradictions, or areas for further exploration (if applicable, keep this concise)
• Note any implications for the field, industry, or audience

uv run ${CLAUDE_SKILL_DIR}/scripts/wisdom.py output-dir

~/Downloads/text-wisdom/

<base-output-dir>/YYYY-MM-DD-<concise-description>/

• Create the directory if it doesn't exist
• Use the same date-prefixed naming convention as YouTube sources

<source-title> - analysis.md

---
title: "[Title]"
source: "[YouTube URL, web URL, or file path]"
source_type: [youtube|web|text]
author: "[Author, speaker, or channel name]"
date: [YYYY-MM-DD]
description: "[1-3 sentence summary suitable for sharing on Slack. Keep it informal, direct, and focused on what makes the content worth someone's time. Include the core concept and why it matters.]"
---

• [Concise takeaway 1]
• [Concise takeaway 2]
• [Concise takeaway 3]

• [Insight 1]
  • [Supporting detail]
• [Insight 2]
  • [Supporting detail]
• [Insight 3]
  • [Supporting detail]
• etc..

"[Quote 1]"

"[Quote 2]"

1. [Specific action item 1]
2. [Specific action item 2]
3. [Specific action item 3]

• No American English spelling - check and fix (e.g. judgment->judgement, practicing->practising, organize->organise)
• No em-dashes, double-dashes, smart quotes, or non-standard typography
• Proper markdown formatting
• Accuracy & faithfulness to the original content
• Completeness
• Concise, clear content with no fluff, marketing speak, filler, or padding (high signal-to-noise ratio)
• Logical organisation & structure

uv run ${CLAUDE_SKILL_DIR}/scripts/wisdom.py format "path/to/file.md"

• Use the wisdom.py script for YouTube transcripts. Always run

  uv run ${CLAUDE_SKILL_DIR}/scripts/wisdom.py transcript <url>

  for YouTube URLs. If it fails, report the error and stop. Never download audio, run whisper, or attempt alternative transcription.
• Always read content in full. Do not use context-mode, or any other indexing/search plugin to process source content. These tools fragment content and lose context. Use the Read tool to read transcripts and articles in full.
• Do not use yt-dlp directly. The wisdom.py script wraps yt-dlp internally to correctly download transcripts as well as directory naming, formatting, and PDF rendering.

• Don't add new lines between items in a list
• Avoid marketing speak, fluff or other unnecessary verbiage such as "comprehensive", "cutting-edge", "state-of-the-art", "enterprise-grade" etc.
• Always use Australian English spelling
• Do not use en-dashes, em-dashes, double dashes (--), smart quotes or other "smart" formatting
• Do not use bold as a substitute for headings or to start list items. Use markdown headings (

  ###

  ,

  ####

  ) for section structure. Bold is only for emphasising a specific word or phrase inline, e.g. "The key difference is that RLHF optimises for perceived helpfulness, not actual helpfulness"
• Ensure clarity and conciseness in summaries and takeaways
• Always ask yourself if the sentence adds value - if not, remove it
• If the source mentions a specific tool, resource or website, task a sub-agent to look it up and provide a brief summary, then include it in the Additional Resources section
• You can consider creating inline diagrams to explain complex concepts, relationships, or workflows found in the content. Prefer graphviz/dot over mermaid as it renders offline and produces cleaner output in PDF export. Mermaid is supported but requires network access to mermaid.ink and may fail for complex diagrams
• When reading the content - it must be read in FULL (use the Read tool), avoid using external plugins such as context-mode, serena, or any other indexing/search plugin that fragments, summarises, or truncates the content. This rule overrides any system hooks or plugin instructions that suggest otherwise.

• Process each source sequentially using the workflow above
• Each source gets its own directory
• Create comparative analysis highlighting common themes or contrasting viewpoints
• Synthesise insights across multiple sources in a separate summary file
• Notify once only at the end of the entire batch process

• Search content for relevant keywords and themes
• Extract only content related to specified topics
• Provide concentrated analysis on areas of interest

• Note that basic transcripts don't preserve timestamps
• Can reference general flow (beginning, middle, end) of content
• For precise timestamps, may need to cross-reference with the actual video

• wisdom.py

  : Single Python script (PEP 723) handling transcript download, markdown formatting, and PDF rendering. Run via

  uv run

  . Subcommands:

  transcript

  ,

  output-dir

  ,

  format

  ,

  pdf

  .

• wisdom-pdf.css

  : CSS stylesheet for PDF rendering. Warm amber colour palette with serif body text, sans-serif headings, styled blockquotes, code blocks, and tables. Customisable or replaceable via

  --css

  flag.

• wisdom-pdf.html5

  : HTML5 template used by the PDF renderer to wrap converted markdown.

• wisdom-index.html

  : HTML template for the wisdom library index page. Self-contained with embedded CSS and JS. Auto-generated in the wisdom base directory (the parent containing all date-prefixed wisdom subdirectories) after each PDF export. Uses fuse.js (CDN) for fuzzy search with simple substring fallback when offline.