etanhey/nightly-journal
skills/golem-powers/_archive/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/writing-skills
development
VerifiedTrustedCommunity
Create, edit, and verify golem-powers skills using the standard SKILL.md structure, workflow files, adapters, templates, and eval fixtures. Use for new skills, structural edits, workflows/adapters, and pre-deploy validation. NOT for invoking existing skills, superpowers skills, or skill-creator agent workflows.
3SKILL.mdUpdated Jun 4, 2026
etanhey/video-extract
testing
VerifiedTrustedCommunity
Extract structured knowledge from any video source — YouTube URLs or local screen recordings. YouTube → gems workflow (yt-dlp transcript → keyword hotspots → frame extract → brain_digest → structured gems). Screen recordings → QA workflow (reuses /qa-video stalker pipeline). Use when user shares a YouTube link wanting deep extraction with frames, shares a .mov/.mp4 for QA processing, says "extract from video", "video gems", "process this recording", or mentions gem extraction from video content.
3SKILL.mdUpdated Jun 4, 2026
etanhey/monitor-loop
testing
VerifiedTrustedCommunity
Use when running or reviewing any recurring monitor loop for merge queues, worker queues, collab tails, or agent completion. Enforces drive-to-completion ticks: every tick must query live state with `!`, classify whether real progress happened, and then dispatch, verify-and-decrement, or escalate-park. Triggers on: monitor loop, /loop, recurring tick, keep monitoring, silent autonomous, merge gate, blocked review, no-progress loop.
3SKILL.mdUpdated Jun 4, 2026
etanhey/mehayom
tools
VerifiedTrustedCommunity
MeHayom freelance client management — daily updates, decision tracking, time logging. Use when drafting Yuval updates, logging scope changes, tracking hours, or any MeHayom client communication. Triggers: 'draft Yuval update', 'client update', 'daily update', 'log decision', 'track time', 'mehayom'.
3SKILL.mdUpdated Jun 4, 2026