TOOLS.md - Local Notes

Skills define how tools work. This file is for your specifics — the stuff that's unique to your setup.

Vultr Snapshots

Automated Weekly Backups

• Tool: tools/vultr-snapshot.sh
• Schedule: Sundays 10:00 PM PT (after rebuild + hygiene)
• Rotation: Keep 4 most recent, auto-delete oldest
• Credentials: /home/node/.openclaw/credentials/vultr-api.json
• Instance ID: bc5f56e5-a60e-4f3e-a40b-74eccae58f28
• Setup date: Feb 13, 2026

Cost: ~$6/month (4 snapshots × ~30GB × $0.05/GB/month)

Manual run:

./tools/vultr-snapshot.sh

IP Allowlist: If API returns "Unauthorized IP", add 144.202.121.97 to Vultr API key allowlist at https://my.vultr.com/settings/#settingsapi

---

Package Tracking

UPS

• Tool: tools/ups-track.py <tracking_number>
• API Account: 15BR09 (Quan's business account)
• Credentials: /home/node/.openclaw/credentials/ups-api.json
• Token cache: /home/node/.openclaw/credentials/ups-token.json (auto-refreshed)
• Setup date: Feb 13, 2026

Usage:

./tools/ups-track.py 1Z999AA10123456784
./tools/ups-track.py 1Z999AA10123456784 --json  # Include raw JSON

Returns: Status, location, timestamp, delivery confirmation, activity count.

Multi-Carrier (Future)

• Consider AfterShip if we need FedEx, USPS, DHL combined tracking
• UPS covers most business shipments for now

---

Quo (Business SMS/Phone)

⚠️ CRITICAL BOUNDARY: Only (385) 485-5863 maps to Quan's personal phone.

NEVER use these numbers:

• (562) 451-8061 - Quan direct
• (626) 828-8000 - ZTAG Main Line
• (661) 386-4777 - ZTAG INC
• (986) 886-4673 - Tin

Tools:

• API credentials: /home/node/.openclaw/credentials/quo-api.json
• Messaging script: tools/quo-messaging.py
• Webhook handler: tools/quo-webhook-handler-v2.py (port 18791)
• Systemd service: quo-webhook.service (host-managed)

Status: ✅ Operational (fixed Feb 15, 2026)

• Webhook URL: https://sms-7f2a1b.relay9kq.us/
• SMS → Telegram: Working
• Telegram → SMS: Manual via quo-messaging.py

---

Tailscale + Markdown Server

Setup: VPS connected to Tailscale network as minnie-core

Tailscale Access:

• VPS IP: 100.72.11.53
• Hostname: minnie-core (if MagicDNS enabled)
• Setup date: Feb 16, 2026

Markdown Server:

• Access: http://100.72.11.53:9876 or http://minnie-core:9876
• Purpose: Browse workspace markdown files rendered as HTML in browser
• Server script: tools/markdown-server.js
• Systemd service: markdown-server.service (container-managed)
• Port: 9876 (exposed from container)

Usage:

• Open http://100.72.11.53:9876 on any Tailscale-connected device (phone, laptop)
• Browse folders, click .md files to view rendered
• Example URLs:
  • /MEMORY.md - Long-term memory
  • /analysis/ - Analysis documents
  • /working/ops/ - Operational tasks

Troubleshooting:

• Can't connect? Check Tailscale app is connected (green icon)
• Restart server: systemctl restart markdown-server (on host)
• Check status: systemctl status markdown-server
• View logs: journalctl -u markdown-server -f

Pattern: Container port exposure (same as Quo webhook on 18791)

---

PDF Generation & Chinese Font Rendering

Tool: tools/markdown-to-pdf.js - Convert markdown to PDF using puppeteer

Usage:

node tools/markdown-to-pdf.js <input.md> [output.pdf]

Chinese Font Support (STANDARD PATTERN):

• Google Fonts CDN: Markdown server loads Noto Sans SC automatically
• Font Family: "Noto Sans SC" listed first in CSS font stack
• Rendering: Chinese characters display properly in both browser and PDF
• PDF Size: ~2.5 MB (with fonts) vs ~500 KB (English only)
• Setup date: Feb 16, 2026

When generating multi-language PDFs:

1. Ensure markdown server is running (port 9876)
2. Chinese fonts load automatically from Google Fonts CDN
3. PDF generation embeds fonts for offline viewing
4. Test on actual device before delivering

Example:

# English PDF
node tools/markdown-to-pdf.js MASTER_PLAN.md MASTER_PLAN.pdf

# Chinese PDF (fonts automatically embedded)
node tools/markdown-to-pdf.js MASTER_PLAN_中文.md MASTER_PLAN_中文.pdf

Download via Tailscale:

• English: http://100.72.11.53:9876/MASTER_PLAN.pdf
• Chinese: http://100.72.11.53:9876/MASTER_PLAN_中文.pdf

---

Google Calendar Integration

Tool: tools/google-calendar-list.py - List events from ALL calendars

Usage:

python3 tools/google-calendar-list.py --days 1 [--timezone America/Los_Angeles]

Multi-Calendar Support (CRITICAL):

• Queries ALL calendars (not just primary)
• Includes: Quan ZTAG, quan@gantom.com, Team Calendar, Holidays, etc.
• Each event shows source calendar: [Quan ZTAG], [Team Calendar], etc.

Timezone Handling:

• Default: America/Los_Angeles (PT)
• Critical: Always use PT timezone for calculating "tomorrow"
• UTC calculations show wrong day (timezone bug fixed Feb 16, 2026)

OAuth Credentials:

• Tokens: /home/node/.openclaw/credentials/google-calendar-tokens.json
• Client Secret: /home/node/.openclaw/credentials/google-calendar-client-secret.json
• Auto-refreshes tokens when expired

Used By:

• Evening schedule briefing (10 PM PT daily)
• Early morning event warning (6 PM PT daily)

Example Output:

all-day - Presidents' Day [Holidays in United States]
10:00 AM - 🎯 Minnie: Telegram Topics Setup [quan@gantom.com]
1:00 PM - 🎯 Minnie: Daily Markdown Maintenance Setup [quan@gantom.com]
6:00 PM - Geo Yoyo class [Quan ZTAG]

Debugging:

# Test tomorrow's events
python3 tools/google-calendar-list.py --days 1

# JSON output for debugging
python3 tools/google-calendar-list.py --days 1 --json

---

What Goes Here

Things like:

• Camera names and locations
• SSH hosts and aliases
• Preferred voices for TTS
• Speaker/room names
• Device nicknames
• Package tracking accounts
• Anything environment-specific

Why Separate?

Skills are shared. Your setup is yours. Keeping them apart means you can update skills without losing your notes, and share skills without leaking your infrastructure.

---

Add whatever helps you do your job. This is your cheat sheet.