source-talks-workshops
Skill1 starsChanged 23 days agoMITView on GitHub
How to find conference talks, meetup recordings and hands-on workshops about a technology for a codelabgen course — especially workshops with a step-by-step repository — and read them through transcripts. Source type `talk-workshop`.
In this repository24 other files it gives its agents.
- code-authoringSkill
- codelabgen-orchestratorSkill
- course-extensionSkill
- curriculum-designSkill
- diagrammingSkill
- example-designSkill
- lesson-reviewSkill
- notes-writingSkill
- readalong-writingSkill
- runtime-strategySkill
- site-assemblySkill
- source-articlesSkill
- source-books-coursesSkill
- source-digestSkill
- source-evaluationSkill
- source-github-reposSkill
- source-official-blogSkill
- source-official-docsSkill
- source-package-internalsSkill
- source-papers-specsSkill
- source-qaSkill
- source-universitySkill
- state-protocolSkill
- topic-extractionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Prefer recordings with good subtitles, since agents can't watch video.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Talks and workshops (talk-workshop)
Talks by maintainers explain design decisions you won't find in the docs. Workshops are often small courses in themselves: a repo with numbered steps is a ready-made view of how to teach the topic.
Search
- WebSearch and YouTube:
<topic> talk,<topic> conference,<topic> workshop,<topic> tutorial PyCon(or JSConf, GopherCon, KubeCon, depending on the ecosystem), and the vendor's own events and channels. - GitHub:
codelabgen github repos "<topic> workshop". Look for repos withstep-01,exercises/,solutions/folders. - In the course language too, for example Russian conferences and meetups (
<topic> доклад,<topic> воркшоп).
Reading a talk
codelabgen transcript <video url> saves the subtitles as text in the cache (it uses yt-dlp, through uvx when not installed). Skim the transcript for the talk's structure and its key claims, and check that the speaker is a maintainer or an experienced user. Talks older than the pinned major version are only worth recording for their reasoning.
What to record
- Workshops with a step-by-step repo: the repo URL (
structure,code-truthwhen on the pinned version). Inreason, describe the steps briefly. - Talks by maintainers on design and internals (
concepts). - Talks on production experience (
pitfalls).
Prefer recordings with good subtitles, since agents can't watch video. Record the talk's page (the YouTube or conference URL) with the speaker and event in title.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.