System Restoration

Restore Advantage HPE operational intelligence systems. Use when systems are down, missing alerts, broken scheduling, or data source issues. Covers LaunchD s...

Security Scan

The skill's purpose (restore local operational services) is plausible, but its instructions reference user-specific paths and sensitive local credentials (Slack bot token) without declaring them, and it instructs system-level changes — this mismatch and required sensitive access are concerning.

Purpose & Capability

The skill claims to restore local Advantage HPE operational systems and includes steps to load LaunchD plists, run scripts, and create cron jobs — these actions are consistent with the stated purpose. However, the skill is hard-coded to a single user's home paths (/Users/stephendobbins/...) and assumes access to local integration credentials. The metadata declares no required env vars or config paths even though the instructions explicitly reference local files and tokens, which is an inconsistency.

Instruction Scope

SKILL.md instructs the agent to read and edit files under /Users/stephendobbins (scripts, .openclaw workspace, LaunchAgents), to copy backups, to create/load LaunchD plist files, and to check a local integrations.json that contains a Slack bot token. Those actions are within a restoration workflow but they also involve access to sensitive credentials and making persistent system changes. The instructions do not limit or gate access to those secrets or require explicit consent, and they reference paths that are not declared in the skill metadata.

Install Mechanism

There is no install spec (instruction-only skill), and included Python scripts appear to be local helpers (one writes a plist file, the other provides mock browser data functions). No external downloads or obscure install URLs are used. This is the lower-risk install pattern, but the presence of code files that manipulate system services increases the surface area compared to a pure-text guide.

Credentials

The skill does not declare any required environment variables or config paths, yet SKILL.md and references explicitly point to a local integrations.json (/Users/stephendobbins/.config/ranger/integrations.json) that contains a Slack bot token (example shows xoxb-...). Requesting or reading that file would expose credentials unrelated to the skill metadata. The number and sensitivity of local resources the instructions require (Slack token, user-specific directories, LaunchAgents) are disproportionate to what was declared.

Persistence & Privilege

The skill instructs creation of LaunchD plists and loading them (scripts/create-live-nudges-service.py writes com.ranger.live-nudges.plist). Those actions modify per-user persistent scheduling and are coherent with system restoration duties, but they are privileged operations that should be performed only after explicit local approval. The skill itself is not marked always:true, and it does not request to auto-enable itself — but its instructions enable persistent agents on the host.

What to consider before installing

This skill appears to be a practical restoration playbook for a specific user (stephendobbins) and will instruct reading/writing files and creating LaunchD services on the host. Before installing or running it: 1) Verify you are the intended machine/user — the skill uses hard-coded /Users/stephendobbins paths; running it on another account could fail or access the wrong files. 2) Manually inspect the referenced integrations file (/Users/stephendobbins/.config/ranger/integrations.json) — it contains a Slack bot token; do not allow the skill to read or transmit that token unless you trust the code and environment. 3) Review the included scripts (create-live-nudges-service.py and browser_data_sources.py) to ensure they do only what you expect; consider running them in a sandbox or with safe dry-run flags. 4) Prefer making system changes (launchctl load/unload, creating plists, copying backups) manually or via an audited maintenance process rather than letting an automated skill do them without explicit operator approval. 5) Ask the author to remove hard-coded user paths, declare required config paths/credentials in metadata, and add explicit consent prompts before reading any credential files. If you lack confidence in those changes, classify this skill as untrusted for production use.

Comprehensive guide for restoring Advantage HPE's operational intelligence systems when they fail or go down.

Investigation Workflow

1. System Status Assessment

Before fixing anything, map out what's broken:

Core Intelligence Systems:

1. Zero Revenue Alerts → #margin-alerts (Every 30 min)
2. Morning Pulse → #manager-nudges (Daily 6:35 AM)
3. Live Nudges → #manager-nudges (Every 15 min)
4. Material Truth Report → #material-intel-systems (Daily 7:00 AM)
5. Friend-Zone Reformatter → #live-ops (ServiceTitan email alerts)

Investigation Commands:

# Check LaunchD services
launchctl list | grep ranger

# Check cron jobs  
cron list

# Check running processes
ps aux | grep -E "(keel|pulse|margin|nudge)" | grep -v grep

# Find system code
find /Users/stephendobbins/.config/ranger -name "*.py" | grep -E "(pulse|margin|nudge)"
find /Users/stephendobbins/.openclaw/workspace -name "*.py" | grep -E "(zero|revenue)"

2. Locate Code & Determine Failure Cause

Common Locations:

• /Users/stephendobbins/.config/ranger/scripts/ - Main operational scripts
• /Users/stephendobbins/.config/ranger/materials/ - Material intelligence
• /Users/stephendobbins/.openclaw/workspace/ - Recent scripts & fixes
• /Users/stephendobbins/Library/LaunchAgents/ - LaunchD service definitions

Common Failure Patterns:

• LaunchD services unloaded - Emergency shutdown or system restart
• Data source broken - ServiceTitan API returning wrong data
• Scheduling missing - Functions exist but no cron/LaunchD trigger
• Script errors - Import failures, credential issues

System-Specific Restoration

Zero Revenue Alerts

Script: /Users/stephendobbins/.config/ranger/scripts/margin_alerts.py Channel: #margin-alerts (C0A5L7MG60P) Schedule: Every 30 minutes

Restoration Steps:

1. Verify script exists and posts to Slack
2. Load LaunchD service: launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.margin-alerts.plist
3. Test manually: cd /Users/stephendobbins/.config/ranger/scripts && python3 margin_alerts.py
4. Check logs: tail /tmp/margin_alerts.log

Morning Pulse

Script: /Users/stephendobbins/.config/ranger/scripts/pulse_os_full.py Channel: #manager-nudges (C0A5V9JL2KV) Schedule: Daily 6:35 AM CT

Restoration Steps:

1. If broken API data: Check for .bak backup with working data sources
2. Restore backup: cp pulse_os_full.py.bak pulse_os_full.py
3. Fix data sources: Replace API calls with browser automation (see references/browser-data-sources.md)
4. Load LaunchD service: launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.morning-pulse.plist
5. Test: python3 pulse_os_full.py pulse

Live Nudges

Script: /Users/stephendobbins/.config/ranger/scripts/pulse_os_full.py nudges Channel: #manager-nudges Schedule: Every 15 minutes

Function: run_nudges() on line 548-617 Features: 🚗 dispatched / 📍 arrived / ✅ completed alerts

Restoration Steps:

1. Verify function exists: grep -n "def run_nudges" pulse_os_full.py
2. Create LaunchD service (see scripts/create-live-nudges-service.py)
3. Load service: launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.live-nudges.plist
4. Test: python3 pulse_os_full.py nudges

Material Truth Report

Script: /Users/stephendobbins/.config/ranger/materials/reconciliation_report.py Channel: #material-intel-systems (C0A5L7RB5EK)
Schedule: Daily 7:00 AM CT

Restoration Steps:

1. Test script: cd /Users/stephendobbins/.config/ranger/materials && python3 reconciliation_report.py --no-email
2. Create cron job with 7:00 AM schedule
3. Verify channel posting

Data Source Repair

ServiceTitan API vs UI Data

Problem: ServiceTitan API often returns test/historical data instead of real operational data.

Solution: Replace API calls with browser automation:

1. Create browser data source module (see scripts/browser_data_sources.py)
2. Import in main script: Replace parse functions with browser equivalents
3. Preserve output format - Same sections, different data source

Browser Data Functions:

• get_browser_low_margin_jobs()
• get_browser_stale_estimates()
• get_browser_revenue_leaks()
• get_browser_driver_incidents()

KEEL System Issues

Script: /Users/stephendobbins/.config/ranger/keel/keel_slack_bot.py

Safe restart for field tech DM only:

1. Disable operational intelligence: Set OPERATIONAL_INTELLIGENCE_ENABLED = False
2. Restart process: cd /Users/stephendobbins/.config/ranger/keel && python3 keel_slack_bot.py &
3. Verify running: ps aux | grep keel_slack_bot

Service Management Commands

LaunchD Services

# List services
launchctl list | grep ranger

# Load service  
launchctl load /Users/stephendobbins/Library/LaunchAgents/com.ranger.<service>.plist

# Unload service
launchctl unload /Users/stephendobbins/Library/LaunchAgents/com.ranger.<service>.plist

# Start service immediately
launchctl start com.ranger.<service>

# Check service logs
tail /tmp/<service>.log
tail /tmp/<service>.err

Cron Jobs (OpenClaw)

# List jobs
cron list

# Add job  
cron add <job-definition>

# Remove job
cron remove <job-id>

Emergency Shutdown Recovery

When systems are emergency-stopped due to bad data:

1. Investigate root cause - Usually ServiceTitan API data issues
2. Fix data sources - Switch to browser automation or correct API endpoints
3. Test manually - Verify data accuracy before re-enabling
4. Restore services - Load LaunchD services and cron jobs
5. Monitor initially - Check logs and channel posts for accuracy

Resources

scripts/

• create-live-nudges-service.py - Generate LaunchD plist for live nudges
• browser_data_sources.py - Browser automation replacement for broken APIs

references/

• launchd-service-templates.md - LaunchD plist templates for different schedules
• channel-ids.md - Slack channel IDs for all operational intelligence channels
• troubleshooting-checklist.md - Step-by-step debugging guide