new-track
Skill0 starsChanged 5 days agoMITView on GitHub
Create a new learning track in this vault (course, book, certification, interview, research, skill, language or other) from the recipe of its kind. Asks for the kind and the horizon. Use when the user starts learning something. Writes files, so only run when asked.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- drafthq/drafttheir own version, first seen Jul 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- drafthq/draft★ 40same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- adaptive-scaffoldSkill
- calibration-coachSkill
- compression-challengeSkill
- counterfactualSkill
- defuddleSkill
- dependency-checkSkill
- error-recoverySkill
- json-canvasSkill
- memory-palaceSkill
- misconception-drillSkill
- mistake-reviewSkill
- new-concept-noteSkill
- no-ai-checkpointSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- pretestSkill
- process-paperSkill
- process-webSkill
- quizSkill
- record-attemptSkill
- recovery-after-inactivitySkill
- retention-auditSkill
- review-queueSkill
- run-checksSkill
- schedule-reviewSkill
- spoken-mockSkill
- teach-the-agentSkill
- transfer-labSkill
- vault-searchSkill
- visual-reconstructionSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 0 are distinctive, and 8 are 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.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read the recipe for that kind in 90_System/Specs/Track_kinds.md.
- Very specific: line 11
Create the folder 10_Tracks/<NN>_<Track_Name>/ with underscores instead of spaces.
- Very specific: line 12
Create <Track_Name>.md from 90_System/Templates/Track.md with type: track, kind, horizon, goal, done_criterion, deadline, if_then, status: …
- Very specific: line 13
Create sessions/ (sessions come from 90_System/Templates/Session.md, named session-NN-<slug>.md) and practice/.
- Very specific: line 20
Every kind also gets Concept_Map.md: the learner orders the concepts by necessity.
- Very specific: line 21
When the track has a deadline, also copy Checkpoints.md and Plan_48h.md.
- Very specific: line 23
Run the run-checks skill and report each check as passed, failed or not run.
- Very specific: line 24
Add one line to 90_System/Agent_Log/YYYY-MM.md.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Tutor mode: the goal, the done criterion and the if-then plan are the learner's words. Ask for them and write what the learner says; do not invent them.
- Ask only for what is missing: the track name; the kind (
course,book,certification,interview,research,skill,language,other); the horizon (finiteends when the done criterion is met,ongoinghas no end); the goal; adone_criterionthat can be failed; thedeadline(finite only); oneif_thenplan ("If X, then I do Y"). - Read the recipe for that kind in
90_System/Specs/Track_kinds.md. - Create the folder
10_Tracks/<NN>_<Track_Name>/with underscores instead of spaces;NNis the next free number. - Create
<Track_Name>.mdfrom90_System/Templates/Track.mdwithtype: track,kind,horizon,goal,done_criterion,deadline,if_then,status: activeandorder. Fill## Setupand## Review cadencefrom the recipe. - Create
sessions/(sessions come from90_System/Templates/Session.md, namedsession-NN-<slug>.md) andpractice/. Copy the kit for the kind from90_System/Templates/Practice/intopractice/, settingtrack: "[[<Track_Name>]]":certification:Blueprint_Map.md.interview:Problem_Log.md.language:Input_Log.mdandOutput_Sample.md.research:Synthesis_Matrix.md.skill:Attempt_Log.md.course,book,other:Checkpoints.md. Every kind also getsConcept_Map.md: the learner orders the concepts by necessity; you point out missing prerequisites. When the track has a deadline, also copyCheckpoints.mdandPlan_48h.md.
- The track appears in
00_Home.mdthroughTracks.base; nothing to add by hand. - Run the
run-checksskill and report each check as passed, failed or not run. - Add one line to
90_System/Agent_Log/YYYY-MM.md.
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.

