Keeps the principal current on the fundamentals of what is going on in the principal's projects, work and technical infrastructure: spoken interactive lessons on the conversation topic, deep explanations of an area's fundamentals read fresh from live sources, and quizzes that remember what the principal missed
The thinking, frameworks, and architecture that distinguish this skill from a generic version of the same task.
| Intent | Trigger | File |
|---|---|---|
| Teach | "teach me", "/tm", "/teach-me", "tutorial", "quiz me" on what we just covered | Intents/Teach.md |
| ExplainFundamentals | "/ef", "explain the fundamentals of", "catch me up on", "how does X actually work" | Intents/ExplainFundamentals.md |
| QuizFundamentals | "/qf", "quiz me on the fundamentals of", "test what I know about", "am I still current on" | Intents/QuizFundamentals.md |
| File | Read when |
|---|---|
Setup.md |
first-time setup: the voice server and Fish key the spoken narration needs, and a read-only check |
Teach works on the conversation topic as a spoken dialogue. ExplainFundamentals and QuizFundamentals work on a standing area (a project, a work stream, a system) whether or not we touched it this session, and share one set of fundamentals per area so the quiz tests what the explanation taught.
e shortcut is not this skill. It explains my last answer more, and more simply; /ef explains an area's fundamentals.Example 1: Teach the thing we just built
User: "teach me" (after a session debugging DNS records)
→ Teach intent
→ Spoken intro, a concept map of 3-5 ideas, one beat and one question per turn
→ Ends with a 2-3 question quiz and a recap diagram
Example 2: Explain an area's fundamentals
User: "/ef billing service"
→ ExplainFundamentals intent
→ Reads its projects-table row, the project ISA and its code layout this session
→ The fundamentals by the "without X it can no longer ___" test, each with what it connects to, one flow diagram, what changed lately
Example 3: Quiz on fundamentals
User: "/qf home network"
→ QuizFundamentals intent
→ Reads the live sources and the learning record, asks 5 application questions one per turn, weighted to past misses
→ Each answer gets a verdict against the source and is appended to the STATVS learning stream
Each workflow is one job the skill runs. The trigger phrases route your request to the right one — this is the skill's routing table.
Intents/Teach.md teach me, /tm, /teach-me, tutorial, quiz me on what we just covered
Intents/ExplainFundamentals.md /ef, explain the fundamentals of, catch me up on, how does X actually work
Intents/QuizFundamentals.md /qf, quiz me on the fundamentals of, test what I know about, am I still current on
Say any of these to your DA and LifeOS activates the Explain skill automatically:
Or invoke explicitly:
Skill("Explain")Auxiliary files the skill loads at runtime — frameworks, guides, configs.
Install LifeOS on your machine — your DA gets the Explain skill plus 96 others, all hooked into one Life OS.