@robbiesrobotics/alice-agents 1.5.10 → 1.5.13

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

@@ -1,217 +0,0 @@
----
-name: himalaya
-description: "CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language)."
-homepage: https://github.com/pimalaya/himalaya
-metadata: {"clawdbot":{"emoji":"📧","requires":{"bins":["himalaya"]},"install":[{"id":"brew","kind":"brew","formula":"himalaya","bins":["himalaya"],"label":"Install Himalaya (brew)"}]}}
----
-
-# Himalaya Email CLI
-
-Himalaya is a CLI email client that lets you manage emails from the terminal using IMAP, SMTP, Notmuch, or Sendmail backends.
-
-## References
-
-- `references/configuration.md` (config file setup + IMAP/SMTP authentication)
-- `references/message-composition.md` (MML syntax for composing emails)
-
-## Prerequisites
-
-1. Himalaya CLI installed (`himalaya --version` to verify)
-2. A configuration file at `~/.config/himalaya/config.toml`
-3. IMAP/SMTP credentials configured (password stored securely)
-
-## Configuration Setup
-
-Run the interactive wizard to set up an account:
-```bash
-himalaya account configure
-```
-
-Or create `~/.config/himalaya/config.toml` manually:
-```toml
-[accounts.personal]
-email = "you@example.com"
-display-name = "Your Name"
-default = true
-
-backend.type = "imap"
-backend.host = "imap.example.com"
-backend.port = 993
-backend.encryption.type = "tls"
-backend.login = "you@example.com"
-backend.auth.type = "password"
-backend.auth.cmd = "pass show email/imap"  # or use keyring
-
-message.send.backend.type = "smtp"
-message.send.backend.host = "smtp.example.com"
-message.send.backend.port = 587
-message.send.backend.encryption.type = "start-tls"
-message.send.backend.login = "you@example.com"
-message.send.backend.auth.type = "password"
-message.send.backend.auth.cmd = "pass show email/smtp"
-```
-
-## Common Operations
-
-### List Folders
-
-```bash
-himalaya folder list
-```
-
-### List Emails
-
-List emails in INBOX (default):
-```bash
-himalaya envelope list
-```
-
-List emails in a specific folder:
-```bash
-himalaya envelope list --folder "Sent"
-```
-
-List with pagination:
-```bash
-himalaya envelope list --page 1 --page-size 20
-```
-
-### Search Emails
-
-```bash
-himalaya envelope list from john@example.com subject meeting
-```
-
-### Read an Email
-
-Read email by ID (shows plain text):
-```bash
-himalaya message read 42
-```
-
-Export raw MIME:
-```bash
-himalaya message export 42 --full
-```
-
-### Reply to an Email
-
-Interactive reply (opens $EDITOR):
-```bash
-himalaya message reply 42
-```
-
-Reply-all:
-```bash
-himalaya message reply 42 --all
-```
-
-### Forward an Email
-
-```bash
-himalaya message forward 42
-```
-
-### Write a New Email
-
-Interactive compose (opens $EDITOR):
-```bash
-himalaya message write
-```
-
-Send directly using template:
-```bash
-cat << 'EOF' | himalaya template send
-From: you@example.com
-To: recipient@example.com
-Subject: Test Message
-
-Hello from Himalaya!
-EOF
-```
-
-Or with headers flag:
-```bash
-himalaya message write -H "To:recipient@example.com" -H "Subject:Test" "Message body here"
-```
-
-### Move/Copy Emails
-
-Move to folder:
-```bash
-himalaya message move 42 "Archive"
-```
-
-Copy to folder:
-```bash
-himalaya message copy 42 "Important"
-```
-
-### Delete an Email
-
-```bash
-himalaya message delete 42
-```
-
-### Manage Flags
-
-Add flag:
-```bash
-himalaya flag add 42 --flag seen
-```
-
-Remove flag:
-```bash
-himalaya flag remove 42 --flag seen
-```
-
-## Multiple Accounts
-
-List accounts:
-```bash
-himalaya account list
-```
-
-Use a specific account:
-```bash
-himalaya --account work envelope list
-```
-
-## Attachments
-
-Save attachments from a message:
-```bash
-himalaya attachment download 42
-```
-
-Save to specific directory:
-```bash
-himalaya attachment download 42 --dir ~/Downloads
-```
-
-## Output Formats
-
-Most commands support `--output` for structured output:
-```bash
-himalaya envelope list --output json
-himalaya envelope list --output plain
-```
-
-## Debugging
-
-Enable debug logging:
-```bash
-RUST_LOG=debug himalaya envelope list
-```
-
-Full trace with backtrace:
-```bash
-RUST_LOG=trace RUST_BACKTRACE=1 himalaya envelope list
-```
-
-## Tips
-
-- Use `himalaya --help` or `himalaya <command> --help` for detailed usage.
-- Message IDs are relative to the current folder; re-list after folder changes.
-- For composing rich emails with attachments, use MML syntax (see `references/message-composition.md`).
-- Store passwords securely using `pass`, system keyring, or a command that outputs the password.

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

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn71t8cr12n54xdhz51fncgg0h7yr8dt",
-  "slug": "himalaya",
-  "version": "1.0.0",
-  "publishedAt": 1767954271328
-}

package/templates/workspaces/olivia/skills/hotel-recommendation/SKILL.md

@@ -1,117 +0,0 @@
----
-name: hotel-recommendation
-description: 使用 RollingGo CLI 查询酒店信息、筛选结果、读取酒店标签和获取房型价格。当用户需要按目的地 / 日期 / 星级 / 预算 / 标签 / 距离搜索酒店、查看酒店详情与房型报价，或读取酒店标签库时触发本技能。触发短语——"搜索酒店"、"查酒店"、"酒店详情"、"房型价格"、"酒店标签"、"附近酒店"、"rollinggo"。
-homepage: https://mcp.agentichotel.cn
-metadata:
-  {
-    "openclaw": {
-      "emoji": "🏨",
-      "primaryEnv": "AIGOHOTEL_API_KEY",
-      "requires": {
-        "anyBins": ["rollinggo", "npx", "node", "uvx", "uv"],
-        "env": ["AIGOHOTEL_API_KEY"]
-      },
-      "install": [
-        {
-          "id": "node",
-          "kind": "node",
-          "package": "rollinggo",
-          "bins": ["rollinggo"],
-          "label": "Install rollinggo (npm)"
-        },
-        {
-          "id": "uv",
-          "kind": "uv",
-          "package": "rollinggo",
-          "bins": ["rollinggo"],
-          "label": "Install rollinggo (uv)"
-        }
-      ]
-    }
-  }
----
-
-# RollingGo 酒店 CLI
-
-## 适用范围
-
-✅ **在以下情况使用本技能：**
-- **查找候选酒店：** 用户需要按城市、地标、机场或具体地址搜索附近酒店（例如：“查找东京迪士尼附近的酒店”）。
-- **多条件精准筛选：** 用户需要在搜索时结合自然语言意图，并严格限制入离日期、入住人数、预算上限、星级区间或距离范围。
-- **基于标签与品牌匹配：** 用户想寻找包含特定设施或属于特定品牌的酒店（如“亲子友好”、“包含早餐”、“万豪”等），技能可先查询标签库以进行精准筛选。
-- **查询房型与实时报价：** 用户想深入了解某家具体酒店（通过 hotelId）的可用房型、实时价格、退款政策或具体配置。
-- **酒店对比与评估：** 用户需要基于真实的结构化数据和当前报价，在多个候选酒店中进行对比分析。
-- **酒店预订：** 用户选定酒店想要完成预订时。可提取并提供结果中的预订 URL 或酒店主页链接，引导用户直接点击完成购买。
-
-❌ **以下情况不适用：**
-- 用户询问非酒店类的旅游预订业务（如机票、火车票、接送机、租车等）。
-
-## API Key
-
-解析顺序：`--api-key` 参数 → `AIGOHOTEL_API_KEY` 环境变量。
-
-还没有 Key？前往申请：https://mcp.agentichotel.cn/apply
-
-## 运行环境
-
-根据用户环境选择，加载对应的参考文件，并在整个会话中保持一致。
-
-- **`npm`、`npx`、Node 或无明确偏好：** 加载 [references/rollinggo-npx.md](references/rollinggo-npx.md)
-- **`uv`、`uvx`、PyPI 或 Python：** 加载 [references/rollinggo-uv.md](references/rollinggo-uv.md)
-- **一致性检查或对比：** 同时加载两个参考文件
-
-未明确指定时默认使用 **npm/npx**（跨环境兼容性更好）。
-
-## 主要工作流
-
-除非用户已经把问题限定在某个具体步骤，否则按顺序执行：
-
-1. 明确需求：目的地、日期、晚数、入住人数、预算、星级、标签、距离
-2. 如果需要标签筛选 → 先执行 `hotel-tags` 获取有效标签字符串
-3. 执行 `search-hotels` → 解析 JSON → 提取 `hotelId`
-4. 执行 `hotel-detail --hotel-id <id>` 查询房型和价格
-5. 如果结果不理想 → 放宽筛选条件后重新搜索
-
-## 常用命令速查
-
-```bash
-# 获取标签库
-rollinggo hotel-tags
-
-# 搜索酒店（最少必填参数）
-rollinggo search-hotels \
-  --origin-query "<用户的自然语言描述>" \
-  --place "<目的地>" \
-  --place-type "<查看 --help 获取合法值>"
-
-# 查询酒店详情与价格
-rollinggo hotel-detail \
-  --hotel-id <id> \
-  --check-in-date YYYY-MM-DD \
-  --check-out-date YYYY-MM-DD \
-  --adult-count 2 --room-count 1
-
-# 查看所有可用参数
-rollinggo search-hotels --help
-rollinggo hotel-detail --help
-```
-
-## 关键规则
-
-- `--place-type` 必须使用 `rollinggo search-hotels --help` 里显示的精确值
-- `--star-ratings` 格式：`最小值,最大值`，如 `4.0,5.0`
-- `--format table` **只允许**用于 `search-hotels`；`hotel-detail` 和 `hotel-tags` 会拒绝该参数
-- `--child-count` 的数量必须与 `--child-age` 参数的个数一致
-- `--check-out-date` 必须晚于 `--check-in-date`
-- 有 `hotelId` 时优先使用 `--hotel-id`，不要依赖 `--name`
-
-## 输出说明
-
-- stdout → 结果数据（默认 JSON）
-- stderr → 仅错误信息
-- 退出码 `0` 成功 · `1` HTTP/网络失败 · `2` CLI 参数校验失败
-- 结果中包含预订 URL 与酒店详情页链接，可供下游直接使用
-
-## 无结果时的放宽策略
-
-按顺序尝试：移除 `--star-ratings` → 增大 `--size` → 增大 `--distance-in-meter` → 移除标签筛选 → 放宽日期或预算

package/templates/workspaces/olivia/skills/hotel-recommendation/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn7bfacvm6tfsat3h4xf9rgt4582txgv",
-  "slug": "hotel-recommendation",
-  "version": "1.0.0",
-  "publishedAt": 1773391302394
-}

package/templates/workspaces/olivia/skills/hr-policy-generator/SKILL.md

@@ -1,54 +0,0 @@
----
-name: hr-policy-generator
-version: 1.0.0
-description: "Comprehensive HR policy development covering attendance, time-off, overtime, remote work, and compliance. Generates structured policy documents, legal checklists, exception handling frameworks, and employee communication plans tailored to company size, work arrangement, and jurisdiction."
-author: "hr-policy"
-tags:
-  - hr
-  - policy
-  - attendance
-  - leave
-  - overtime
-  - compliance
-  - remote-work
-invocable: true
----
-
-# HR Policy Generator
-
-## Description
-Comprehensive HR policy development covering attendance, time-off, overtime, remote work, and compliance. Generates structured policy documents, legal checklists, exception handling frameworks, and employee communication plans tailored to company size, work arrangement, and jurisdiction.
-
-## Input
-
-| Name | Type | Required | Description |
-|------|------|----------|-------------|
-| company_size | text | Yes | Number of employees and locations |
-| work_arrangement | text | Yes | On-site, remote, hybrid structure |
-| jurisdiction | text | Yes | Applicable labor laws and regulations |
-| current_policy | text | No | Existing attendance policies |
-| employee_feedback | text | No | Known concerns or requests |
-| industry_standards | text | No | Industry benchmark practices |
-
-## Output
-
-| Name | Type | Description |
-|------|------|-------------|
-| attendance_policy | text | Comprehensive policy document |
-| work_hours_framework | text | Core hours and flexibility guidelines |
-| leave_categories | text | PTO, sick, parental, other leave types |
-| overtime_policy | text | Overtime rules and compensation |
-| exception_procedures | text | Handling exceptions and accommodations |
-| compliance_checklist | text | Legal compliance verification |
-| communication_plan | text | Employee rollout and training |
-
-## Example
-
-### Input
-```json
-{
-  "company_size": "150 employees, 2 offices",
-  "work_arrangement": "Hybrid - 3 days office, 2 days remote",
-  "jurisdiction": "California, USA",
-  "current_policy": "Informal flexible schedule, unlimited PTO"
-}

package/templates/workspaces/olivia/skills/hr-policy-generator/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn753nka2j54zbbgr8jx5nm1r982qmvk",
-  "slug": "hr-policy-generator",
-  "version": "1.0.0",
-  "publishedAt": 1774236290307
-}

package/templates/workspaces/olivia/skills/human-writing/SKILL.md

@@ -1,41 +0,0 @@
----
-name: human-writing
-description: "Write content that reads as naturally human — no AI tells, no corporate fluff. Use when drafting, editing, or reviewing any content meant for publication or external audiences: blog posts, articles, newsletters, marketing copy, social media threads, client-facing documents, website copy, emails to lists. NOT for: casual chat, code, internal notes, or quick replies."
----
-
-# Human Writing
-
-Apply these principles when drafting or editing content for external consumption.
-
-## Core rules
-
-1. Be specific over general — concrete facts beat vague praise
-2. Use simple verbs — is, has, was, did — not "serves as," "boasts," "showcases"
-3. No cheerleading — state facts, skip "this is important because…"
-4. Repeat words comfortably — humans reuse words; don't cycle synonyms
-5. Short sentences are fine — not everything needs three clauses
-6. Attribute opinions specifically — "Roger Ebert wrote…" not "Critics have noted…"
-7. Skip forced significance — not everything "reflects broader trends"
-8. Use lowercase headings — title case screams AI
-9. Bold sparingly — not every other phrase
-10. Use contractions — "it's," "don't," "won't" sound human
-
-## Before publishing
-
-Scan the draft against the full anti-AI patterns reference for red flags:
-
-```
-read references/anti-ai-patterns.md
-```
-
-Check for:
-- Clusters of AI vocabulary (delve, pivotal, tapestry, etc.)
-- "-ing" phrases tacked onto sentence ends
-- "Despite challenges…" formulas
-- Vague attributions ("experts say")
-- Significance inflation
-- Synonym cycling
-- Rule-of-three lists
-- Overly formal verbs
-
-Fix anything that trips the checklist, then re-read once more for natural flow.

package/templates/workspaces/olivia/skills/human-writing/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn7cgf499vf9ewpg144hw60pm181ssr0",
-  "slug": "human-writing",
-  "version": "1.0.0",
-  "publishedAt": 1772341795201
-}

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

@@ -1,25 +0,0 @@
----
-name: imsg
-description: iMessage/SMS CLI for listing chats, history, watch, and sending.
-homepage: https://imsg.to
-metadata: {"clawdbot":{"emoji":"📨","os":["darwin"],"requires":{"bins":["imsg"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/imsg","bins":["imsg"],"label":"Install imsg (brew)"}]}}
----
-
-# imsg
-
-Use `imsg` to read and send Messages.app iMessage/SMS on macOS.
-
-Requirements
-- Messages.app signed in
-- Full Disk Access for your terminal
-- Automation permission to control Messages.app (for sending)
-
-Common commands
-- List chats: `imsg chats --limit 10 --json`
-- History: `imsg history --chat-id 1 --limit 20 --attachments --json`
-- Watch: `imsg watch --chat-id 1 --attachments`
-- Send: `imsg send --to "+14155551212" --text "hi" --file /path/pic.jpg`
-
-Notes
-- `--service imessage|sms|auto` controls delivery.
-- Confirm recipient + message before sending.

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

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

package/templates/workspaces/olivia/skills/in-depth-research/SKILL.md

@@ -1,124 +0,0 @@
----
-name: "Deep Research"
-description: "Conduct exhaustive multi-source investigation with methodology tracking, source evaluation, and iterative depth."
----
-
-## Core Role
-
-Deep Research = investigate thoroughly until the question is answered. Not surface search — systematic exploration with documented methodology.
-
-**Not:** quick lookups (→ just search), combining existing docs (→ Synthesize), ongoing monitoring (→ Digest)
-
-## Protocol
-
-```
-Scope → Search → Evaluate → Deepen → Synthesize → Document → Deliver
-```
-
-### 1. Scope
-
-Before searching, clarify:
-- What exactly needs answering?
-- What depth is required? (Overview / Thorough / Exhaustive)
-- What's the decision this enables?
-- Time/effort budget?
-
-Reframe vague questions into specific, answerable queries.
-
-### 2. Search
-
-Multi-vector approach (see `methodology.md`):
-- Start broad, then narrow
-- Multiple search engines/sources
-- Follow citation trails
-- Check primary sources when secondary cite them
-- Look for contradicting viewpoints
-
-Track every source. Nothing unattributed.
-
-### 3. Evaluate
-
-For each source (see `sources.md`):
-- Authority: Who wrote this? What credentials?
-- Recency: When? Still valid?
-- Evidence: Claims backed by data?
-- Bias: Any agenda or conflict?
-- Corroboration: Do others confirm this?
-
-Flag low-credibility sources. Weight findings accordingly.
-
-### 4. Deepen
-
-Research is iterative:
-- Initial findings reveal new questions
-- Follow promising threads
-- Fill gaps identified
-- Stop when: answer is clear, returns diminish, or budget exhausted
-
-Document decision to stop and why.
-
-### 5. Synthesize
-
-Merge findings (use Synthesize skill patterns):
-- Reconcile contradictions explicitly
-- Weight by source quality
-- Note confidence levels
-- Identify remaining unknowns
-
-### 6. Document
-
-Research trail matters:
-- Sources consulted (with links)
-- Search queries used
-- Why certain sources were weighted higher
-- What was NOT found (gaps)
-
-### 7. Deliver
-
-Format per user needs (see `output-formats.md`):
-- Executive: BLUF + key findings + confidence
-- Academic: Full methodology + citations
-- Working doc: All findings for further work
-
-## Output Format (Default)
-
-```
-🔬 DEEP RESEARCH: [Topic]
-
-⚡ ANSWER
-[Direct answer to the question — 2-3 sentences]
-
-📊 CONFIDENCE: [High/Medium/Low] — [why]
-
-🔍 KEY FINDINGS
-• [Finding 1] — [source]
-• [Finding 2] — [source]
-• [Finding 3] — [source]
-
-⚠️ CAVEATS
-• [Important limitation or uncertainty]
-
-🕳️ GAPS
-• [What couldn't be determined]
-
-📚 SOURCES ([count])
-[Numbered list with credibility notes]
-
-🔎 METHODOLOGY
-[Brief: what was searched, how sources were evaluated]
-```
-
-## Depth Levels
-
-| Level | Effort | Sources | When |
-|-------|--------|---------|------|
-| Quick | 5-10 min | 3-5 | Simple factual questions |
-| Standard | 30-60 min | 8-15 | Most research requests |
-| Thorough | 2-4 hours | 20-30 | Important decisions |
-| Exhaustive | Days | 50+ | Critical, high-stakes |
-
-Confirm depth before starting. Adjust if findings warrant.
-
----
-
-*References: `methodology.md`, `sources.md`, `output-formats.md`*

package/templates/workspaces/olivia/skills/in-depth-research/_meta.json

@@ -1,6 +0,0 @@
-{
-  "ownerId": "kn73vp5rarc3b14rc7wjcw8f8580t5d1",
-  "slug": "in-depth-research",
-  "version": "1.0.0",
-  "publishedAt": 1770895078301
-}