lesson-content-writer
Skill1 starsChanged 6 months agoMITView on GitHub
Write the body of a course lesson following the lesson template (intro/concepts/exercises/answer key). Use when Andy says write lesson N, fill out lesson X, build out week Y.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- commit-message-writerSkill
- compile-topicSkill
- course-builderSkill
- daily-note-writerSkill
- deck-builderSkill
- diagnoseSkill
- drift-fixSkill
- forgeSkill
- git-bootstrapSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- project-scaffolderSkill
- prototypeSkill
- retroSkill
- reviveSkill
- setup-pre-commitSkill
- specialist-creatorSkill
- sweep-inboxSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- workflow-authorSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 59
Don't write all 12 lessons in one go - one at a time
- Distinctive: line 60
Don't skip exercises - that's where learning happens
- Distinctive: line 61
Don't add tangential concepts - the lesson stays scoped
≈ “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
Lesson Content Writer
When to use
Triggers: write lesson N, fill out lesson X, build out week Y, draft this lesson.
Load
03 - Skills & Rules/Rules/course-format.md- lesson template03 - Skills & Rules/Agents/Specialists/lesson-writer.md- canonical spec- Writer's universal memory for tone:
03 - Skills & Rules/Agents/memory/Writer/universal.md - Existing lesson 1 as reference:
13 - Courses/fundamentals-of-coding/week-01-*/lesson-01-*.md
Confirm
- Which course + week + lesson
- Specific concept(s) the lesson covers
- Difficulty assumption (what did the prior lesson cover?)
Structure
---
type: lesson
course: <slug>
week: N
status: in-progress
created: <date>
tags: [lesson]
---
# Lesson <NN>: <Title>
## Intro
Why this matters in 2-3 sentences. Concrete hook.
## Concepts
- Core idea 1 (with code example)
- Core idea 2 (with code example)
- Core idea 3 (with code example)
## Try it
3-5 progressive exercises. Each: clear prompt, expected behavior.
## Answer key
Collapsed by default. One solution per exercise with brief explanation.
## Next
What lesson <NN+1> will cover.Tone (per Writer memory)
- Warm, direct, professional. Human, not corporate.
- No "honestly", "genuinely", "feel free to", "great question".
- Sentence case. Length matches substance.
Don't
- Don't write all 12 lessons in one go - one at a time
- Don't skip exercises - that's where learning happens
- Don't add tangential concepts - the lesson stays scoped
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.

