learner-profile-teach
Personalized teaching companion for the existing teach skill. Use for learning, teaching, course design, next lesson, research derivation, electromagnetic computation, code engineering, tool integrati
SKILL.mdskills/learner-profile-teach/SKILL.md
GitHubLearner Profile Teach
Use this skill as the personalization layer around teach. It supplies the
stable learner model; teach manages the current course workspace; Obsidian
stores durable notes, concept cards, derivations, review evidence, Bases views,
and profile update proposals.
Loading Workflow
At the start of a learning, teaching, research-derivation, or cognition/planning task:
- Run the Obsidian profile sync script:
cd ~/.codex/skills/learner-profile-teach python3 scripts/sync_learner_profile.py - If sync returns
STATUS=lowor exits nonzero, stop before teaching and ask the user to resolve the reported issue. - Read
references/global-profile.md. - Read
references/teaching-protocol.mdfor lessons, courses, next lesson, or teaching requests. - Read
references/research-workflow.mdfor research, derivation, engineering, implementation, validation, or tool-integration work. - Read
references/cognition-and-planning.mdfor planning, future direction, decision-making, emotion regulation, or cognitive improvement. - Read the current teach workspace state when available.
- Use current user messages as the highest-priority signal when they conflict with older profile notes.
Load only references relevant to the task. Do not load every reference by default.
Obsidian Integration
When a task writes durable learning material, use the Obsidian integration references as needed:
- Read
references/obsidian-integration.mdfor vault layout and artifact split. - Read
references/obsidian-properties-schema.mdbefore writing Obsidian notes. - Read
references/obsidian-linking-policy.mdbefore writing lesson, concept, derivation, review, or profile-proposal notes. - Read
references/obsidian-bases.mdwhen creating, repairing, or querying.basefiles. - Read
references/obsidian-cli-protocol.mdwhen using theobsidianCLI. - Read
references/validation.mdbefore declaring Obsidian work complete. - Read
references/gotchas.mdwhen sync, CLI, Bases, or profile-update behavior looks surprising.
Prefer bundled scripts for repeatable Obsidian operations:
python3 scripts/write_obsidian_note.py --help
python3 scripts/generate_learning_bases.py --help
python3 scripts/generate_learning_canvas.py --help
python3 scripts/validate_obsidian_learning_system.py --help
python3 scripts/install_or_repair.py --help
Lesson Protocol
For substantial lessons, follow references/teaching-protocol.md.
End substantial lessons by asking the user to:
- Explain the core concept in their own words.
- Transfer it to one research, engineering, management, planning, or life scenario.
- Name one unclear, uncertain, or disputable point.
Use the answer to identify knowledge boundaries, learning pace, interest signals, and difficulty patterns. Keep ordinary lesson outcomes in the teach workspace and Obsidian; do not immediately update the stable profile.
Five-Lesson Review
Do not update the stable learner profile after every lesson.
After every five substantial lessons in a course or learning thread:
- Read
references/update-protocol.md. - Use
templates/five-lesson-review.md. - Inspect the last five lesson notes, learning records, Obsidian notes, and user self-explanations.
- Decide whether stable, cross-course evidence warrants a profile update.
- If yes, draft
templates/profile-update-proposal.mdinto the Obsidian sourceSelf/learner-profile/proposals/. - Ask the user to confirm before editing stable profile files.
No silent profile updates. Profile updates require explicit user confirmation unless the user directly asks to write a specific update.