dot_config/ai_templates/skills/meta/ContentAnalysis/SKILL.md
Content-adaptive wisdom extraction from videos, podcasts, articles, and YouTube -- dynamic sections built from what the content actually contains, not static templates. USE WHEN extract wisdom, content analysis, analyze content, analyze video, analyze podcast, extract insights, key takeaways, what did I miss, extract from YouTube, insight report, summarize content, what's interesting.
npx skillsauth add pascalandy/dotfiles ContentAnalysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Content-adaptive wisdom extraction -- dynamic sections built from what the content actually contains, not static templates.
Load references/ROUTER.md to determine which sub-skill handles this request.
Traditional content extraction follows a fixed template: IDEAS, QUOTES, HABITS, FACTS, REFERENCES. Every piece of content gets the same headers regardless of what it actually contains. A programming interview gets a "HABITS" section. A geopolitical analysis gets "FACTS" that are really just opinions. The output feels mechanical and misses the real gems because the sections were decided before the content was even read.
The fundamental issue: the extraction format should serve the content, not the other way around.
ContentAnalysis 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."
Core capabilities:
The sections adapt because the content dictates them.
| Component | Path | Purpose |
|-----------|------|---------|
| Skill router | references/ROUTER.md | Minimal routing table that dispatches requests to the right sub-skill |
| ExtractWisdom skill | references/ExtractWisdom/MetaSkill.md | Dynamic content extraction methodology, tone rules, depth levels, quality standards |
| Extract workflow | references/ExtractWisdom/workflows/Extract.md | Step-by-step extraction workflow |
Summary:
This sounds similar to the original extract_wisdom which also pulls insights from content. The difference:
The original extract_wisdom uses static sections -- IDEAS, QUOTES, HABITS, FACTS, REFERENCES -- for every piece of content. ContentAnalysis reads the content first, figures out what wisdom domains are present, and builds sections around what it finds. A talk about AI agents gets "Self-Modifying Software" and "The Agent Spectrum" instead of generic IDEAS. The tone follows a conversational voice standard (Level 3) that produces bullets people actually want to read, not compressed information nuggets. Depth levels let you choose between a 30-second skim and a comprehensive deep dive.
| Trigger | What Happens | |---------|--------------| | "extract wisdom from [URL]" | Routes to ExtractWisdom -- Full-depth extraction with 5-12 dynamic sections | | "analyze this video" | Routes to ExtractWisdom -- Content scan, section detection, extraction with closing sections | | "extract wisdom (fast)" | Routes to ExtractWisdom -- Fast-depth: 3 sections, 3 bullets each, no closing sections | | "extract wisdom at comprehensive level" | Routes to ExtractWisdom -- Maximum depth: 10-15 sections plus Themes and Connections | | "key takeaways from this podcast" | Routes to ExtractWisdom -- Full extraction with emphasis on actionable insights | | "what did I miss in this article" | Routes to ExtractWisdom -- Full extraction focused on non-obvious insights |
User: "extract wisdom from [YouTube URL about AI agents]"
AI responds:
# EXTRACT WISDOM: Building AI Agents That Actually Work
> A deep dive into agent engineering with [speaker] -- from self-modifying
> software to the economics of building with AI
---
## The Death of 80% of Apps
- He wasn't trying to build self-modifying software. He just let the agent
see its own source code and it started fixing itself.
- Most apps are just a UI on a database. Agents can generate those on the fly.
The app store as we know it is already dead.
- ...
## Money Stops Mattering
- Past a certain point, money stops mattering. A cheeseburger is a cheeseburger
no matter how rich you are.
- Every VC is offering hundreds of millions. He genuinely doesn't care.
- ...
[... more dynamic sections ...]
---
## One-Sentence Takeaway
The best agents aren't programmed -- they're given access to their own source
code and a reason to improve.
## If You Only Have 2 Minutes
- Self-modifying software happened by accident, not design
- 80% of current apps will be replaced by agent-generated UIs
- ...
## References & Rabbit Holes
- **Claude Code** -- The agent framework he built everything on
- **MCP protocol** -- The tool integration layer that makes agents practical
User: "extract wisdom (fast) from this podcast episode"
AI responds:
# EXTRACT WISDOM: [Title]
> [One-line description]
## [Dynamic Section 1]
- [3 tight bullets]
## [Dynamic Section 2]
- [3 tight bullets]
## [Dynamic Section 3]
- [3 tight bullets]
No configuration required. The skill works out of the box with sensible defaults (Full depth level). All extraction uses built-in Level 3 conversational voice standards.
No customization needed -- the skill adapts dynamically to each piece of content.
| Customization | Where | Impact | |--------------|-------|--------| | Default depth level | Invoke with depth keyword | Changes from Full to another level per request | | Section preferences | Modify ExtractWisdom SKILL.md | Always-include or always-exclude section types |
development
Explicitly triggered when the user mentions `wiki-map`. It ingests, queries, lints, or compiles a markdown wiki.
testing
Explicitly triggered when the user mentions `single-skill-creator`. It scaffolds a new `SKILL.md`.
testing
Explicitly triggered when the user mentions `qmd`. It searches local markdown or QMD collections.
development
Explicitly triggered when the user mentions `ontology-map`. It builds, refreshes, or checks an ontology.