myelinate
AGENTS.md4 starsChanged 2 days agoMITView on GitHub
myelinate.md is the authored router skill and skills/<name>/SKILL.md are its fifteen sub-skills (tutor, teach, assignment, project, code, assess, course-project, notes, lab, print, flashcards, memory-hooks, study-plan, find-media, verify). The repo is one plugin for Claude Code, the Claude apps and Codex (.claude-plugin/, .codex-plugin/, marketplace baney75). skills/myelinate/ and the references/, templates/, examples/, scripts/ and assets/ folders inside each skill folder are generated by python3 scripts/check.py --sync from the root sources: edit the root files, never the copies. Paths in a skill are…
Files
Working on Myelinate
myelinate.md is the authored router skill and skills/<name>/SKILL.md are its fifteen sub-skills (tutor, teach, assignment, project, code, assess, course-project, notes, lab, print, flashcards, memory-hooks, study-plan, find-media, verify). The repo is one plugin for Claude Code, the Claude apps and Codex (.claude-plugin/, .codex-plugin/, marketplace baney75). skills/myelinate/ and the references/, templates/, examples/, scripts/ and assets/ folders inside each skill folder are generated by python3 scripts/check.py --sync from the root sources: edit the root files, never the copies. Paths in a skill are relative to its own folder; sibling skills are ../<name>/SKILL.md. Leave version out of .claude-plugin/plugin.json so installs update by commit; keep .codex-plugin/plugin.json's version equal to the router's. every sub-skill auto-loads on its description, so descriptions must trigger on learning intent and never on ordinary coding or work requests. Keep each description 175 characters or less, double-quoted, and opening with "Use when" or "Use for": skill listings drop long descriptions once their budget runs out, and a skill listed by name alone never auto-loads. Run claude plugin validate . after manifest changes. SKILL.md is the router's generated install entrypoint; after changes run python3 scripts/check.py --sync and review both. Keep references conditional and the core usable when pasted alone.
Teach in chat by default. Do not gate explanations behind intake, health disclosure, or a quiz. Ask course learners for their study guide, syllabus, notes, and textbook/edition. Ask what helps and what gets in the way in everyday terms; a learner may share a learning condition if they choose, but it is never required, inferred, or repeated back as a label. Teaching stays honest, not agreeable. Keep learner records, private courses, and diagnostic disclosures out of this repository.
Claims need sources and limits. Never claim forced permanent memory, measured myelination, clinical efficacy, guaranteed grades, or proven efficacy of this package. Hinted/revealed work is not independent success. Reminders require real scheduling support.
Check package integrity with python3 scripts/check.py. For behavioral changes, use the relevant cases in evals/scenarios.md with a fresh agent, and inspect its response. For demo changes, inspect desktop/mobile renders and exercise answer, invalid input, hint, reveal, and reset. Record exactly what was tested; simulated learners do not establish learning gains.
The router must stay usable alone: its core rules are the minimum standard when sub-skill files are missing. Sub-skills reference each other by name and by skills/<name>/SKILL.md. Run verify's adversarial review on substantive teaching changes, and keep examples/oxygen-lab.html passing its journey test when the lab engine or template changes. Brand rules live in assets/brand.md.
The repo must work when someone simply pastes its URL into any assistant: keep SKILL.md self-sufficient, keep llms.txt accurate, and keep the fetch URLs in the router valid (the current version tag and main). Bump the version line in myelinate.md and tag a release for behavior changes.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- myelinateSkill
- assessSkill
- assignmentSkill
- codeSkill
- course-projectSkill
- find-mediaSkill
- flashcardsSkill
- labSkill
- memory-hooksSkill
- myelinateSkill
- notesSkill
- printSkill
- projectSkill
- study-planSkill
- teachSkill
- tutorSkill
- verifySkill
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.

