@robbiesrobotics/alice-agents 1.5.11 → 1.5.13

package/templates/workspaces/olivia/skills/travel-planning/packing-templates.md

@@ -1,155 +0,0 @@
-# Packing Templates — Travel Planning
-
-## Base Template (7-day trip)
-
-### Documents (CARRY-ON ONLY)
-- [ ] Passport (check 6-month validity)
-- [ ] Visa / travel authorization
-- [ ] Travel insurance card
-- [ ] Flight confirmations
-- [ ] Hotel confirmations
-- [ ] Driver's license (if renting)
-- [ ] Credit cards (notify bank)
-- [ ] Local currency (20% of budget)
-- [ ] Photo copies of all documents (separate from originals)
-
-### Electronics
-- [ ] Phone + charger
-- [ ] Power adapter (research plug type)
-- [ ] Portable battery
-- [ ] Headphones
-- [ ] Camera + charger (if applicable)
-- [ ] Kindle / tablet (optional)
-
-### Clothing (adjust for climate)
-- [ ] Underwear (days + 2)
-- [ ] Socks (days + 1)
-- [ ] T-shirts/tops (days ÷ 2 if laundry)
-- [ ] Pants/shorts (2-3)
-- [ ] Layering piece (sweater/hoodie)
-- [ ] Rain jacket or windbreaker
-- [ ] Sleepwear
-- [ ] Swimsuit (if applicable)
-- [ ] Walking shoes (broken in!)
-- [ ] Sandals/flip-flops
-- [ ] Dress shoes (if needed)
-- [ ] Belt
-
-### Toiletries
-- [ ] Toothbrush + toothpaste
-- [ ] Deodorant
-- [ ] Shampoo/conditioner (travel size)
-- [ ] Skincare basics
-- [ ] Sunscreen
-- [ ] Medications (1.5x supply + prescriptions)
-- [ ] First aid basics (bandaids, pain reliever)
-- [ ] Glasses/contacts + solution
-
-### Bags
-- [ ] Carry-on (fits overhead)
-- [ ] Personal item (under seat)
-- [ ] Day bag / backpack
-- [ ] Packing cubes (highly recommended)
-
----
-
-## Climate Variations
-
-### Hot / Beach
-Add:
-- [ ] Extra swimsuits (2-3)
-- [ ] Cover-up / sarong
-- [ ] Sun hat
-- [ ] Reef-safe sunscreen
-- [ ] After-sun lotion
-- [ ] Lightweight breathable fabrics
-
-Remove:
-- Heavy layers
-- Bulky shoes
-
-### Cold / Winter
-Add:
-- [ ] Thermal base layers
-- [ ] Warm coat / down jacket
-- [ ] Warm hat + gloves
-- [ ] Scarf / neck gaiter
-- [ ] Warm socks (wool/synthetic)
-- [ ] Waterproof boots
-- [ ] Hand warmers (optional)
-
-### Rainy Season
-Add:
-- [ ] Packable rain jacket
-- [ ] Waterproof bag cover
-- [ ] Quick-dry clothing
-- [ ] Extra plastic bags for wet items
-- [ ] Waterproof phone case
-
----
-
-## Activity-Specific Additions
-
-### Hiking / Outdoors
-- [ ] Hiking boots (broken in!)
-- [ ] Hiking socks
-- [ ] Trekking poles (if serious hikes)
-- [ ] Daypack with hydration
-- [ ] Trail snacks
-- [ ] Bug spray
-- [ ] Blister kit
-
-### Business Trip
-- [ ] Suit / business attire
-- [ ] Dress shoes (comfortable for walking)
-- [ ] Laptop + charger
-- [ ] Business cards
-- [ ] Presentation materials
-- [ ] Steamer or wrinkle spray
-
-### Photography Trip
-- [ ] Camera body + lenses
-- [ ] Extra batteries
-- [ ] Memory cards (more than you think)
-- [ ] Lens cleaning kit
-- [ ] Tripod (travel size)
-- [ ] Waterproof camera bag
-
-### Family / Kids
-- [ ] Entertainment for transport
-- [ ] Snacks (lots)
-- [ ] Comfort items
-- [ ] Basic first aid + fever reducer
-- [ ] Copies of kids' documents
-- [ ] Car seat (if needed)
-
----
-
-## Packing Tips
-
-### Carry-On Must-Haves (in case luggage is lost)
-- All documents
-- Medications (full supply)
-- One change of clothes
-- Electronics
-- Valuables
-- Toiletry basics
-
-### Weight Distribution
-- Heavy items bottom of bag, close to wheels
-- Fragile items center, cushioned
-- Frequently needed items top/outside pockets
-
-### Space Savers
-- Roll clothes (less wrinkles too)
-- Packing cubes (game changer)
-- Wear bulkiest items on plane
-- Multi-use items (sarong = beach cover + scarf + blanket)
-
-### Before Departure Checklist
-- [ ] Passport validity: 6+ months?
-- [ ] Visa: required and obtained?
-- [ ] Bank notified?
-- [ ] Phone plan / roaming sorted?
-- [ ] Home secured (lights, mail, plants)?
-- [ ] Emergency contacts shared itinerary?

package/templates/workspaces/olivia/skills/travel-planning/setup.md

@@ -1,66 +0,0 @@
-# Setup — Travel Planning
-
-Read this when `~/travel-planning/` doesn't exist or is empty. Use these guidelines to onboard the user naturally.
-
-## Your Attitude
-
-You're helping someone who's excited about travel. Whether they're planning their first international trip or their fiftieth, meet their energy. Travel planning should feel exciting, not overwhelming.
-
-**Communication style:** Focus on travel content rather than technical details. If the user asks where data is stored, explain openly: "Everything is saved in ~/travel-planning/ as markdown files you can read anytime."
-
-## Priority Order
-
-### 1. First: Integration (within first 2-3 exchanges)
-
-Figure out when this skill should activate in the future:
-- "Should I jump in whenever you mention a destination or trip idea?"
-- "Want me to help proactively — like reminding you about booking windows — or only when you ask?"
-- "Any upcoming trips I should start tracking?"
-
-Save their answer to their MAIN memory so other sessions know when to use this skill.
-
-### 2. Then: Understand Their Travel Style
-
-Ask open questions to understand their preferences:
-- "What kind of traveler are you? Do you love having every day planned, or prefer to wing it?"
-- "Do you have any dream destinations on your mind right now?"
-- "What's your typical trip length and budget range?"
-
-After each response:
-1. Reflect back what you understood
-2. Connect it to how you'll help them specifically
-3. Then ask the next question
-
-Example:
-> User: "I hate over-planning. I usually just book flights and figure out the rest there."
-> 
-> Good: "Got it — you like spontaneity. I'll focus on the essentials: flight timing, visa deadlines, and packing. I won't overwhelm you with hour-by-hour itineraries. Do you have any trips coming up, or destinations you've been dreaming about?"
-
-### 3. Finally: Capture Any Immediate Context
-
-If they mention upcoming trips or destinations:
-- Create wishlist entry or trip folder
-- Note any known dates, companions, purpose
-
-If they mention past trips:
-- Ask what worked and what didn't
-- These become preferences in memory
-
-## What You're Saving (internally)
-
-In `~/travel-planning/memory.md`:
-- Travel style: planner vs spontaneous, budget vs luxury, solo vs group
-- Accommodation preferences: hotels, Airbnb, hostels
-- Typical daily budget range
-- Any document info they share: passport expiry, frequent flyer programs
-- Past trip patterns that emerge
-
-Don't ask for all of this upfront. Learn it naturally over conversations.
-
-## When "Done"
-
-Once you know:
-1. When to activate (integration)
-2. Their general travel style
-
-...you're ready to help. Everything else builds over time through planning actual trips.

package/templates/workspaces/olivia/skills/update-it-all/SKILL.md

@@ -1,143 +0,0 @@
----
-name: update-it-all
-description: "Automates the full A.L.I.C.E. product update cycle after major releases. Auto-detects new/removed agents, generates changelog + release notes, waits for confirmation, then commits, tags, and publishes to npm. Use whenever agents are added/removed or a significant feature lands."
----
-
-# Update It All
-
-Automates the complete A.L.I.C.E. product update cycle — from auto-detection to npm publish — with zero manual changelog writing.
-
-## Philosophy
-
-The script **auto-detects what changed** by diffing git history and `agents.ts`, **generates the full changelog and release notes draft for you to review**, and only pushes when you confirm. You provide the judgment call; it handles the mechanical work.
-
-## Quick Start
-
-```bash
-# Interactive (recommended) — auto-detects, shows draft, waits for confirm
-bash ~/.openclaw/workspace-olivia/scripts/update-it-all.sh
-
-# Dry run — see what would be detected without changing anything
-bash ~/.openclaw/workspace-olivia/scripts/update-it-all.sh --dry-run
-
-# Non-interactive — auto-confirms (for CI)
-bash ~/.openclaw/workspace-olivia/scripts/update-it-all.sh --confirm
-```
-
-## What Gets Auto-Detected
-
-| What changed | How detected | Result |
-|---|---|---|
-| New agents | `git diff agents.ts` vs last tag | Added to changelog as `feat` |
-| Removed agents | Same diff | Added to changelog as `chore` |
-| Version bump type | Minor if new agents, else patch | Suggested automatically |
-| Landing page changes | Git diff of landing dir | `chore: landing page updated` |
-
-## How the Pipeline Works
-
-1. **Detect** — Diff `agents.ts` against the last git tag to find new/removed agents
-2. **Generate** — Auto-build the changelog entry + release notes draft
-3. **Review** — Shows you the draft and asks for version number + confirmation
-4. **Execute** — On confirm: commits, pushes, runs tests, tags, publishes npm
-5. **Verify** — Confirms the version is live on npm
-
-## What the Output Looks Like
-
-When you run the script, it shows you:
-
-```
-Current state:
-  Last git tag:       v1.5.1
-  Current version:     1.5.1
-  Suggested bump:      minor → v1.5.2
-  New agents:         aria, nate
-  Removed agents:     none
-  Total agents after:  31
-
-Draft changelog entry:
-
-  ## v1.5.2 — 2026-03-26
-  - **feat** Agent roster expanded — 2 new agent(s): aria, nate
-  - **chore** Landing page and documentation updated
-
-  New version [v1.5.2]:    ← you can override here
-  Proceed with v1.5.2? [y/N]  ← your call
-```
-
-## Version Bump Rules
-
-| Change | Bump type |
-|---|---|
-| New agent(s) added | **Minor** (`1.5.1` → `1.5.2`) |
-| Agent(s) removed | **Minor** (`1.5.1` → `1.5.2`) |
-| Internal fixes only | **Patch** (`1.5.1` → `1.5.1`) |
-
-You can always override the suggested version at the prompt.
-
-## What Gets Committed and Pushed
-
-### Landing page (`robbiesrobotics/alice-landing`)
-- `content/changelog.md` — new entry prepended
-- `lib/agents.ts` — new agent entries (if any)
-- `components/AgentGrid.tsx` — updated counts
-
-### alice-agents package (`robbiesrobotics/alice-agents`)
-- `package.json` — version bumped
-- `README.md` — agent table + counts updated
-- `landing/` — submodule updated to new landing commit
-- `releases/v{VERSION}.md` — release notes generated
-
-## What the Script Does NOT Touch
-
-These require manual attention after the script runs:
-- `ROSTER.md` — full agent entries (if new agents were added)
-- `HEARTBEAT.md` — agent count (auto-updated by script)
-- Landing page `vercel.json` or env vars
-- Any third-party integrations (Stripe, Supabase, etc.)
-
-## Git Credential Setup
-
-If `git push` fails with `could not read Username for 'https://github.com'`, the script auto-sets this:
-
-```bash
-git config --global credential.helper "$(which gh) auth git-credential"
-```
-
-The `gh` CLI is logged in as `robbiesrobotics-bot` and handles auth automatically.
-
-## Test Failures
-
-If `npm test` fails, the script pauses and asks:
-
-```
-Some tests failed. Continue anyway? [y/N]
-```
-
-Always fix tests before tagging. The most common cause is agent count assertions in `lib/agent-registry.mjs` that don't match the actual agent list.
-
-## Key File Locations
-
-| File | Path |
-|---|---|
-| Master script | `~/.openclaw/workspace-olivia/scripts/update-it-all.sh` |
-| Landing page | `~/.openclaw/workspace-olivia/alice-agents/landing/` |
-| Changelog (landing) | `landing/content/changelog.md` |
-| Agent grid lib | `landing/lib/agents.ts` |
-| alice-agents package | `~/.openclaw/workspace-olivia/alice-agents/` |
-| npm package.json | `alice-agents/package.json` |
-| Release notes | `alice-agents/releases/v{VERSION}.md` |
-| Workspace HEARTBEAT | `~/.openclaw/workspace-olivia/HEARTBEAT.md` |
-
-## When to Run This Skill
-
-Run `update-it-all` when:
-- A new agent was added to the roster
-- An agent was renamed or removed
-- A major feature lands in alice-agents or Mission Control
-- The landing page had significant content changes
-- After any `git commit` that touches `agents.ts`, `landing/`, or `README.md`
-
-Do NOT run this for:
-- Hotfixes that don't touch agents or landing page
-- Docs-only changes
-- Dependency bumps (use `npm version patch` instead)

package/templates/workspaces/olivia/skills/update-it-all/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "robbiesrobotics",
-  "slug": "update-it-all",
-  "version": "1.0.0",
-  "publishedAt": 1742997780
-}

package/templates/workspaces/olivia/skills/voice/SKILL.md

@@ -1,62 +0,0 @@
-# Voice Pipeline Skill
-
-Speech-to-text and text-to-speech using Whisper + Piper running on the **Jetson AGX Orin** node, callable from any OpenClaw agent session.
-
-## Architecture
-
-```
-[Input Audio] → MacBook Air → SCP to AGX Orin → whisper (STT)
-                                              ↓
-                                      text transcript
-                                              ↓
-                                      piper TTS (AGX Orin)
-                                              ↓
-                                      audio WAV file
-                                              ↓
-                              SCP back to MacBook Air → play / send
-```
-
-## Prerequisites
-
-- whisper on AGX Orin: `/home/alice/.local/bin/whisper`
-- piper on AGX Orin: `/usr/local/bin/piper`
-- Piper model: `/home/alice/piper-voices/en_US-lessac-high.onnx`
-- SSH key: `~/.ssh/alice_auto` (passphraseless) for `alice@agx-orin`
-
-## Usage
-
-### Transcribe (STT)
-```bash
-voice-pipeline.sh transcribe /path/to/audio.wav
-# Returns: transcribed text
-```
-
-### Speak (TTS)
-```bash
-voice-pipeline.sh respond "Text to speak"
-# Returns: /tmp/voice_response.wav
-```
-
-### Full pipeline test
-```bash
-~/.openclaw/workspace-olivia/bin/voice-pipeline.sh transcribe /tmp/test2.wav
-~/.openclaw/workspace-olivia/bin/voice-pipeline.sh respond "Hello from Alice"
-```
-
-## Telegram Integration
-
-To handle Telegram voice notes:
-1. Receive the `file_id` from the incoming message
-2. Download: `https://api.telegram.org/bot<TOKEN>/getFile?file_id=<file_id>`
-3. Get download URL: `https://api.telegram.org/file/bot<TOKEN>/<file_path>`
-4. Download audio → convert to 16kHz WAV
-5. Run `voice-pipeline.sh transcribe`
-6. Process transcript as normal text
-7. Run `voice-pipeline.sh respond "<text>"`
-8. Send voice note back via `message action=send ... asVoice=true`
-
-## Files
-
-- Script: `~/.openclaw/workspace-olivia/bin/voice-pipeline.sh`
-- SSH key: `~/.ssh/alice_auto`
-- AGX Orin: `agx-orin` (in ~/.ssh/config)

package/templates/workspaces/olivia/skills/weather/SKILL.md

@@ -1,49 +0,0 @@
----
-name: weather
-description: Get current weather and forecasts (no API key required).
-homepage: https://wttr.in/:help
-metadata: {"clawdbot":{"emoji":"🌤️","requires":{"bins":["curl"]}}}
----
-
-# Weather
-
-Two free services, no API keys needed.
-
-## wttr.in (primary)
-
-Quick one-liner:
-```bash
-curl -s "wttr.in/London?format=3"
-# Output: London: ⛅️ +8°C
-```
-
-Compact format:
-```bash
-curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w"
-# Output: London: ⛅️ +8°C 71% ↙5km/h
-```
-
-Full forecast:
-```bash
-curl -s "wttr.in/London?T"
-```
-
-Format codes: `%c` condition · `%t` temp · `%h` humidity · `%w` wind · `%l` location · `%m` moon
-
-Tips:
-- URL-encode spaces: `wttr.in/New+York`
-- Airport codes: `wttr.in/JFK`
-- Units: `?m` (metric) `?u` (USCS)
-- Today only: `?1` · Current only: `?0`
-- PNG: `curl -s "wttr.in/Berlin.png" -o /tmp/weather.png`
-
-## Open-Meteo (fallback, JSON)
-
-Free, no key, good for programmatic use:
-```bash
-curl -s "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12&current_weather=true"
-```
-
-Find coordinates for a city, then query. Returns JSON with temp, windspeed, weathercode.
-
-Docs: https://open-meteo.com/en/docs

package/templates/workspaces/olivia/skills/weather/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn70pywhg0fyz996kpa8xj89s57yhv26",
-  "slug": "weather",
-  "version": "1.0.0",
-  "publishedAt": 1767545394459
-}

package/templates/workspaces/olivia/skills/web-researcher/SKILL.md

@@ -1,21 +0,0 @@
----
-name: web-researcher
-description: "Use this skill for deep research, fact-checking, or finding the latest technical news."
----
-
-# Web Researcher Skill
-
-## When to use
-- Use when the user asks for "the latest," "news," or "research" on a topic.
-- Use when you need to verify a fact that isn't in your local training data.
-
-## Research Protocol
-1. **Multi-Query Search**: Don't just search once. Run 2-3 targeted searches (e.g., "OpenClaw 2026.3.2 features" AND "OpenClaw 2026.3.2 bugs").
-2. **Deep Dive**: Use `web_fetch` on at least the top 2 most relevant URLs to get the full text. Snippets are not enough for deep research.
-3. **Synthesis**: Summarize the findings by grouping them into "Key Facts," "Timeline," and "Contradictions" (if any).
-4. **Cite Sources**: Always list the URLs you actually read at the end of your report.
-
-## Output Format
-- Start with a 🪐 **Jupiter Research Brief** header.
-- Use bullet points for readability.
-- Highlight any "Breaking News" or "Critical Alerts" in bold.

package/templates/workspaces/olivia/skills/web-researcher/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn77r2q5g5g70eg9j17en64y5d8251aq",
-  "slug": "web-researcher",
-  "version": "1.0.0",
-  "publishedAt": 1772798446862
-}