@robbiesrobotics/alice-agents 1.5.10 → 1.5.13

package/templates/workspaces/olivia/skills/azure-devops/SKILL.md

@@ -1,115 +0,0 @@
----
-name: azure-devops
-description: List Azure DevOps projects, repositories, and branches; create pull requests; manage work items; check build status. Use when working with Azure DevOps resources, checking PR status, querying project structure, or automating DevOps workflows.
-metadata: {"openclaw": {"emoji": "☁️", "requires": {"bins": ["curl", "jq"], "env": ["AZURE_DEVOPS_PAT"]}, "primaryEnv": "AZURE_DEVOPS_PAT"}}
----
-
-# Azure DevOps Skill
-
-List projects, repositories, branches. Create pull requests. Manage work items. Check build status.
-
-## Check before running for valid Configuration, if values missing ask the user!
-
-**Required:**
-- `AZURE_DEVOPS_PAT`: Personal Access Token
-- `AZURE_DEVOPS_ORG`: Organization name
-
-**If values are missing from `~/.openclaw/openclaw.json`, the agent should:**
-1. **ASK** the user for the missing PAT and/or organization name
-2. Store them in `~/.openclaw/openclaw.json` under `skills.entries["azure-devops"]`
-
-### Example Config
-
-```json5
-{
-  skills: {
-    entries: {
-      "azure-devops": {
-        apiKey: "YOUR_PERSONAL_ACCESS_TOKEN",  // AZURE_DEVOPS_PAT
-        env: {
-          AZURE_DEVOPS_ORG: "YourOrganizationName"
-        }
-      }
-    }
-  }
-}
-```
-
-## Commands
-
-### List Projects
-
-```bash
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/_apis/projects?api-version=7.1" \
-  | jq -r '.value[] | "\(.name) - \(.description // "No description")"'
-```
-
-### List Repositories in a Project
-
-```bash
-PROJECT="YourProject"
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/${PROJECT}/_apis/git/repositories?api-version=7.1" \
-  | jq -r '.value[] | "\(.name) - \(.webUrl)"'
-```
-
-### List Branches in a Repository
-
-```bash
-PROJECT="YourProject"
-REPO="YourRepo"
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/${PROJECT}/_apis/git/repositories/${REPO}/refs?filter=heads/&api-version=7.1" \
-  | jq -r '.value[] | .name | sub("refs/heads/"; "")'
-```
-
-### Create a Pull Request
-
-```bash
-PROJECT="YourProject"
-REPO_ID="repo-id-here"
-SOURCE_BRANCH="feature/my-branch"
-TARGET_BRANCH="main"
-TITLE="PR Title"
-DESCRIPTION="PR Description"
-
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  -H "Content-Type: application/json" \
-  -X POST \
-  -d '{
-    "sourceRefName": "refs/heads/'"${SOURCE_BRANCH}"'",
-    "targetRefName": "refs/heads/'"${TARGET_BRANCH}"'",
-    "title": "'"${TITLE}"'",
-    "description": "'"${DESCRIPTION}"'"
-  }' \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/${PROJECT}/_apis/git/repositories/${REPO_ID}/pullrequests?api-version=7.1"
-```
-
-### Get Repository ID
-
-```bash
-PROJECT="YourProject"
-REPO_NAME="YourRepo"
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/${PROJECT}/_apis/git/repositories/${REPO_NAME}?api-version=7.1" \
-  | jq -r '.id'
-```
-
-### List Pull Requests
-
-```bash
-PROJECT="YourProject"
-REPO_ID="repo-id"
-curl -s -u ":${AZURE_DEVOPS_PAT}" \
-  "https://dev.azure.com/${AZURE_DEVOPS_ORG}/${PROJECT}/_apis/git/repositories/${REPO_ID}/pullrequests?api-version=7.1" \
-  | jq -r '.value[] | "#\(.pullRequestId): \(.title) [\(.sourceRefName | sub("refs/heads/"; ""))] -> [\(.targetRefName | sub("refs/heads/"; ""))] - \(.createdBy.displayName)"'
-```
-
-## Notes
-
-- Base URL: `https://dev.azure.com/${AZURE_DEVOPS_ORG}`
-- API Version: `7.1`
-- Auth: Basic Auth with empty username and PAT as password
-- Never log or expose the PAT in responses
-- Documentation: https://learn.microsoft.com/en-us/rest/api/azure/devops/

package/templates/workspaces/olivia/skills/azure-devops/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn7fcaydc22jpp2mbrgsj8jffs80nxh3",
-  "slug": "azure-devops",
-  "version": "1.0.0",
-  "publishedAt": 1770664564141
-}

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

@@ -1,46 +0,0 @@
----
-name: blogwatcher
-description: Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
-homepage: https://github.com/Hyaxia/blogwatcher
-metadata: {"clawdbot":{"emoji":"📰","requires":{"bins":["blogwatcher"]},"install":[{"id":"go","kind":"go","module":"github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest","bins":["blogwatcher"],"label":"Install blogwatcher (go)"}]}}
----
-
-# blogwatcher
-
-Track blog and RSS/Atom feed updates with the `blogwatcher` CLI.
-
-Install
-- Go: `go install github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest`
-
-Quick start
-- `blogwatcher --help`
-
-Common commands
-- Add a blog: `blogwatcher add "My Blog" https://example.com`
-- List blogs: `blogwatcher blogs`
-- Scan for updates: `blogwatcher scan`
-- List articles: `blogwatcher articles`
-- Mark an article read: `blogwatcher read 1`
-- Mark all articles read: `blogwatcher read-all`
-- Remove a blog: `blogwatcher remove "My Blog"`
-
-Example output
-```
-$ blogwatcher blogs
-Tracked blogs (1):
-
-  xkcd
-    URL: https://xkcd.com
-```
-```
-$ blogwatcher scan
-Scanning 1 blog(s)...
-
-  xkcd
-    Source: RSS | Found: 4 | New: 4
-
-Found 4 new article(s) total!
-```
-
-Notes
-- Use `blogwatcher <command> --help` to discover flags and options.

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

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

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

@@ -1,27 +0,0 @@
----
-name: blucli
-description: BluOS CLI (blu) for discovery, playback, grouping, and volume.
-homepage: https://blucli.sh
-metadata: {"clawdbot":{"emoji":"🫐","requires":{"bins":["blu"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/blucli/cmd/blu@latest","bins":["blu"],"label":"Install blucli (go)"}]}}
----
-
-# blucli (blu)
-
-Use `blu` to control Bluesound/NAD players.
-
-Quick start
-- `blu devices` (pick target)
-- `blu --device <id> status`
-- `blu play|pause|stop`
-- `blu volume set 15`
-
-Target selection (in priority order)
-- `--device <id|name|alias>`
-- `BLU_DEVICE`
-- config default (if set)
-
-Common tasks
-- Grouping: `blu group status|add|remove`
-- TuneIn search/play: `blu tunein search "query"`, `blu tunein play "query"`
-
-Prefer `--json` for scripts. Confirm the target device before changing playback.

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

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

package/templates/workspaces/olivia/skills/check-analytics/SKILL.md

@@ -1,92 +0,0 @@
----
-name: check-analytics
-description: Audit existing Google Analytics implementation. Checks for common issues, missing configurations, and optimization opportunities.
----
-
-# Analytics Audit Skill
-
-You are auditing the Google Analytics implementation in this project.
-
-## Step 1: Find Existing Analytics
-
-Search for analytics code:
-- `gtag` or `dataLayer` references
-- Google Tag Manager (`GTM-`)
-- Universal Analytics (`UA-`) - deprecated
-- GA4 Measurement IDs (`G-`)
-- Third-party analytics (Mixpanel, Amplitude, Plausible, etc.)
-
-## Step 2: Generate Audit Report
-
-Create a report with these sections:
-
-### Current Setup
-- Framework detected
-- Analytics provider(s) found
-- Measurement ID(s) found (redact last 6 chars for security: `G-XXXX******`)
-- Implementation method (gtag.js, GTM, npm package)
-
-### Issues Found
-
-Check for:
-1. **Deprecated UA properties** - Universal Analytics sunset July 2024
-2. **Missing pageview tracking** for SPAs
-3. **Hardcoded Measurement IDs** (should use env vars)
-4. **Missing TypeScript types** for gtag
-5. **No consent mode** implementation
-6. **Debug mode in production** (check for `debug_mode: true`)
-7. **Duplicate script loading**
-8. **Missing error boundaries** around analytics code
-9. **Blocking script loading** (should be async)
-10. **No fallback** for ad-blocker scenarios
-
-### Recommendations
-
-Provide actionable fixes ranked by priority:
-- 🔴 Critical (breaking/deprecated)
-- 🟡 Warning (best practice violations)
-- 🟢 Suggestion (optimizations)
-
-### Event Coverage Analysis
-
-List custom events being tracked and suggest missing ones:
-- Sign up / Login events
-- Purchase/conversion events
-- Form submissions
-- Error tracking
-- Key user interactions
-
-## Output Format
-
-```markdown
-# Analytics Audit Report
-
-## Summary
-- **Status**: [Healthy / Needs Attention / Critical Issues]
-- **Provider**: [GA4 / GTM / Other]
-- **Framework**: [detected framework]
-
-## Current Implementation
-[describe what was found]
-
-## Issues
-
-### 🔴 Critical
-[list critical issues]
-
-### 🟡 Warnings
-[list warnings]
-
-### 🟢 Suggestions
-[list suggestions]
-
-## Event Coverage
-| Event Type | Status | Recommendation |
-|------------|--------|----------------|
-| Page Views | ✅ | - |
-| Sign Up | ❌ | Add sign_up event |
-| ... | ... | ... |
-
-## Next Steps
-1. [ordered action items]
-```

package/templates/workspaces/olivia/skills/check-analytics/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn7a4sqttds99g97yye7djqy1980dqy0",
-  "slug": "check-analytics",
-  "version": "0.1.0",
-  "publishedAt": 1770054071458
-}

package/templates/workspaces/olivia/skills/cloud-architect/SKILL.md

@@ -1,89 +0,0 @@
----
-name: cloud-architect
-description: Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.
-license: MIT
-metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: infrastructure
-  triggers: AWS, Azure, GCP, Google Cloud, cloud migration, cloud architecture, multi-cloud, cloud cost, Well-Architected, landing zone, cloud security, disaster recovery, cloud native, serverless architecture
-  role: architect
-  scope: infrastructure
-  output-format: architecture
-  related-skills: devops-engineer, kubernetes-specialist, terraform-engineer, security-reviewer, microservices-architect, monitoring-expert
----
-
-# Cloud Architect
-
-Senior cloud architect specializing in multi-cloud strategies, migration patterns, cost optimization, and cloud-native architectures across AWS, Azure, and GCP.
-
-## Role Definition
-
-You are a senior cloud architect with 15+ years of experience designing enterprise cloud solutions. You specialize in multi-cloud architectures, migration strategies (6Rs), cost optimization, security by design, and operational excellence. You design highly available, secure, and cost-effective cloud infrastructures following Well-Architected Framework principles.
-
-## When to Use This Skill
-
-- Designing cloud architectures (AWS, Azure, GCP)
-- Planning cloud migrations and modernization
-- Implementing multi-cloud and hybrid cloud strategies
-- Optimizing cloud costs (right-sizing, reserved instances, spot)
-- Designing for high availability and disaster recovery
-- Implementing cloud security and compliance
-- Setting up landing zones and governance
-- Architecting serverless and container platforms
-
-## Core Workflow
-
-1. **Discovery** - Assess current state, requirements, constraints, compliance needs
-2. **Design** - Select services, design topology, plan data architecture
-3. **Security** - Implement zero-trust, identity federation, encryption
-4. **Cost Model** - Right-size resources, reserved capacity, auto-scaling
-5. **Migration** - Apply 6Rs framework, define waves, test failover
-6. **Operate** - Set up monitoring, automation, continuous optimization
-
-## Reference Guide
-
-Load detailed guidance based on context:
-
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| AWS Services | `references/aws.md` | EC2, S3, Lambda, RDS, Well-Architected Framework |
-| Azure Services | `references/azure.md` | VMs, Storage, Functions, SQL, Cloud Adoption Framework |
-| GCP Services | `references/gcp.md` | Compute Engine, Cloud Storage, Cloud Functions, BigQuery |
-| Multi-Cloud | `references/multi-cloud.md` | Abstraction layers, portability, vendor lock-in mitigation |
-| Cost Optimization | `references/cost.md` | Reserved instances, spot, right-sizing, FinOps practices |
-
-## Constraints
-
-### MUST DO
-- Design for high availability (99.9%+)
-- Implement security by design (zero-trust)
-- Use infrastructure as code (Terraform, CloudFormation)
-- Enable cost allocation tags and monitoring
-- Plan disaster recovery with defined RTO/RPO
-- Implement multi-region for critical workloads
-- Use managed services when possible
-- Document architectural decisions
-
-### MUST NOT DO
-- Store credentials in code or public repos
-- Skip encryption (at rest and in transit)
-- Create single points of failure
-- Ignore cost optimization opportunities
-- Deploy without proper monitoring
-- Use overly complex architectures
-- Ignore compliance requirements
-- Skip disaster recovery testing
-
-## Output Templates
-
-When designing cloud architecture, provide:
-1. Architecture diagram with services and data flow
-2. Service selection rationale (compute, storage, database, networking)
-3. Security architecture (IAM, network segmentation, encryption)
-4. Cost estimation and optimization strategy
-5. Deployment approach and rollback plan
-
-## Knowledge Reference
-
-AWS (EC2, S3, Lambda, RDS, VPC, CloudFront), Azure (VMs, Blob Storage, Functions, SQL Database, VNet), GCP (Compute Engine, Cloud Storage, Cloud Functions, Cloud SQL), Kubernetes, Docker, Terraform, CloudFormation, ARM templates, CI/CD, disaster recovery, cost optimization, security best practices, compliance frameworks (SOC2, HIPAA, PCI-DSS)

package/templates/workspaces/olivia/skills/cloud-architect/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn73yagkag2f0yzt0xetz2zfr582bstw",
-  "slug": "cloud-architect",
-  "version": "0.1.0",
-  "publishedAt": 1772892986422
-}

package/templates/workspaces/olivia/skills/cloud-infra-automation/SKILL.md

@@ -1,50 +0,0 @@
-# Cloud Infrastructure Automation
-
-Automate cloud infrastructure with IaC.
-
-## Features
-
-### Multi-Cloud Support
-- AWS
-- Google Cloud Platform
-- Azure
-
-### Infrastructure as Code
-- Terraform templates
-- Ansible playbooks
-- CloudFormation
-
-### Automation
-- Server provisioning
-- Configuration management
-- Deployment pipelines
-
-## Quick Start
-
-```bash
-# Initialize AWS
-./cloud.sh init aws
-
-# Create infrastructure
-./cloud.sh apply prod
-
-# Destroy
-./cloud.sh destroy prod
-```
-
-## Templates
-
-- Web application
-- Database setup
-- Kubernetes cluster
-- Serverless functions
-
-## Requirements
-
-- Terraform
-- Ansible
-- AWS/GCP/Azure CLI
-
-## Author
-
-Sunshine-del-ux

package/templates/workspaces/olivia/skills/cloud-infra-automation/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn754w8negkve53dntzhycyd0h82565k",
-  "slug": "cloud-infra-automation",
-  "version": "1.0.0",
-  "publishedAt": 1772652022543
-}

package/templates/workspaces/olivia/skills/cloud-storage/SKILL.md

@@ -1,61 +0,0 @@
----
-name: Cloud Storage
-slug: cloud-storage
-version: 1.0.1
-description: Manage files across cloud providers with authentication, cost awareness, and multi-provider operations.
-changelog: Added When to Use section for consistency
-metadata: {"clawdbot":{"emoji":"☁️","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
----
-
-## When to Use
-
-User needs to upload, download, sync, or manage files across cloud storage providers. Agent handles multi-provider operations with cost awareness.
-
-## Quick Reference
-
-| Topic | File |
-|-------|------|
-| Provider-specific patterns | `providers.md` |
-| Authentication setup | `auth.md` |
-| Cost calculation | `costs.md` |
-
-## Scope
-
-This skill covers operational cloud storage tasks across providers:
-- S3, GCS, Azure Blob, Backblaze B2, Cloudflare R2
-- Google Drive, Dropbox, OneDrive, iCloud
-
-For storage architecture decisions, see `storage` skill.
-For S3-specific deep patterns, see `s3` skill.
-
-## Critical Rules
-
-1. **Verify operations completed** — API 200 ≠ success; check file exists with correct size/checksum
-2. **Calculate ALL costs before large transfers** — egress fees often exceed storage costs; check `costs.md`
-3. **Never delete without backup verification** — confirm backup exists AND is restorable before removing source
-4. **Handle partial failures** — long operations fail mid-way; implement checkpoints and resume logic
-5. **Rate limits vary wildly** — Google 750GB/day upload, Dropbox batch limits, S3 3500 PUT/s per prefix
-
-## Authentication Traps
-
-- **OAuth tokens expire** — refresh before long operations, not during
-- **Service account ≠ user account** — different quotas, permissions, audit trails
-- **Wrong region/endpoint** — S3 bucket in `eu-west-1` won't work with `s3.amazonaws.com`
-- **MFA required** — some operations need session tokens, plan for interactive auth
-
-## Multi-Provider Gotchas
-
-| Concept | Translates differently |
-|---------|----------------------|
-| Shared folder | Drive "Shared with me" ≠ Dropbox "Team Folders" ≠ OneDrive "SharePoint" |
-| File ID | Drive uses IDs; Dropbox uses paths; S3 uses keys |
-| Versioning | S3 explicit enable; Drive automatic; Dropbox 180 days |
-| Permissions | S3 ACLs + policies; Drive roles; Dropbox link-based |
-
-## Before Any Bulk Operation
-
-- [ ] Estimated time calculated (size ÷ bandwidth)
-- [ ] Rate limits checked for both source AND destination
-- [ ] Cost estimate including egress + API calls
-- [ ] Checkpoint/resume strategy for failures
-- [ ] Verification method defined (checksum, count, spot-check)

package/templates/workspaces/olivia/skills/cloud-storage/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn73vp5rarc3b14rc7wjcw8f8580t5d1",
-  "slug": "cloud-storage",
-  "version": "1.0.1",
-  "publishedAt": 1771412465611
-}

package/templates/workspaces/olivia/skills/cloud-storage/auth.md

@@ -1,97 +0,0 @@
-# Authentication Setup
-
-## Service Accounts vs User Accounts
-
-| Aspect | Service Account | User Account |
-|--------|-----------------|--------------|
-| Best for | Automated operations, servers | Interactive, per-user access |
-| Quotas | Usually higher | Per-user limits |
-| MFA | Not applicable | May be required |
-| Audit | Clear service identity | Mixed with user activity |
-
-**Rule:** Use service accounts for automation; user accounts for interactive tools.
-
----
-
-## AWS Authentication
-
-```bash
-# Environment variables (session)
-export AWS_ACCESS_KEY_ID=AKIA...
-export AWS_SECRET_ACCESS_KEY=...
-export AWS_DEFAULT_REGION=us-east-1
-
-# Named profiles (~/.aws/credentials)
-[profile-name]
-aws_access_key_id = AKIA...
-aws_secret_access_key = ...
-region = us-east-1
-
-# IAM roles (recommended for EC2/Lambda)
-# Automatic via instance metadata
-```
-
-**Traps:**
-- Access keys rotate; automate rotation
-- Root account keys = security incident
-- Region mismatch = "bucket not found" errors
-
----
-
-## Google Cloud Authentication
-
-```bash
-# Service account (recommended)
-export GOOGLE_APPLICATION_CREDENTIALS=/path/to/key.json
-
-# User account (interactive)
-gcloud auth login
-gcloud auth application-default login
-
-# Impersonation (for local dev with SA permissions)
-gcloud auth application-default login --impersonate-service-account=SA@PROJECT.iam.gserviceaccount.com
-```
-
-**Traps:**
-- OAuth tokens expire in 1 hour
-- Service account keys are security-sensitive; prefer Workload Identity
-- `application-default` vs `gcloud auth` are different credential chains
-
----
-
-## Azure Authentication
-
-```bash
-# Service Principal
-export AZURE_CLIENT_ID=...
-export AZURE_TENANT_ID=...
-export AZURE_CLIENT_SECRET=...
-
-# CLI login
-az login
-az account set --subscription NAME
-
-# Managed Identity (Azure VMs)
-# Automatic via IMDS
-```
-
-**Traps:**
-- Tenant vs subscription confusion
-- SAS tokens leak easily; use short expiration
-- RBAC propagation takes minutes
-
----
-
-## OAuth for Consumer Services
-
-### Google Drive / Dropbox / OneDrive
-
-1. **Create OAuth app** in provider console
-2. **Request minimal scopes** — `drive.file` not `drive` for Google
-3. **Store refresh tokens** — access tokens expire quickly
-4. **Handle token refresh** before long operations
-
-**Traps:**
-- Refresh tokens can be revoked by user
-- Scopes determine what operations work
-- Rate limits often per-user, not per-app