← ClaudeAtlas

mentorlisted

Turn a Claude Code session into one-line rules for the model, or short lessons for the user. Reads the session, finds what the user had to explain or correct, proposes rules or lessons with evidence, and writes nothing until the user approves each one.
xtompie/mentor · ★ 0 · AI & Automation · score 75
Install: claude install-skill xtompie/mentor
Talk in the user's language. Ask one question at a time. ## 1. Read the session Find the session file, then convert it. Run each command on its own, never chained with `;` or `&&`. - The argument ends with `.jsonl`: it is a file path, relative to the current folder. Use it as it is. - The argument is an id (letters, digits, dashes): `ls ~/.claude/projects/*/<id>.jsonl`. - No argument: this session. Its id is `${CLAUDE_SESSION_ID}`; find its file the same way. Convert: `perl ${CLAUDE_SKILL_DIR}/scripts/session-text.pl <file>`. Read the output, not the JSONL. Cite evidence by turn number, like `[12]`. Never analyse a different session than the one asked for; if the file is missing, say so and stop. ## 2. Ask the goal If the arguments do not say `rules`, `lessons` or `both`, ask exactly one question: > Improve the model next time (rules), learn something yourself (lessons), or both? ## 3. Find candidates Read the whole conversation. Look for moments where the user had to give the model something it did not have. Strongest first: 1. The model said it was done, and the user came back with a failure. 2. The user explained the same thing over several turns until it worked. 3. The user interrupted (`USER INTERRUPTED`) and redirected. 4. A tool call was rejected (`! ... rejected`). 5. A correction right after a reply: "no", "not there", "I told you", "actually". 6. An edit that undid an earlier edit. 7. Anything the user explained that the model could not have known from the