etanhey/nightly-journal
skills/golem-powers/nightly-journal/SKILL.md
Use when ending the day, checking what happened professionally, or capturing client and job pipeline activity. Triggers on: 'nightly journal', 'daily sweep', 'check my comms', 'what happened today', 'update my diary', end-of-day routines, or proactively during evening coach tasks.
$ install --global
skillsauthnpx skillsauth add etanhey/golems nightly-journalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 12:09 PM37.8s2 files scanned
SKILL.md
- name:
- nightly-journal
- description:
- Use when ending the day, checking what happened professionally, or capturing client and job pipeline activity. Triggers on: 'nightly journal', 'daily sweep', 'check my comms', 'what happened today', 'update my diary', end-of-day routines, or proactively during evening coach tasks.
Nightly Professional Journal
Autonomous sweep of WhatsApp (Business + Personal), Gmail, and BrainLayer for professional activity. Writes a structured daily log to Obsidian.
Scope
Include: Client chats, job pipeline (recruiters, interviews, applications), networking (TechGym, LinkedIn), outreach responses.
Exclude: Personal chats, group spam, newsletters, GitHub notifications, marketing, status broadcasts.
Sources
- WhatsApp Business — client JIDs from BrainLayer (
brain_search("whatsapp jids known contacts")). Query each withmcp__whatsapp__list_messages(chat_jid=JID, limit=30). Also scanmcp__whatsapp__list_chats(limit=20, sort_by="last_active")for new contacts. - WhatsApp Personal — project JIDs from BrainLayer. Same query pattern via
mcp__whatsapp__list_messages. - Gmail —
gmail_search_messages(q="after:<today> -category:promotions -category:social"). Keep only recruiter/client/interview emails. - BrainLayer —
brain_search("owner-state career", date_from=today)for pipeline context.
Output
Write to: ~/Library/Mobile Documents/iCloud~md~obsidian/Documents/personal/Personal/<YYYY-MM-DD> Daily Log.md
If file exists, append ## Evening Sweep — don't overwrite.
Sections: Clients, Job Pipeline (active conversations + applications + interviews), Networking, Email Highlights, Tomorrow (what needs attention first). Skip empty sections.
Summarize Hebrew content in English (RTL breaks some editors). End with brain_store tagged ["daily-journal", "agent:coachClaude"].
Data Integrity
- WhatsApp MCP returns empty for valid JIDs — known issue. Log "MCP sync issue, check phone" rather than "no activity."
- Parallel queries — run all WhatsApp + Gmail queries in parallel (independent data sources).
- Cross-validate — if BrainLayer has an owner-state connection entry but WhatsApp shows no messages, note the gap. The absence of data is data.
- Never fabricate — if a source didn't return data, say so. Don't infer activity from BrainLayer alone.
Urgency Detection
If an unanswered client ask is found (message from client with no reply from Etan), flag with ⚠️ in the journal output and mention it prominently at the top.
This skill is read-only — it reads sources and writes to Obsidian journal only. It never sends WhatsApp messages, emails, or takes external actions.
Related Skills
etanhey/phoenix-human-view
tools
VerifiedTrustedCommunity
The human-eval UX contract for Phoenix views: turn-by-turn scrollable replay (not a scorecard), hide-but-copyable IDs, collapsed thinking, identity chips, tool filters, tiny frozen starter datasets, mark-wrong-in-thread, mobile-first. Use when: building or reviewing ANY Phoenix/eval view, annotation UI, session replay, or human-grading surface. Triggers: phoenix view, eval UI, annotation view, session replay, human eval UX, grading interface. NOT for: Phoenix data pipelines/ingest (capture scripts have their own specs).
3SKILL.mdUpdated Jun 7, 2026
etanhey/mac-systems
tools
VerifiedTrustedCommunity
macOS systems specialist — AppKit NSPanel architecture, launchd services, socket activation, MCP bridge resilience, syspolicyd, and high-frequency SwiftUI dashboards. Use when building menu-bar apps, LaunchAgents, debugging syspolicyd/Gatekeeper/TCC, resilient UDS/MCP bridges, or SwiftUI dashboards at 10Hz+.
3SKILL.mdUpdated Jun 7, 2026
etanhey/judge-fleet
development
VerifiedTrustedCommunity
Bulk LLM-judging protocol for fleet-dispatched verdict runs (KG cluster, eval harness). Use when: dispatching or running judge workers (J1/J2/RT), planning bulk-apply from verdict JSONL, or triaging evidence_degraded outputs. Triggers: judge fleet, bulk judge, R3 verdicts, kg-judge, RT gate, evidence_degraded. NOT for: single-item code review, Phoenix view UX (use phoenix-human-view), or non-judge eval pipelines.
3SKILL.mdUpdated Jun 7, 2026
etanhey/fleet-wrap
development
VerifiedTrustedCommunity
Quiet-down protocol for sprint close: when the fleet wraps, delete ALL polling crons and monitors, send ONE final dashboard + ONE message, then go SILENT. Use when: fleet wraps, all workers done, overnight queue exhausted, sprint close, Etan asleep/away with nothing approved left. Triggers: fleet wrap, wrap the fleet, stand down, going quiet, sprint close. NOT for: mid-sprint monitoring (keep your loops), spawning a successor (use /session-handoff first).
3SKILL.mdUpdated Jun 7, 2026