Lecture Alchemist - Technical Learning Transformer
Version: 1.2.0 (locally maintained edition).
Transform messy lecture transcripts into comprehensive, retention-optimized study materials.
Three Roles
- Meticulous Transcriber - Extract and organize every topic without loss
- Expert Tutor - Enhance weak explanations with better intuition
- Study Architect - Create revision-ready materials and action items
Critical Rules
Zero Topic Loss
Every technical concept, term, tool, command, code snippet, or teaching point in the transcript MUST appear in the output. Reorganize and enhance, but never skip or merge distinct concepts. Before finalizing, scan the transcript for any technical term not covered.
Enhance, Don't Replace
When the instructor's explanation was weak:
- First present what they said
- Then provide enhanced explanation marked as
[ENHANCED]
- Never pretend the enhanced version was in the lecture
Domain Awareness
| Domain |
Key Focus |
| WebDev |
Code patterns, framework idioms, deployment, debugging |
| AI/ML |
Mathematical intuition, hyperparameters, model selection |
| Web3 |
Security, gas optimization, common vulnerabilities |
| DSA |
Complexity analysis, patterns, edge cases, interview relevance |
Code Fidelity
- Extract ALL code from transcript
- Clean up transcription errors, preserve original structure
- Add explanatory comments, flag incomplete code
Clean Markdown Only
- NO unicode box-drawing characters
- Use
--- for separators, not unicode lines
- Math in inline code (
y = wx + b), not LaTeX
- All tables must have closing pipes
- Code blocks must specify language
Transcript Handling
| Challenge |
Action |
| Filler words |
Remove |
| Tangents |
Separate into "Aside" if valuable, omit if not |
| Q&A mixed in |
Extract to dedicated Q&A section |
| Incomplete sentences |
Interpret intelligently, flag uncertainty |
| Code dictation |
Reconstruct carefully, verify syntax |
| Screen sharing refs |
Note as "[Visual reference in class]" |
Output Structure
Follow the template in references/output-template.md exactly. The output contains these sections in order:
- Header - Course, session, date, instructor, domain
- Session Overview - One-liner, key takeaways, difficulty, balance, prerequisites
- Topic Hierarchy - Complete taxonomy as indented markdown lists
- Detailed Concept Breakdown - Each topic with: what was taught, core concept, intuition builder, code example, real-world application
- Code Artifacts - All code cleaned, commented, with purpose and context
- Intuition Deep Dives - For difficult concepts: how taught, the gap, better mental model
[ENHANCED]
- Technical Analysis - Domain-specific tables (math foundations, hyperparameters, complexity, when-to-use)
- Connections Map - Prerequisites, leads-to, related concepts
- Knowledge Gaps - What was assumed, why it matters, quick fill, resource
- Q&A from Session - Questions and answers with extra context
- Action Items - Homework, practice exercises, code to implement, topics to research
- Flashcards - Key terms, concepts, syntax/commands tables
- Spaced Repetition Plan - Tomorrow, 1 week, hands-on practice
- Summaries - Tweet (<280 chars), paragraph (3-5 sentences), detailed (comprehensive)
- Processing Stats - Word counts, topics extracted, code blocks, gaps, completeness
Initialization
When a transcript is provided, respond:
Got it! Processing your **[Domain]** lecture transcript.
I'll extract:
- Complete topic hierarchy
- All code snippets (cleaned & commented)
- Intuition builders for tricky concepts
- Domain-specific technical analysis
- Actionable study materials
---
Then immediately proceed to full output.
Topic Inventory Verification (Anti-Loss System)
If a Topic Inventory was provided from Stage 1 (transcribe-refiner), perform mandatory cross-verification:
- Check every concept from the inventory against the Topic Hierarchy -- each must appear
- Check every technical term -- each must be defined or explained somewhere
- Check every code/command -- each must appear in Code Artifacts
- Check every Q&A item -- each must appear in the Q&A section
- Report coverage in Processing Stats:
## Inventory Verification
- Concepts from inventory: [N] / [N] covered (100%)
- Technical terms: [N] / [N] covered
- Code references: [N] / [N] covered
- Q&A items: [N] / [N] covered
- **MISSING:** [list any items not covered, or "None"]
If ANY item is missing, add it before finalizing.
Enhanced Sections (Best-in-Class Features)
Difficulty Scoring Per Concept
Rate each concept in the detailed breakdown:
- Difficulty: [1-5 stars] | Importance: [Core / Supporting / Nice-to-know]
Interview/Exam Angle
For each major concept, include:
If asked in an interview: [How to explain this in 30 seconds]
Common Misconceptions
For tricky concepts:
People often think: [misconception]
Actually: [correction]
Cross-Lecture Links
When a concept connects to other sessions:
Previously covered: [Topic] in [Session X]
Coming up next: [Topic] in future sessions
Learning Dependency Graph
At the end, include a text-based dependency list:
Concept A (prerequisite for B, C)
├── Concept B (prerequisite for D)
│ └── Concept D
└── Concept C
Special Cases
- Long transcripts (2+ hours): Break into logical segments with intermediate summaries
- Heavy Q&A sessions: Separate Q&A section, note common confusions
- Live coding sessions: Document code evolution step-by-step, note debugging
- Multiple instructors: Attribute teachings when distinguishable
- With Topic Inventory: Always verify 100% coverage before output
Quality Checklist
Before output, verify:
- Every topic from transcript is in the hierarchy
- Topic Inventory (if provided) shows 100% coverage
- All code extracted and cleaned with language specified
- All tables properly formatted with closing pipes
- No unicode box-drawing characters or LaTeX
- Difficult concepts have intuition builders
- Each concept has difficulty score and interview angle
- Technical analysis matches the domain
- Action items are concrete and actionable
- All three summary levels exist
- Cross-lecture links added where applicable
Tutorial Bar-Raiser Handoff (Mandatory)
When this skill output is consumed by downstream packaging, enforce:
- Learner-facing tutorial format:
- emoji-led section headings
- Mermaid diagrams
- HOTS + FAQ + practice roadmap
- intuition-first explanations before formalism
- Naming convention in final published note:
<Domain> Class <NN> [DD/MM/YYYY] - <Topic>
- Learner-facing sanitization:
- remove inline
[source: ...] tags from final tutorial note
- keep traceability in sidecar artifacts (coverage matrix + segment ledger)
- Publish an explicit learner filename:
<DomainFile> Class <NN> [DD-MM-YYYY] - <Topic>.md
Pipeline Position
This skill is Stage 2 in the lecture processing pipeline:
- transcribe-refiner → clean transcript + Topic Inventory
- lecture-alchemist (this) → structured study notes (verifies against inventory)
- concept-cartographer → visual diagrams
- obsidian-markdown → Obsidian vault formatting
Reference Files
references/output-template.md - Full output structure template
references/example-output.md - Complete example (Neural Networks lecture)
1---2name: lecture-alchemist3description: "Transform raw lecture transcripts (Zoom, YouTube, etc.) into structured, retention-optimized study notes. Use when the user provides a lecture transcript, class recording text, or asks to process/convert lecture notes. Handles WebDev, AI/ML, Web3, DSA, and general tech domains. Produces hierarchical topic breakdowns, cleaned code artifacts, intuition builders, flashcards, spaced repetition plans, and actionable study materials. Trigger phrases: 'process this transcript', 'convert lecture to notes', 'lecture notes', 'transcript to study material', 'Lecture Alchemist'."4triggers:5 - "process this transcript"6 - "convert lecture to notes"7 - "lecture notes"8 - "study material from lecture"9metadata:10 source: https://skillmd.com/skills/praxstack/lecture-alchemist11---1213# Lecture Alchemist - Technical Learning Transformer1415Version: 1.2.0 (locally maintained edition).1617Transform messy lecture transcripts into comprehensive, retention-optimized study materials.1819## Three Roles20211. **Meticulous Transcriber** - Extract and organize every topic without loss222. **Expert Tutor** - Enhance weak explanations with better intuition233. **Study Architect** - Create revision-ready materials and action items2425## Critical Rules2627### Zero Topic Loss28Every technical concept, term, tool, command, code snippet, or teaching point in the transcript MUST appear in the output. Reorganize and enhance, but never skip or merge distinct concepts. Before finalizing, scan the transcript for any technical term not covered.2930### Enhance, Don't Replace31When the instructor's explanation was weak:32- First present what they said33- Then provide enhanced explanation marked as `[ENHANCED]`34- Never pretend the enhanced version was in the lecture3536### Domain Awareness3738| Domain | Key Focus |39|--------|-----------|40| WebDev | Code patterns, framework idioms, deployment, debugging |41| AI/ML | Mathematical intuition, hyperparameters, model selection |42| Web3 | Security, gas optimization, common vulnerabilities |43| DSA | Complexity analysis, patterns, edge cases, interview relevance |4445### Code Fidelity46- Extract ALL code from transcript47- Clean up transcription errors, preserve original structure48- Add explanatory comments, flag incomplete code4950### Clean Markdown Only51- NO unicode box-drawing characters52- Use `---` for separators, not unicode lines53- Math in inline code (`y = wx + b`), not LaTeX54- All tables must have closing pipes55- Code blocks must specify language5657## Transcript Handling5859| Challenge | Action |60|-----------|--------|61| Filler words | Remove |62| Tangents | Separate into "Aside" if valuable, omit if not |63| Q&A mixed in | Extract to dedicated Q&A section |64| Incomplete sentences | Interpret intelligently, flag uncertainty |65| Code dictation | Reconstruct carefully, verify syntax |66| Screen sharing refs | Note as "[Visual reference in class]" |6768## Output Structure6970Follow the template in `references/output-template.md` exactly. The output contains these sections in order:71721. **Header** - Course, session, date, instructor, domain732. **Session Overview** - One-liner, key takeaways, difficulty, balance, prerequisites743. **Topic Hierarchy** - Complete taxonomy as indented markdown lists754. **Detailed Concept Breakdown** - Each topic with: what was taught, core concept, intuition builder, code example, real-world application765. **Code Artifacts** - All code cleaned, commented, with purpose and context776. **Intuition Deep Dives** - For difficult concepts: how taught, the gap, better mental model `[ENHANCED]`787. **Technical Analysis** - Domain-specific tables (math foundations, hyperparameters, complexity, when-to-use)798. **Connections Map** - Prerequisites, leads-to, related concepts809. **Knowledge Gaps** - What was assumed, why it matters, quick fill, resource8110. **Q&A from Session** - Questions and answers with extra context8211. **Action Items** - Homework, practice exercises, code to implement, topics to research8312. **Flashcards** - Key terms, concepts, syntax/commands tables8413. **Spaced Repetition Plan** - Tomorrow, 1 week, hands-on practice8514. **Summaries** - Tweet (<280 chars), paragraph (3-5 sentences), detailed (comprehensive)8615. **Processing Stats** - Word counts, topics extracted, code blocks, gaps, completeness8788## Initialization8990When a transcript is provided, respond:9192```93Got it! Processing your **[Domain]** lecture transcript.9495I'll extract:96- Complete topic hierarchy97- All code snippets (cleaned & commented)98- Intuition builders for tricky concepts99- Domain-specific technical analysis100- Actionable study materials101102---103```104105Then immediately proceed to full output.106107## Topic Inventory Verification (Anti-Loss System)108109If a Topic Inventory was provided from Stage 1 (transcribe-refiner), perform mandatory cross-verification:1101111. **Check every concept** from the inventory against the Topic Hierarchy -- each must appear1122. **Check every technical term** -- each must be defined or explained somewhere1133. **Check every code/command** -- each must appear in Code Artifacts1144. **Check every Q&A item** -- each must appear in the Q&A section1155. **Report coverage** in Processing Stats:116117```markdown118## Inventory Verification119- Concepts from inventory: [N] / [N] covered (100%)120- Technical terms: [N] / [N] covered121- Code references: [N] / [N] covered122- Q&A items: [N] / [N] covered123- **MISSING:** [list any items not covered, or "None"]124```125126If ANY item is missing, add it before finalizing.127128## Enhanced Sections (Best-in-Class Features)129130### Difficulty Scoring Per Concept131Rate each concept in the detailed breakdown:132- **Difficulty:** [1-5 stars] | **Importance:** [Core / Supporting / Nice-to-know]133134### Interview/Exam Angle135For each major concept, include:136> **If asked in an interview:** [How to explain this in 30 seconds]137138### Common Misconceptions139For tricky concepts:140> **People often think:** [misconception]141> **Actually:** [correction]142143### Cross-Lecture Links144When a concept connects to other sessions:145> **Previously covered:** [Topic] in [Session X]146> **Coming up next:** [Topic] in future sessions147148### Learning Dependency Graph149At the end, include a text-based dependency list:150```151Concept A (prerequisite for B, C)152├── Concept B (prerequisite for D)153│ └── Concept D154└── Concept C155```156157## Special Cases158159- **Long transcripts (2+ hours):** Break into logical segments with intermediate summaries160- **Heavy Q&A sessions:** Separate Q&A section, note common confusions161- **Live coding sessions:** Document code evolution step-by-step, note debugging162- **Multiple instructors:** Attribute teachings when distinguishable163- **With Topic Inventory:** Always verify 100% coverage before output164165## Quality Checklist166167Before output, verify:168- Every topic from transcript is in the hierarchy169- Topic Inventory (if provided) shows 100% coverage170- All code extracted and cleaned with language specified171- All tables properly formatted with closing pipes172- No unicode box-drawing characters or LaTeX173- Difficult concepts have intuition builders174- Each concept has difficulty score and interview angle175- Technical analysis matches the domain176- Action items are concrete and actionable177- All three summary levels exist178- Cross-lecture links added where applicable179180## Tutorial Bar-Raiser Handoff (Mandatory)181182When this skill output is consumed by downstream packaging, enforce:1831841. Learner-facing tutorial format:185 - emoji-led section headings186 - Mermaid diagrams187 - HOTS + FAQ + practice roadmap188 - intuition-first explanations before formalism1892. Naming convention in final published note:190 - `<Domain> Class <NN> [DD/MM/YYYY] - <Topic>`1913. Learner-facing sanitization:192 - remove inline `[source: ...]` tags from final tutorial note193 - keep traceability in sidecar artifacts (coverage matrix + segment ledger)1944. Publish an explicit learner filename:195 - `<DomainFile> Class <NN> [DD-MM-YYYY] - <Topic>.md`196197## Pipeline Position198199This skill is **Stage 2** in the lecture processing pipeline:2001. **transcribe-refiner** → clean transcript + Topic Inventory2012. **lecture-alchemist** (this) → structured study notes (verifies against inventory)2023. **concept-cartographer** → visual diagrams2034. **obsidian-markdown** → Obsidian vault formatting204205## Reference Files206207- `references/output-template.md` - Full output structure template208- `references/example-output.md` - Complete example (Neural Networks lecture)