etanhey/mehayom
skills/golem-powers/_archive/mehayom/SKILL.md
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'.
$ install --global
skillsauthnpx skillsauth add etanhey/golems mehayomInstall 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:15 PM10.3s6 files scanned
SKILL.md
- name:
- mehayom
- description:
- 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'.
MeHayom Client Management
Three interconnected workflows for managing the MeHayom freelance engagement with Yuval Nir.
Why This Exists
April 13, 2026: Yuval escalated — checkpoints not delivered, hours burned without warning, code pushed without discussion. Nearly ended the relationship. Root cause: no daily updates, no proactive hour tracking, no decision trail. These workflows prevent that from happening again.
Client Profile
| Field | Value | |-------|-------| | Client | Yuval Nir, partner Lior | | App | MeHayom — anti-porn addiction, 8K+ downloads | | Language | Hebrew, casual, non-technical | | Rate | 140 NIS/hr (30hr blocks), overage 160 NIS/hr | | Tools | Linear (tickets), TestFlight/EAS (builds), WhatsApp (comms) | | Priority | SPEED above everything |
Workflows
| Workflow | Trigger | What it does | |----------|---------|-------------| | daily-update | "draft Yuval update", "client update", end of work day | Draft structured async standup in Hebrew | | decision-tracking | Scope change, hour overrun, feature pivot, "log decision" | Store WHO/WHAT/WHY/WHEN immediately | | time-tracking | Start/stop work, "track time", "log hours" | Log human vs agent vs wall-clock time |
How They Connect
Time Tracking ──feeds──> Daily Update (hours worked today)
Decision Tracking ──feeds──> Daily Update (scope changes to mention)
Daily Update ──references──> both (pulls data for standup)
Hebrew Voice Rules (from 6 rounds of corrections)
These rules apply to ALL client-facing Hebrew output:
NEVER
- Start with name greeting on WhatsApp ("יובל," — just start with content)
- Include branch names, PR numbers, or git terminology
- Ask "should I...?" questions — state what you need
- List bugs in the message — defer: "מצאתי כמה באגים, אתעד ונעבור ביחד"
- Use technical jargon — "componentization" = "סידור וצמצום הקוד"
- Offer options that make the client work
- Use "מונה" when "מספור" is more natural
- Label bugs with technical terms — describe what the user will SEE
ALWAYS
- Status in first line (what's done)
- Collaborative framing: "ונעבור על זה ביחד"
- Max 2 options, never 3
- Casual tone: "אז ככה," to start explanations
- Explain WHY you waited: "חיכיתי תביקורת מכם"
- Reference their tools: "הטיקטים בלינאר" not "features"
- "ראיתי ש..." to show proactive tracking
- Specific ask > open question
- Group chat = plural verbs ("תבדוקו" not "תבדוק")
- For issues: [what client will see] + [what we'll do about it]
- "מעולה." alone is enough acknowledgment
- Comma not dash: "עוד דבר שמצאתי, המפתח..." not "עוד דבר שמצאתי - מפתח..."
Word Choices
| Wrong | Right | Why | |-------|-------|-----| | חילצתי | הוצאתי | More natural | | מונה | מספור | More natural for counter | | שמהבהב | שמראה | Describe what it DOES not how it LOOKS | | לשנייה | לרגעים ראשונים | Less precise, more natural | | בכניסה | לאחר התחברות | More formal/correct for "after login" | | מסיים עד סוף השבוע | ממשיך היום | Signal active work NOW |
Data Sources
- Voice corrections: BrainLayer
brain_search("user-correction hebrew voice-calibration yuval") - Entity:
brain_entity("Yuval Nir") - Files: Obsidian
Clients/MeHayom/ - Contract: Obsidian
Clients/MeHayom/sprint2-approval.md
Critical Rule
Updates go to Etan's self-chat first, NEVER directly to the client. The draft is for Etan to review, edit, and send himself.
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