Menu
Set up LifeOS — connect API, configure cron jobs for proactive check-ins
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
Read or write the user's Google Calendar via the LifeOS broker endpoint. Use any time the user asks to read events, check schedule, add/move/cancel a calendar event, prepare for a meeting, or anything that touches Google Calendar. NEVER read or write any local google-token.json — auth is centralised in LifeOS.
Run a weekly review with the user as a single voice-note conversation on Telegram (or chat). Use when: user says /weekly-review, 'do my weekly review', 'let's review the week', 'sunday review', or it's late Sunday and they haven't reviewed yet. Pulls the prior week's priorities, wins, and goal context, asks for one voice note covering reflection + next-week priorities, parses the transcript, and writes the review to LifeOS.
Bump the OpenClaw version used by LifeOS pods. Use when the user says "bump openclaw", "update openclaw", "upgrade openclaw", "new openclaw version", or wants to update the OpenClaw Docker image used by LifeOS deployments.
Personal life operating system — manage tasks, goals, day plans, journal, finances, and more via CLI
Set up LifeOS — your personal life operating system. Use when: user says /lifeos-init, 'set up lifeos', 'initialize lifeos', or is using LifeOS for the first time. Walks through configuration, learns about goals and routines, and creates a personalized productivity system. NOT for: users who already have goals and tasks set up.
Check for LifeOS CLI updates, display changelog, obtain user confirmation, and execute the update. Use when: user says "update", "upgrade", "check for updates", "is there a new version?", "update lifeos", "update cli", or wants to update the LifeOS CLI to the latest version. Also triggers proactively when ~/.claude/cache/lifeos-update-check.json indicates an update is available (written by the SessionStart hook).
| name | lifeos-setup |
| description | Set up LifeOS — connect API, configure cron jobs for proactive check-ins |
| required_binaries | ["lifeos","openclaw"] |
Walk the user through LifeOS setup step by step.
Ask the user:
For self-hosted, guide them:
git clone https://github.com/<org>/lifeos && cd lifeos
cp .env.example .env
# Edit .env: set DB_PASSWORD and LIFEOS_SECRET to random values
docker compose up -d
# Visit http://localhost:3000 to set up account and create API key
# Install the CLI
npm install -g lifeos-cli
# Configure connection
lifeos config set-url <api-url> # e.g., https://app.lifeos.dev or http://localhost:3001
lifeos config set-key <api-key> # The API key from the dashboard
# Verify
lifeos whoami
Ask the user for their timezone (e.g., "America/New_York", "Europe/Berlin", "Asia/Tokyo").
Configure OpenClaw cron for proactive LifeOS features. Ask the user which ones they want, then set them up:
openclaw cron add --name "lifeos-morning" \
--cron "0 7 * * *" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger morning-briefing --json
Parse the JSON result and share a concise morning briefing with me:
- Any overdue tasks that need attention
- Today's scheduled tasks
- Today's MIT/P1/P2 if a day plan exists
- Any goals that are at risk" \
--announce
openclaw cron add --name "lifeos-daily-review" \
--cron "0 21 * * *" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger daily-review --json
Parse the result and walk me through an end-of-day review:
- Did I complete my MIT? P1? P2?
- What did I accomplish today?
- Any wins to celebrate?
- Help me write a quick journal entry using: lifeos journal write" \
--announce
openclaw cron add --name "lifeos-weekly-review" \
--cron "0 10 * * 0" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger weekly-review --json
Parse the result and help me with my weekly review:
- Summarize what I accomplished this week
- How did my goals progress?
- What were my wins?
- Help me plan next week using: lifeos week create" \
--announce
openclaw cron add --name "lifeos-overdue-triage" \
--cron "0 12 * * 1-5" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger overdue-triage --json
Check if I have overdue tasks. If yes, help me decide for each one:
- Reschedule it (lifeos task update <id> --due <new-date>)
- Drop it (lifeos task update <id> --status dropped)
- Complete it now
If no overdue tasks, just say 'All clear!' briefly." \
--announce
openclaw cron add --name "lifeos-reminders" \
--cron "*/15 * * * *" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger reminder-check --json
If there are due reminders, tell me about each one concisely.
If there are no due reminders, produce no output at all." \
--announce --best-effort
openclaw cron add --name "lifeos-goal-health" \
--cron "0 9 * * 1" --tz "<USER_TZ>" \
--prompt "Run: lifeos trigger goal-health --json
Review my goal health scores. Only mention goals that are at_risk or off_track.
For each, suggest concrete next actions I could take this week." \
--announce
# Check CLI connection
lifeos whoami
# Check cron jobs
openclaw cron list
# Test a trigger
lifeos trigger morning-briefing
# Create a test task
lifeos task create "Test LifeOS setup" --due today
lifeos task list --due today
lifeos task complete <id>
lifeos undo
Tell the user: "LifeOS is ready! Your cron jobs will start running on schedule. You can manage everything via the lifeos CLI or the web dashboard."