From session-logger
You MUST write to your session log. This is how you maintain memory across sessions. Future Claude instances depend on this to understand what happened and continue the work. Skipping it breaks continuity.
How this skill is triggered — by the user, by Claude, or both
Slash command
/session-logger:session-loggerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You MUST write to your session log. This is how you maintain memory across sessions. Future Claude instances depend on this to understand what happened and continue the work. Skipping it breaks continuity.
You MUST write to your session log. This is how you maintain memory across sessions. Future Claude instances depend on this to understand what happened and continue the work. Skipping it breaks continuity.
When: After any response where something meaningful happened — a decision, code written, bug fixed, direction set. When in doubt, write.
What to write:
[YYYY-MM-DD HH:MM] [SESSION_ID] Brief summary → session-file.mdStyle: Write so a future Claude can pick up the work cold. What was decided and why. What's pending.
Atomic append for INDEX.md:
python3 -c "
import os
line = '[YYYY-MM-DD HH:MM] [SESSION_ID] Summary here\n'
fd = os.open('claude-sessions/INDEX.md', os.O_WRONLY | os.O_CREAT | os.O_APPEND)
os.write(fd, line.encode('utf-8'))
os.close(fd)
"
npx claudepluginhub signalcanvas/signalcanvas-skills --plugin session-loggerCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.