/ExtractWisdom

name: ExtractWisdom
version: 1.1.16
description: "Content-adaptive wisdom extraction that reads content first, detects which wisdom domains are present, and builds custom sections around them, with five depth levels and mandatory contrarian takes; pulls YouTube via fabric and articles via WebFetch. USE WHEN extract wisdom, analyze video, analyze podcast, extract insights, key takeaways, summarize interview, distill content. NOT FOR static Fabric extract_wisdom pattern (use Fabric)."

Customization

**Before executing, check for user customizations at:** `~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/ExtractWisdom/`

If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

ExtractWisdom — Dynamic Content Extraction

What It Does

Pulls the best ideas out of videos, podcasts, interviews, and articles. It reads the content first, detects what kinds of wisdom are actually in there, then builds custom sections around what it finds instead of forcing the same headers every time. Five depth levels from Instant to Comprehensive. Output always ends with a one-sentence takeaway, an "If You Only Have 2 Minutes" list, and references worth following.

The Problem

Static extraction templates force every piece of content into the same boxes — IDEAS, QUOTES, HABITS, FACTS — so a security talk and a business podcast come out looking identical and the real gems get flattened into generic bullets. The output reads like a book report, not like a smart friend telling you the parts that made them stop. This skill adapts its sections to the content and writes the points the way you'd actually say them out loud, so the contrarian takes and first-time revelations survive instead of getting watered down.

How It Works

Instead of static sections (IDEAS, QUOTES, HABITS...), this skill detects what wisdom domains actually exist in the content and builds custom sections around them.

A programming interview gets "Programming Philosophy" and "Developer Workflow Tips." A business podcast gets "Contrarian Business Takes" and "Money Philosophy." A security talk gets "Threat Model Insights" and "Defense Strategies." The sections adapt because the content dictates them.

When to Use

• Analyzing YouTube videos, podcasts, interviews, articles
• User says "extract wisdom", "what's interesting in this", "key takeaways"
• Processing any content where you want to capture the best stuff
• When standard extraction patterns miss the gems

Depth Levels

Extract at different depths depending on need. Default is **Full** if no level is specified.

| Level | Sections | Bullets/Section | Closing Sections | When | |-------|----------|----------------|-----------------|------| | **Instant** | 1 | 8 | None | Quick hit. One killer section. | | **Fast** | 3 | 3 | None | Skim in 30 seconds. | | **Basic** | 3 | 5 | One-Sentence Takeaway only | Solid overview without the deep cuts. | | **Full** | 5-12 | 3-15 | All three | The default. Complete extraction. | | **Comprehensive** | 10-15 | 8-15 | All three + Themes & Connections | Maximum depth. Nothing left behind. |

**How to invoke:** "extract wisdom (fast)" or "extract wisdom at comprehensive level" or just "extract wisdom" for Full.

**Comprehensive extras:**

• **Themes & Connections** closing section: identify 3-5 throughlines that connect multiple sections. Not summaries — the deeper patterns the speaker may not even realize they're revealing.
• Prioritize breadth. Every significant wisdom domain gets its own section.
• No merging sections to save space. If the content supports 15 sections, use 15.

**All levels use the same voice, tone rules, and quality standards.** The only thing that changes is structure. An Instant extraction should hit just as hard per-bullet as a Comprehensive one.

Workflow Routing

| Workflow | Trigger | File | |----------|---------|------| | **Extract** | "extract wisdom from", "analyze this", YouTube URL | `Workflows/Extract.md` |

Tone Rules (CRITICAL)

**Canonical voice reference: `LIFEOS/USER/PRINCIPAL/WRITINGSTYLE.md`** — read this file for the full voice definition. The bullets should sound like the user telling a friend about it over coffee. Not compressed info nuggets. Not clever one-liners. Actual spoken observations.

**THREE LEVELS — we're aiming for Level 3:**

**Level 1 (BAD — documentation):**

• The speaker discussed the importance of self-modifying software in the context of agentic AI development
• It was noted that financial success has diminishing returns beyond a certain threshold
• The distinction between "vibe coding" and "agentic engineering" was emphasized as meaningful

**Level 2 (BETTER — but still "smart bullet points"):**

• He built self-modifying software basically by accident — just made the agent aware of its own source code
• Money has diminishing returns. A cheeseburger is a cheeseburger no matter how rich you are.
• "Vibe coding is a slur" — he calls it agentic engineering, and only does vibe coding after 3am

**Level 3 (YES — this is what we want — conversational, the user's voice):**

• He wasn't trying to build self-modifying software. He just let the agent see its own source code and it started fixing itself.
• Past a certain point, money stops mattering. A cheeseburger is a cheeseburger no matter how rich you are.
• He calls vibe coding a slur. What he does is agentic engineering. The vibe coding only happens after 3am, and he regrets it in the morning.

**The difference between Level 2 and 3:** Level 2 is compressed info with em-dashes. Level 3 is how you'd actually SAY it. Varied sentence lengths. Letting a thought breathe. Not trying to be clever — just being clear and direct and a little bit personal.

**Key signals of Level 3:**

• Reads naturally when spoken aloud
• Varied sentence lengths — some short, some longer
• Understated — lets the content c