claudetools/.grok/skills/save/SKILL.md

name, description

name	description
save	Save a comprehensive session log to the appropriate `session-logs/` directory, then sync the repo. Use when the user invokes /save, says "save the session", "log this work", "save session log", "checkpoint the context", or similar. Triggers after significant work, at end of day, before switching machines.

/save — Comprehensive Session Log + Sync

Save a comprehensive session log to the appropriate session-logs/ directory, then sync the repo.

/save and /sync share bash .claude/scripts/sync.sh as the canonical driver for git operations. The only difference: /save writes a session log first, then calls sync. /sync calls sync directly (no log).

Grok note (coexistence): This is the native Grok skill wrapper for the shared ClaudeTools command. The complete detailed specification, required sections, location rules, and phase-by-phase instructions live in the authoritative source .claude/commands/save.md. When this skill is activated:

1. Use the read_file tool to load .claude/commands/save.md (and related like whoami-block.sh output).
2. Follow its instructions precisely.
3. Adapt for Grok's tool set:
   • Shell commands → run_terminal_command
   • Sub-agents / delegation → spawn_subagent (with appropriate subagent_type like "general-purpose")
   • File reads → read_file
   • Edits → search_replace
4. Still obey the top-level CLAUDE.md contract for this repo: Coordinator posture (delegate heavy work), no emojis, use [OK]/[ERROR] ASCII markers, session start protocol (identity, mode, coord messages/locks), etc.
5. For narrative sections marked "(Ollama)", you can use local models per identity or direct reasoning; keep factual.

Quick Reference (from source)

Location rules

• Single project: projects/<project>/session-logs/YYYY-MM-DD-session.md
• Client: clients/<slug>/session-logs/YYYY-MM-DD-session.md
• General/multi: session-logs/YYYY-MM-DD-session.md

Required sections (order)

1. User block — run bash .claude/scripts/whoami-block.sh and paste verbatim.
2. Session Summary
3. Key Decisions
4. Problems Encountered
5. Configuration Changes
6. Credentials & Secrets (unredacted if new)
7. Infrastructure & Servers
8. Commands & Outputs
9. Pending / Incomplete Tasks
10. Reference Information

Append updates to existing same-day file with ## Update: HH:MM ... header.

After writing the log, perform the sync (git add, commit if needed, push).

See the full .claude/commands/save.md and .claude/commands/README.md (and related skills like checkpoint, scc) for complete flows, error handling, and examples.

When in doubt, include MORE detail — these logs are searched by future sessions and wiki-compile.