eodlisted

Run the End-of-Day review for the trading journal (CLAUDE.md Section 12, at /Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md). Global, MCP-only — writes exclusively to the trading-journal MCP server, no markdown output. Auto-detects the gap since the last closed-out day, classifies each as PENDING or MISSED, then runs the full review. Invoke every evening.
latuconsinafr/claude-code-config · ★ 0 · AI & Automation · score 65

Install: claude install-skill latuconsinafr/claude-code-config

# End of Day Review (global, MCP-only) **Replaces the old project-local `/eod`** (formerly at `Journals/.claude/skills/eod/`, deferring to `Journals/PROMPTS.md`). See `sod/SKILL.md`'s header for the same reasoning — that file is left in place, unused. `CLAUDE.md` at `/Users/latuconsinafr/Personal/Trading/Journals/CLAUDE.md` remains the rulebook; Section numbers below point there. **If anything this session suggests a rule should change**, per CLAUDE.md §20.14: add it to CLAUDE.md §21.3, do not act on it. Rule changes belong at quarter boundaries (§13). **Instruments — resolved live via `get_active_instruments`, never hardcoded.** Call it alongside Step 0's connectivity check and use its result for the rest of this session — do not assume EU/GU/UJ/XAU is still the active set (CLAUDE.md §2). Every MCP tool's `instrument` parameter needs the full pair code it returns (`EURUSD`, not the shorthand this file still uses for readability). ## Step 0 — confirm the MCP server is reachable Same as `sod/SKILL.md` Step 0 — call `get_account_state` first. If it fails, stop, explain `just run` needs to be running, and do not silently proceed as if anything here will be recorded. ## Step 1 — resolve the date, and scan the FULL gap via MCP state, not files **Do not default to today's calendar date, and do not stop at the first pending day found.** The old file-existence table (`verdict_summary.md` / `eod_review.md`) has a direct DB equivalent — call **`get_session_completeness`** (rece