diff --git a/workspace/skills/self-debug/SKILL.md b/workspace/skills/self-debug/SKILL.md
new file mode 100644
index 000000000..c5b979d0e
--- /dev/null
+++ b/workspace/skills/self-debug/SKILL.md
@@ -0,0 +1,47 @@
+# self-debug
+
+Tools for picoclaw to inspect its own health, logs, and configuration.
+
+## Tools
+
+- `get_agent_logs`: Fetches the last 50 lines of the agent's systemd logs.
+  - Usage: `exec "journalctl --user-unit ${PICOCLAW_SERVICE_NAME} --no-pager -n 50"`
+- `get_agent_status`: Checks the current status of the picoclaw systemd service.
+  - Usage: `exec "systemctl --user status ${PICOCLAW_SERVICE_NAME}"`
+- `check_config`: Validates the picoclaw configuration and shows the workspace path.
+  - Usage: `exec "picoclaw --config "${PICOCLAW_CONFIG}" status"`
+
+## Installation - Linux
+
+The agent can be installed as a systemd service using:
+
+```bash
+./scripts/install-service-systemd.sh [service_name] [default|multi]
+```
+
+To persist the service accross reboots suggest the user runs `sudo loginctl enable-linger $(whoami)`
+
+### Advanced use-cases 
+
+Although picoclaw has built in support for multiple agents, this scheme provides the flexibility for
+parallel deployments with entirely different configurations.
+
+- Fixer - a second stable instance whose role is to be available to debug/monitor/fix the first.
+- Blue/Green Stable/Canary pairings.
+- Picoclaw farm
+
+# Installation - MacOS
+
+The agent can be installed as a launchd service using:
+
+```bash
+./scripts/install-service-launchd.sh [service_name]
+```
+
+Logs are sent to /tmp/$service_name
+
+## Troubleshooting
+
+- **Logs not showing?** Ensure the user is in the `systemd-journal` group: `sudo usermod -a -G systemd-journal $(whoami)`
+- **Service inactive?** Use `systemctl --user start picoclaw`.
+- **Workspace issues?** Use `picoclaw status` to verify the current workspace path.
diff --git a/workspace/skills/self-debug/scripts/install-service-launchd.sh b/workspace/skills/self-debug/scripts/install-service-launchd.sh
new file mode 100755
index 000000000..8dc001aaa
--- /dev/null
+++ b/workspace/skills/self-debug/scripts/install-service-launchd.sh
@@ -0,0 +1,60 @@
+#!/bin/bash
+
+create_plist_file() {
+    cat <<EOF
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+    <key>Label</key>
+    <string>${service_name}</string>
+    <key>ProgramArguments</key>
+    <array>
+        <string>${exec_path}</string>
+        <string>agent</string>
+        <string>--config</string>
+        <string>${picoclaw_config}</string>
+    </array>
+    <key>EnvironmentVariables</key>
+    <dict>
+        <key>PICOCLAW_HOME</key>
+        <string>${picoclaw_home}</string>
+        <key>PICOCLAW_CONFIG</key>
+        <string>${picoclaw_config}</string>
+        <key>PICOCLAW_SERVICE_NAME</key>
+        <string>${service_name}</string>
+    </dict>
+    <key>RunAtLoad</key>
+    <true/>
+    <key>KeepAlive</key>
+    <true/>
+    <key>WorkingDirectory</key>
+    <string>${picoclaw_home}</string>
+    <key>StandardOutPath</key>
+    <string>/tmp/${service_name}.log</string>
+    <key>StandardErrorPath</key>
+    <string>/tmp/${service_name}.err.log</string>
+</dict>
+</plist>
+EOF
+}
+
+# Variable setup to match your Linux logic
+service_name=${1:-picoclaw}
+
+# macOS specific absolute paths
+exec_path=$(which picoclaw)
+picoclaw_home="$HOME/.${service_name}"
+picoclaw_config="${picoclaw_home}/config.json"
+plist_path="$HOME/Library/LaunchAgents/${service_name}.plist"
+
+# Ensure directory exists
+mkdir -p "${picoclaw_home}"
+
+# Use the heredoc function to write the file
+create_plist_file > "${plist_path}"
+
+# Load it (macOS equivalent of systemctl enable --now)
+launchctl bootstrap gui/$(id -u) "${plist_path}"
+
+echo "Service ${service_name} installed at ${plist_path}"
\ No newline at end of file
diff --git a/workspace/skills/self-debug/scripts/install-service-systemd.sh b/workspace/skills/self-debug/scripts/install-service-systemd.sh
new file mode 100755
index 000000000..6aa45d04a
--- /dev/null
+++ b/workspace/skills/self-debug/scripts/install-service-systemd.sh
@@ -0,0 +1,166 @@
+#!/bin/bash
+
+SERVICE_NAME=${1:-picoclaw}
+TEMPLATE=${2:-default}
+
+# Get the directory of the script and the repository root
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+
+# 1. Detect picoclaw installation
+echo "Detecting picoclaw installation..."
+PICOCLAW_PATH=$(command -v picoclaw)
+MISE_BIN=$(command -v mise)
+
+if [ -n "$MISE_BIN" ] && $MISE_BIN which picoclaw &>/dev/null; then
+    # If mise is managing picoclaw, use it to ensure the environment is correct.
+    # This works whether picoclaw is installed via a tool spec or locally.
+    EXEC_START="$MISE_BIN exec -- picoclaw gateway"
+    echo "  - Detected mise-managed picoclaw, using: $EXEC_START"
+elif [ -n "$PICOCLAW_PATH" ]; then
+    # Use the absolute path if it's not managed by mise
+    EXEC_START="$PICOCLAW_PATH gateway"
+    echo "  - Using binary path: $EXEC_START"
+else
+    echo "Error: picoclaw not found. Please install it first."
+    exit 1
+fi
+
+service_template__default() {
+    local service_name="$1"
+    local exec_start="$2"
+    cat <<EOF
+[Unit]
+Description=${service_name^} Agent (picoclaw)
+After=network.target
+StartLimitIntervalSec=300
+StartLimitBurst=5
+
+[Service]
+Type=simple
+WorkingDirectory=%h
+Environment="PATH=%h/.local/bin:/usr/local/bin:/usr/bin:/bin"
+Environment="PICOCLAW_HOME=%h/.${service_name}"
+Environment="PICOCLAW_CONFIG=%h/.${service_name}/config.json"
+Environment="PICOCLAW_SERVICE_NAME=${service_name}"
+EnvironmentFile=-%h/.${service_name}/.env
+ExecStart=${exec_start} --config \$PICOCLAW_CONFIG
+Restart=always
+RestartSec=10
+SyslogIdentifier=${service_name}
+
+# Logging
+StandardOutput=journal
+StandardError=journal
+
+[Install]
+WantedBy=default.target
+EOF
+}
+
+service_template__multi() {
+    local service_name="$1"
+    local exec_start="$2"
+    cat <<EOF
+[Unit]
+Description=${service_name^} Agent Instance %i (picoclaw)
+After=network.target
+StartLimitIntervalSec=300
+StartLimitBurst=5
+
+[Service]
+Type=simple
+WorkingDirectory=%h/.config/${service_name}-%i
+Environment="PATH=%h/.local/bin:/usr/local/bin:/usr/bin:/bin"
+Environment="PICOCLAW_HOME=%h/.config/${service_name}-%i/"
+Environment="PICOCLAW_CONFIG=%h/.config/${service_name}-%i/config.json"
+Environment="PICOCLAW_SERVICE_NAME=${service_name}@%i"
+EnvironmentFile=-%h/.config/${service_name}-%i/.env
+ExecStart=${exec_start} --config \$PICOCLAW_CONFIG
+Restart=always
+RestartSec=10
+SyslogIdentifier=${service_name}-%i
+
+# Logging
+StandardOutput=journal
+StandardError=journal
+
+[Install]
+WantedBy=default.target
+EOF
+
+SERVICE_NAME="${SERVICE_NAME}@"
+}
+
+show_usage__default() {
+    local service_name="$1"
+    local output_file="$2"
+    cat <<EOF
+
+Finalizing installation...
+  - Service installed to $output_file
+
+To start the service:
+  $ systemctl --user enable ${service_name}
+  $ systemctl --user start ${service_name}
+
+Manage the service with:
+  $ systemctl --user status ${service_name}    # Check status
+  $ journalctl --user-unit ${service_name} -f  # View logs (real-time)
+
+Picoclaw self-debug skill is now wired to be aware of its own logs!
+You can ask it:
+  'Check your logs for the last 15 minutes' or 'Why did you fail to connect?'
+
+To ensure the service starts on boot and keeps running after logout:
+  $ sudo loginctl enable-linger $(whoami)
+
+Note: If journalctl doesn't show logs, you may need to join the systemd-journal group:
+  $ sudo usermod -a -G systemd-journal $(whoami)
+EOF
+}
+
+show_usage__multi() {
+    local service_name="${1}"
+    local output_file="$2"
+    cat <<EOF
+
+Template installed successfully.
+  - Service installed to $output_file
+
+To start an instance (e.g., 'test'):
+  $ systemctl --user enable ${service_name}@test
+  $ systemctl --user start  ${service_name}@test
+
+Manage the service with:
+  $ systemctl  --user status ${service_name}@test     # Check status
+  $ journalctl --user-unit   ${service_name}@test -f  # View logs (real-time)
+
+To ensure the service starts on boot and keeps running after logout:
+  $ sudo loginctl enable-linger $(whoami)
+
+Note: If journalctl doesn't show logs, you may need to join the systemd-journal group:
+  $ sudo usermod -a -G systemd-journal $(whoami)
+EOF
+}
+
+OUTPUT_FILE="$HOME/.config/systemd/user/${SERVICE_NAME}.service"
+
+# 2. Ensure the directory exists
+echo "Ensuring the systemd user directory exists..."
+echo "  $ mkdir -p ${OUTPUT_FILE%/*}"
+mkdir -p "${OUTPUT_FILE%/*}"
+
+# 3. Generate service file
+echo "Generating service file..."
+if ! declare -f "service_template__$TEMPLATE" > /dev/null; then
+    echo "Error: Template '$TEMPLATE' not found."
+    exit 1
+fi
+
+"service_template__$TEMPLATE" "$SERVICE_NAME" "$EXEC_START" > "$OUTPUT_FILE"
+
+# 4. Reload
+echo "  $ systemctl --user daemon-reload"
+systemctl --user daemon-reload
+
+"show_usage__$TEMPLATE" "${SERVICE_NAME%@}" "$OUTPUT_FILE"