ilamanov/lecture-notes
skills/lecture-notes/SKILL.md
Transform a plain-text video lecture transcript into clean, skimmable markdown study notes. Use when the user provides a lecture transcript (or a file containing one) and wants structured notes, a summary, or a study reference from it. Triggers on requests like "make notes from this lecture", "summarize this transcript", "turn this lecture into notes", or when a transcript file is provided with a request for notes.
data-ai
Updated May 25, 2026
$ install --global
skillsauthnpx skillsauth add ilamanov/skills lecture-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 25, 2026, 2:17 AM13.3s1 file scanned
SKILL.md
- name:
- lecture-notes
- description:
- Transform a plain-text video lecture transcript into clean, skimmable markdown study notes. Use when the user provides a lecture transcript (or a file containing one) and wants structured notes, a summary, or a study reference from it. Triggers on requests like "make notes from this lecture", "summarize this transcript", "turn this lecture into notes", or when a transcript file is provided with a request for notes.
Lecture Notes
Transform a video lecture transcript into a well-structured markdown document optimized for skimming and review.
Input
A plain-text transcript of a video lecture, provided either as:
- A file path to a
.txtor.mdfile - Text pasted directly into the conversation
Read the entire transcript before producing notes.
Process
- Read the full transcript to understand scope, structure, and key themes
- Identify the natural topic boundaries — where the lecturer shifts subjects
- Extract key concepts, definitions, examples, and takeaways per topic
- Write the notes document following the output structure below
Output Structure
Save the output as a markdown file. Use the lecture title or topic as the filename (e.g., intro-to-neural-networks.md). If unclear, ask the user or derive from content.
Document layout
# [Lecture Title]
> **TL;DR:** [2-3 sentence summary of the entire lecture]
> **Key Takeaways:**
> - [3-5 most important points from the lecture]
---
## [Topic 1 heading]
[Concise notes as bullets — one idea per bullet]
- **Bold** key terms and definitions inline
- Use sub-bullets for supporting details or examples
- Include concrete examples the lecturer gave
## [Topic 2 heading]
...
---
## Glossary
| Term | Definition |
|------|-----------|
| ... | ... |
## Mentioned Resources
- [Any books, papers, tools, links, or names the lecturer referenced]
Formatting rules
- Use
##for major topic sections,###for subtopics within a section - Bold key terms, names, and definitions on first use
- Use bullet points, not paragraphs — one idea per bullet
- Use sub-bullets (
-) for examples, clarifications, or supporting details - Use
>blockquotes for direct quotes worth preserving verbatim - Use tables for comparisons or structured data the lecturer presents
- Keep bullets concise — aim for 1-2 lines each, not full sentences when possible
- Omit filler, repetition, tangents, and off-topic remarks
- Preserve the lecturer's logical flow — do not reorder topics
- Include the Glossary section only if the lecture introduces 3+ domain-specific terms
- Include the Mentioned Resources section only if the lecturer references external materials
- Omit the
---dividers between sections if the document is short (< 5 sections)
Related Skills
ilamanov/session-atlas
development
VerifiedTrustedCommunity
Map every Codex and Claude Code session for a project to the git worktrees they ran in, in an interactive local UI. Use whenever someone wants to see, search, audit, or clean up past AI coding-agent conversations and the worktrees those ran in — e.g. "what Codex sessions ran on this repo", "list my Claude Code sessions", "which worktree was that session in", "find the chat where I refactored auth", "archive old Codex sessions", or "show every session across my worktrees". Reach for it to untangle which of many worktrees still has live agent history attached. This is about Codex and Claude Code transcript history plus git worktrees — not HTTP, login, or auth sessions, not terminal or tmux sessions, and not user-research sessions.
SKILL.mdUpdated Jun 9, 2026
ilamanov/codebase-conventions
tools
VerifiedTrustedCommunity
Generally-applicable conventions for how code is written and arranged — tooling/package manager, import style, file & component naming, comments, and where files live (colocation vs. global folders). Use whenever creating, naming, moving, or importing a file, running project commands, or deciding where a new module belongs. Consult BEFORE writing the code so the conventions are baked in, not retrofitted. If a convention below matches the work, apply it — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 30, 2026
ilamanov/frontend-patterns
development
VerifiedTrustedCommunity
Generally-applicable frontend/UI best practices. Use whenever building, modifying, or reviewing UI — adding a form/button/dialog/modal, wiring keyboard shortcuts, creating any interactive surface that submits a form, or any time TSX/JSX is being written or edited. Consult BEFORE writing the code so the patterns are baked in, not retrofitted. If a scenario described in the skill body matches the work, apply the pattern — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 26, 2026
ilamanov/backend-patterns
tools
VerifiedTrustedCommunity
Generally-applicable backend/data best practices. Use whenever writing or modifying backend/data code — API routes, server actions, DB writes, background jobs, agent tools, import flows, webhooks, paste handlers, or anywhere data enters the system. Consult BEFORE writing the code so the patterns are baked in, not retrofitted. If a scenario described in the skill body matches the work, apply the pattern — don't ask, just follow it (call out the choice in one line so the user can override).
SKILL.mdUpdated May 26, 2026