macroclaw 0.20.0 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "macroclaw",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "Telegram-to-Claude-Code bridge",
   "license": "MIT",
   "type": "module",

package/workspace-template/.claude/skills/schedule/SKILL.md

@@ -1,10 +1,6 @@
 ---
 name: schedule
-description: >
-  Schedule events, reminders, and recurring tasks. Use when the user wants to:
-  set a reminder, schedule something for later, create a recurring task,
-  set up a periodic check, automate a prompt on a schedule, or plan a
-  one-time or repeating event at a specific time.
+description: "Schedule events, reminders, and recurring tasks. Use when the user wants to: set a reminder, schedule something for later, create a recurring task, set up a periodic check, automate a prompt on a schedule, or plan a one-time or repeating event at a specific time."
 ---
 
 Schedule a new event by adding it to `data/schedule.json`.
@@ -20,12 +16,13 @@ Schedule a new event by adding it to `data/schedule.json`.
 
 ## How to schedule
 
-1. Read `data/schedule.json` (create with `{"jobs": []}` if missing)
-2. Convert the user's request to a cron expression (see reference below)
-3. **Be proactive about timing**: if the user says "next week" or "tomorrow" without a specific time, pick the best time based on what you know (their routine, calendar, context)
-4. Append the new job to the `jobs` array
-5. Write the updated file
-6. Confirm: what was scheduled, when it will fire, and offer to adjust
+1. Run `date` to get the current date and time
+2. Read `data/schedule.json` (create with `{"jobs": []}` if missing)
+3. Convert the user's request to a cron expression (see reference below)
+4. **Be proactive about timing**: if the user says "next week" or "tomorrow" without a specific time, pick the best time based on what you know (their routine, calendar, context)
+5. Append the new job to the `jobs` array
+6. Write the updated file
+7. Confirm: what was scheduled, when it will fire, and offer to adjust
 
 ## Natural language → cron
 

package/workspace-template/.claude/skills/self-update/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: self-update
+description: "Update macroclaw to the latest version. Use when the user asks to update, upgrade, self-update, or update yourself. Handles the service restart safely by using a detached process and scheduled follow-up."
+---
+
+Update macroclaw to the latest version.
+
+## Steps
+
+1. **Check service status**: Run `macroclaw service status` and verify it shows `Installed: yes` and `Running: yes`. If not, tell the user the service isn't running and stop.
+
+2. **Generate LOG_FILE_PATH**: Run `echo "/tmp/macroclaw-update-$(date -u +%Y-%m-%dT%H-%M-%SZ).log"` and use the output as `<LOG_FILE_PATH>` in the following steps.
+
+3. **Schedule follow-up**: Using the `schedule` skill, create a one-shot event 1 minute from now:
+   - Name: `self-update-check`
+   - Prompt: `Check macroclaw update result. Read <LOG_FILE_PATH> — if it contains "Updated macroclaw", report the version change. If it contains "already up to date", say so. If the file doesn't exist or is empty, the update may still be in progress — schedule another check in 1 minute.`
+   - Model: `haiku`
+   - Recurring: `false`
+
+4. **Run the update**: Execute the update script bundled with this skill:
+   ```
+   bash ${CLAUDE_SKILL_DIR}/scripts/update.sh <LOG_FILE_PATH>
+   ```
+
+## Important
+
+- The `macroclaw service update` command stops the service, installs the latest version, and starts it again. Stopping the service kills all processes in the cgroup — including this Claude Code session.
+- Do NOT use a background agent — it gets killed along with the main process.
+- Always run step 4 LAST — everything after it may not execute.

package/workspace-template/.claude/skills/self-update/scripts/update.sh

@@ -0,0 +1,39 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+if [[ $# -ne 1 ]]; then
+  echo "Usage: $0 <log-file>" >&2
+  exit 1
+fi
+
+LOG_FILE="$1"
+
+case "$(uname -s)" in
+  Linux)
+    sudo systemd-run \
+      --unit="macroclaw-update-$(date -u +%Y%m%dT%H%M%SZ)" \
+      --collect \
+      --no-block \
+      --property="User=$(id -un)" \
+      --property="Group=$(id -gn)" \
+      --setenv="HOME=$HOME" \
+      --setenv="PATH=$PATH" \
+      /bin/bash -lc "exec macroclaw service update > \"$LOG_FILE\" 2>&1"
+
+    # --collect: automatically remove the transient unit after it finishes.
+    # --no-block: return immediately instead of waiting for the started job.
+    ;;
+  Darwin)
+    nohup setsid /bin/bash -lc "exec macroclaw service update > \"$LOG_FILE\" 2>&1" >/dev/null 2>&1 &
+
+    # Best-effort only:
+    # macOS launchd has no simple systemd-run equivalent for transient jobs.
+    # nohup + setsid detaches the updater from the current process/session so it
+    # has a better chance of surviving when the main launchd service stops.
+    # A separate launchd job would still be the more robust long-term solution.
+    ;;
+  *)
+    echo "Unsupported platform: $(uname -s)" >&2
+    exit 1
+    ;;
+esac

package/workspace-template/CLAUDE.md

@@ -72,6 +72,8 @@ Skills live in `.claude/skills/`.
 
 When creating new skills, always put them in `.claude/skills/` within this workspace.
 
+**Before using a skill**, check `TOOLS.md` for operational notes — custom instructions, overrides, workarounds, and tips that supplement the skill's own SKILL.md. Update `TOOLS.md` when you discover new issues or tricks.
+
 ## Workspace Structure — Keep It Clean!
 
 **Root is sacred.** Only these belong in workspace root:

package/workspace-template/TOOLS.md

@@ -0,0 +1,7 @@
+# Skills — Operational Notes
+
+Supplements each skill's own SKILL.md with custom instructions, workarounds, and learned tips. Don't duplicate what's in SKILL.md — only add what it doesn't cover.
+
+Update this file when you discover new issues or tricks.
+
+---