Menu
End-of-day consolidation — summarize daily log, track belief changes and customer conversations, promote durable facts to MEMORY.md
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Autonomously set up an OpenClaw bot on a fresh DigitalOcean Droplet (Ubuntu 24.04, default region Frankfurt fra1). Asks the user for exactly two things — a Telegram bot token and one of three LLM access options (Anthropic API key, OpenRouter API key, or OpenAI Codex OAuth via ChatGPT Plus/Pro subscription) — then handles a DigitalOcean API token check, SSH-key upload, Droplet creation, Cloud Firewall, OS hardening, OpenClaw install, CEO AI OS workspace seeding, Telegram pairing, chat_id auto-detection, and bot-reply verification on its own. The only other actions the user performs are pasting a DigitalOcean API token once, pressing /start in Telegram once, and (if Codex) confirming a device code on auth.openai.com. Use when the user says install OpenClaw to DigitalOcean, deploy OpenClaw to a DO Droplet, set up my CEO bot on DigitalOcean, spin up an OpenClaw droplet, create a DigitalOcean VM for OpenClaw, or any close paraphrase. Targets a ~15-minute end-to-end run for non-DevOps users (founders, CEOs, marketi
Autonomously set up an OpenClaw bot on a fresh Hetzner Cloud VM (Falkenstein, Germany — fsn1 — by default; switchable to Helsinki/Nuremberg/Ashburn/Hillsboro/ Singapore). Asks the user for exactly two things — a Telegram bot token and one of three LLM access options (Anthropic API key, OpenRouter API key, or OpenAI Codex OAuth via ChatGPT Plus/Pro subscription) — then handles Hetzner SSH-key upload, firewall creation, VM provisioning, hardening, OpenClaw install, CEO AI OS workspace seeding, Telegram pairing, chat_id auto-detection, and bot-reply verification on its own. The only other actions the user performs are pressing /start in Telegram once and (if Codex) confirming a device code on auth.openai.com. Use when the user says install OpenClaw to Hetzner, deploy OpenClaw to Hetzner Cloud, set up my CEO bot on Hetzner, create a Hetzner VM for OpenClaw, поставь openclaw на hetzner, разверни бота в Hetzner, or any close paraphrase. Targets a ~15-minute end-to-end run for non-DevOps users (founders, CEOs, marke
Autonomously set up an OpenClaw bot on a fresh Yandex Cloud VM in Kazakhstan (kz1-a, Karaganda). Asks the user for exactly two things — a Telegram bot token and one of three LLM access options (Anthropic API key, OpenRouter API key, or OpenAI Codex OAuth via ChatGPT Plus/Pro subscription) — then handles VM creation, hardening, OpenClaw install, CEO AI OS workspace seeding, Telegram pairing, chat_id auto-detection, and bot-reply verification on its own. The only other actions the user performs are pressing /start in Telegram once and (if Codex) confirming a device code on auth.openai.com. Use when the user says install OpenClaw to Yandex Cloud, deploy OpenClaw to YC Kazakhstan, set up my CEO bot in YC KZ, I am at OpenClaw workshop and need my own bot, create a Yandex Cloud VM for OpenClaw, or any close paraphrase. Targets a ~15-minute end-to-end run for non-DevOps users (founders, CEOs, marketing leads). Supports two modes of accessing Yandex Cloud — Plan A (the user's own YC Kazakhstan account via OAuth) and
After an OpenClaw bot is freshly installed (via install-openclaw-to-yc or any other path), collect a small set of basic facts about the user — name, role/company, what matters this week, communication preferences, tools they live in, and anti-patterns — and write them into the bot's USER.md on the remote VM via SSH. This is the difference between a bot that answers generically and one that knows from the very first message who it's talking to. Use when the user says onboard me, knowing me, set up my profile, finish setup, последний шаг, расскажу о себе, познакомимся, who I am, or whenever install-openclaw-to-yc has just successfully completed Step 5 and is handing off. Runs in 2-5 minutes of conversation, idempotent, safe to re-run later to update the profile. For the VM install itself, use install-openclaw-to-yc. For ongoing bot consulting, use openclaw-guide.
Organizer-side companion to install-openclaw-to-yc. Provisions N isolated Yandex Cloud Kazakhstan folders for workshop participants who do NOT have their own YC account — one folder per participant, each with a dedicated service account, minimum-privilege role bindings, default VPC network, and a JSON authorization-key bundle. The bundle file is what the organizer sends privately on Telegram to each participant; that participant then feeds it into install-openclaw-to-yc as "Plan B" (workshop-key mode) and the wizard uses it as a drop-in replacement for personal OAuth. Use when the user says prepare YC workshop, provision workshop folders, generate workshop keys, organizer setup for OpenClaw workshop, раздать ключи к Яндекс Облаку участникам, подготовить Yandex Cloud к воркшопу, or any close paraphrase. Runs end-to-end in ~3 minutes for 25 participants. Includes the matching cleanup that deletes everything after the workshop. For participant-side install, use install-openclaw-to-yc instead.
Monthly self-deception audit — 25 anti-patterns from CEO Bible Section M
| name | daily-recap |
| description | End-of-day consolidation — summarize daily log, track belief changes and customer conversations, promote durable facts to MEMORY.md |
End-of-day consolidation. Triggered by heartbeat at 21:00-22:00 or manually ("recap the day").
Open memory/YYYY-MM-DD.md. If empty or no entries — ask: "Quiet day. Any customer conversations or belief changes to log before we close?" If still nothing → HEARTBEAT_OK.
From all entries of the day, compile:
## Daily Recap
**Customer conversations:** X today (Y this week, target 8-12/week)
- [who]: [key insight or outcome]
**Belief changes:** (what shifted in understanding)
- [was] -> [became] (evidence: [what showed it])
**Decisions:** (decisions made today)
- [decision]: [why] -> [what changes]
**Open threads:** (started but not finished)
- [topic]: [what remains to be done]
**Constraint check:** [current constraint] — today [exploit/subordinate/ignore]?
Count customer conversations from today's log entries. Update memory/heartbeat-state.json field weeklyConversations (increment). If it's Monday — reset to 0.
If weekly count < 4 by Wednesday or < 6 by Friday — add warning: "Below target. What's blocking customer contact?"
Read memory/focus-state.json:
daily_minimum.done == false at recap time and no waiver → note neutrally: "GTM не стартовал сегодня. Завтра снизим порог."For each belief change, ask:
If yes — update MEMORY.md. Keep MEMORY.md < 3KB.
Append the ## Daily Recap block to memory/YYYY-MM-DD.md.
Set "lastRecapDate": "YYYY-MM-DD" in memory/heartbeat-state.json.
Day recap:
GTM: [done ✓ / waived (reason) / missed ✗]
Streak: N дн | Waivers: N/week
Conversations: X today (Y/week, target 8-12)
[list if any]
Belief changes: Z
[list — most important]
Decisions: N
[list if any]
Constraint: [exploit/subordinate/ignore today]
If the day was empty AND GTM missed: "Тихий день. GTM не стартовал — завтра снизим порог. Что-нибудь запомнить перед закрытием?"
Follow output preferences from USER.md (language, format, platform constraints).