← ClaudeAtlas

eveninglisted

Run EOD + SOD together for the trading journal — the pilot's actual nightly routine. Global, MCP-only, composes the global sod and eod skills. Invoke every evening instead of running them separately.
latuconsinafr/claude-code-config · ★ 0 · AI & Automation · score 65
Install: claude install-skill latuconsinafr/claude-code-config
# Evening Session — EOD + SOD together (global, MCP-only) **Replaces the old project-local `/evening`.** Composes `sod/SKILL.md` and `eod/SKILL.md` (both now global, MCP-only) — it does not duplicate their content, and does not read or write `journal/`, `metrics/`, `account/`, or `PROMPTS.md`. `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook. **Why the order matters and why the dates differ:** a SOD verdict written tonight (~21:00) governs trading through tomorrow night's session. So the EOD half of tonight's sitting closes out a **different, earlier calendar date** than the SOD half opens. Running EOD before SOD also means tonight's fresh verdict is informed by how the prior one actually played out. **Instruments — resolved live via `get_active_instruments`.** This file uses EU/GU/UJ/XAU shorthand like CLAUDE.md does for readability, but the active set is not assumed fixed — the composed `sod`/`eod` steps below each call `get_active_instruments` and use its full pair codes for every MCP call. See `sod/SKILL.md`'s header for why a hardcoded table isn't used (a rejected call during its own smoke test, 2026-08-18, back when it was one). ## Step 0 — check what day it actually is **The forex market is closed Saturday and most of Sunday.** - **Saturday** → no evening session. Point to `/week-end` if that week hasn't been closed out yet. Stop. - **Sunday** → no evening session — Friday's flatten closed everything and nothing has