Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Performs Neill-authorized emergency repair on Billy system authentication by clearing tokens, restarting gateway, backing up config, and verifying success.
Performs Neill-authorized emergency repair on Billy system authentication by clearing tokens, restarting gateway, backing up config, and verifying success.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Neill explicitly requests Billy system repair Neill reports Billy authentication/gateway issues Neill says "fix Billy" or "Billy is down" Billy system appears unresponsive to Neill
Billy is working fine Issue is not authentication-related Anyone other than Neill requests the repair Routine maintenance (not emergency)
β οΈ NEILL-ONLY COMMAND β οΈ Only Neill can authorize emergency repairs to Billy. Never run without explicit Neill authorization.
# Switch to Opus for enhanced diagnostics export OPENCLAW_MODEL_OVERRIDE="anthropic/claude-opus-4-6" # Run authorized repair bash ~/.openclaw/workspace/scripts/emergency-repair/fix-billy-auth.sh --authorized-by Neill
# Set up SSH keys first time bash ~/.openclaw/workspace/scripts/emergency-repair/setup-billy-repair-keys.sh
Verifies Neill's authorization (security check) SSH into Billy (EC2 via Tailscale) Backs up Billy's config (safety first) Clears stale authentication tokens (removes .token, device*.json) Removes hardcoded tokens (prevents repeat issues) Restarts Billy's gateway (fresh start) Verifies repair success (tests authentication) Logs everything (full audit trail) Reports back to Neill (success/failure)
Neill: "SAPCONET, Billy is showing authentication errors again, please fix him" SAPCONET Response: π¨ Emergency repair authorized by Neill π§ Switching to Opus model for enhanced diagnostics π Connecting to Billy via SSH... π Backing up Billy's configuration... π§Ή Clearing stale authentication tokens... β οΈ Found hardcoded token - removing... π Restarting Billy's gateway... β³ Waiting for startup... π§ͺ Testing authentication... β SUCCESS: Billy's authentication restored! π Repair completed in 45 seconds
Check Billy is online Verify Tailscale connectivity Confirm SSH key is installed on Billy
Manual intervention required Provide Neill with full error logs Escalate with specific diagnostic info
Gateway responds but status unclear Recommend Neill verify manually Provide repair log for analysis
Neill-only authorization - Script rejects unauthorized use SSH key authentication - Secure connection to Billy Full audit logging - Every action is recorded Config backups - Original settings preserved Non-destructive - Only removes auth tokens
SSH key must be installed on Billy (one-time setup) Tailscale connectivity between SAPCONET and Billy Billy must be online and accessible
/home/neill/.openclaw/workspace/output/billy-repair-YYYYMMDD-HHMM.log ~/.openclaw/openclaw.json.pre-repair-YYYYMMDD-HHMM (backup on Billy)
# Test SSH connection ssh -i ~/.ssh/billy-repair-key ubuntu@100.90.73.34 'echo "Connection works"' # Dry run (check authorization) bash ~/.openclaw/workspace/scripts/emergency-repair/fix-billy-auth.sh # Should show: "UNAUTHORIZED: This repair requires Neill's explicit authorization"
If repair consistently fails: Check Billy's system logs Verify OpenClaw installation integrity Consider full OpenClaw reinstall Check for deeper system issues (disk space, permissions, etc.) Remember: This is for authentication emergencies only. Use Opus model for complex diagnostics.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.