@elizaos/skills 2.0.0-alpha.3

package/skills/video-frames/scripts/frame.sh

@@ -0,0 +1,81 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  cat >&2 <<'EOF'
+Usage:
+  frame.sh <video-file> [--time HH:MM:SS] [--index N] --out /path/to/frame.jpg
+
+Examples:
+  frame.sh video.mp4 --out /tmp/frame.jpg
+  frame.sh video.mp4 --time 00:00:10 --out /tmp/frame-10s.jpg
+  frame.sh video.mp4 --index 0 --out /tmp/frame0.png
+EOF
+  exit 2
+}
+
+if [[ "${1:-}" == "" || "${1:-}" == "-h" || "${1:-}" == "--help" ]]; then
+  usage
+fi
+
+in="${1:-}"
+shift || true
+
+time=""
+index=""
+out=""
+
+while [[ $# -gt 0 ]]; do
+  case "$1" in
+    --time)
+      time="${2:-}"
+      shift 2
+      ;;
+    --index)
+      index="${2:-}"
+      shift 2
+      ;;
+    --out)
+      out="${2:-}"
+      shift 2
+      ;;
+    *)
+      echo "Unknown arg: $1" >&2
+      usage
+      ;;
+  esac
+done
+
+if [[ ! -f "$in" ]]; then
+  echo "File not found: $in" >&2
+  exit 1
+fi
+
+if [[ "$out" == "" ]]; then
+  echo "Missing --out" >&2
+  usage
+fi
+
+mkdir -p "$(dirname "$out")"
+
+if [[ "$index" != "" ]]; then
+  ffmpeg -hide_banner -loglevel error -y \
+    -i "$in" \
+    -vf "select=eq(n\\,${index})" \
+    -vframes 1 \
+    "$out"
+elif [[ "$time" != "" ]]; then
+  ffmpeg -hide_banner -loglevel error -y \
+    -ss "$time" \
+    -i "$in" \
+    -frames:v 1 \
+    "$out"
+else
+  ffmpeg -hide_banner -loglevel error -y \
+    -i "$in" \
+    -vf "select=eq(n\\,0)" \
+    -vframes 1 \
+    "$out"
+fi
+
+echo "$out"

package/skills/voice-call/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: voice-call
+description: Start voice calls via the Otto voice-call plugin.
+metadata:
+  {
+    "otto":
+      {
+        "emoji": "📞",
+        "skillKey": "voice-call",
+        "requires": { "config": ["plugins.entries.voice-call.enabled"] },
+      },
+  }
+---
+
+# Voice Call
+
+Use the voice-call plugin to start or inspect calls (Twilio, Telnyx, Plivo, or mock).
+
+## CLI
+
+```bash
+otto voicecall call --to "+15555550123" --message "Hello from Otto"
+otto voicecall status --call-id <id>
+```
+
+## Tool
+
+Use `voice_call` for agent-initiated calls.
+
+Actions:
+
+- `initiate_call` (message, to?, mode?)
+- `continue_call` (callId, message)
+- `speak_to_user` (callId, message)
+- `end_call` (callId)
+- `get_status` (callId)
+
+Notes:
+
+- Requires the voice-call plugin to be enabled.
+- Plugin config lives under `plugins.entries.voice-call.config`.
+- Twilio config: `provider: "twilio"` + `twilio.accountSid/authToken` + `fromNumber`.
+- Telnyx config: `provider: "telnyx"` + `telnyx.apiKey/connectionId` + `fromNumber`.
+- Plivo config: `provider: "plivo"` + `plivo.authId/authToken` + `fromNumber`.
+- Dev fallback: `provider: "mock"` (no network).

package/skills/wacli/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: wacli
+description: Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
+homepage: https://wacli.sh
+metadata:
+  {
+    "otto":
+      {
+        "emoji": "📱",
+        "requires": { "bins": ["wacli"] },
+        "install":
+          [
+            {
+              "id": "brew",
+              "kind": "brew",
+              "formula": "steipete/tap/wacli",
+              "bins": ["wacli"],
+              "label": "Install wacli (brew)",
+            },
+            {
+              "id": "go",
+              "kind": "go",
+              "module": "github.com/steipete/wacli/cmd/wacli@latest",
+              "bins": ["wacli"],
+              "label": "Install wacli (go)",
+            },
+          ],
+      },
+  }
+---
+
+# wacli
+
+Use `wacli` only when the user explicitly asks you to message someone else on WhatsApp or when they ask to sync/search WhatsApp history.
+Do NOT use `wacli` for normal user chats; Otto routes WhatsApp conversations automatically.
+If the user is chatting with you on WhatsApp, you should not reach for this tool unless they ask you to contact a third party.
+
+Safety
+
+- Require explicit recipient + message text.
+- Confirm recipient + message before sending.
+- If anything is ambiguous, ask a clarifying question.
+
+Auth + sync
+
+- `wacli auth` (QR login + initial sync)
+- `wacli sync --follow` (continuous sync)
+- `wacli doctor`
+
+Find chats + messages
+
+- `wacli chats list --limit 20 --query "name or number"`
+- `wacli messages search "query" --limit 20 --chat <jid>`
+- `wacli messages search "invoice" --after 2025-01-01 --before 2025-12-31`
+
+History backfill
+
+- `wacli history backfill --chat <jid> --requests 2 --count 50`
+
+Send
+
+- Text: `wacli send text --to "+14155551212" --message "Hello! Are you free at 3pm?"`
+- Group: `wacli send text --to "1234567890-123456789@g.us" --message "Running 5 min late."`
+- File: `wacli send file --to "+14155551212" --file /path/agenda.pdf --caption "Agenda"`
+
+Notes
+
+- Store dir: `~/.wacli` (override with `--store`).
+- Use `--json` for machine-readable output when parsing.
+- Backfill requires your phone online; results are best-effort.
+- WhatsApp CLI is not needed for routine user chats; it’s for messaging other people.
+- JIDs: direct chats look like `<number>@s.whatsapp.net`; groups look like `<id>@g.us` (use `wacli chats list` to find).

package/skills/weather/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: weather
+description: Get current weather and forecasts (no API key required).
+homepage: https://wttr.in/:help
+metadata: { "otto": { "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/skills/yara-authoring/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "yara-authoring",
+  "version": "2.0.0",
+  "description": "YARA-X detection rule authoring with linting and quality analysis",
+  "author": {
+    "name": "Trail of Bits",
+    "email": "opensource@trailofbits.com"
+  }
+}

package/skills/yara-authoring/README.md

@@ -0,0 +1,131 @@
+# YARA-X Authoring Plugin
+
+A behavior-driven skill for authoring high-quality YARA-X detection rules, teaching you to think and act like an expert YARA author.
+
+> **YARA-X Focus:** This skill targets [YARA-X](https://virustotal.github.io/yara-x/), the Rust-based successor to legacy YARA. YARA-X powers VirusTotal's Livehunt/Retrohunt production systems and is 5-10x faster for regex-heavy rules. Legacy YARA (C implementation) is in maintenance mode.
+
+## Philosophy
+
+This skill doesn't dump YARA syntax at you. Instead, it teaches:
+
+- **Decision trees** for common judgment calls (Is this string good enough? When to abandon an approach?)
+- **Expert heuristics** (mutex names are gold, API names are garbage)
+- **Rationalizations to reject** (the shortcuts that cause production failures)
+
+An expert uses 5 tools: yarGen, FLOSS, `yr` CLI, signature-base, YARA-CI. Everything else is noise.
+
+## Installation
+
+### YARA-X CLI
+
+```bash
+# macOS
+brew install yara-x
+
+# Or from source
+cargo install yara-x
+
+# Verify installation
+yr --version
+```
+
+### Python Package (for scripts)
+
+```bash
+pip install yara-x
+# or with uv
+uv pip install yara-x
+```
+
+### Plugin
+
+Add this plugin to your Claude Code configuration:
+
+```bash
+claude mcp add-plugin /path/to/yara-authoring
+```
+
+## Skills
+
+### yara-rule-authoring
+
+Guides authoring of YARA-X rules for malware detection with expert judgment.
+
+**Covers:**
+- Decision trees for string quality, when to abandon approaches, debugging FPs
+- Expert heuristics from experienced YARA authors
+- Rationalizations to reject (common shortcuts that fail)
+- Naming conventions (CATEGORY_PLATFORM_FAMILY_DATE format)
+- Performance optimization (atom quality, short-circuit conditions)
+- Testing workflow (goodware corpus validation)
+- **YARA-X migration guide** for converting legacy rules
+- **Chrome extension analysis** with `crx` module
+- **Android DEX analysis** with `dex` module
+
+**Triggers:** YARA, YARA-X, malware detection, threat hunting, IOC, signature
+
+## Scripts
+
+The skill includes two Python scripts that require `uv` to run:
+
+### yara_lint.py
+
+Validates YARA-X rules for style, metadata, compatibility issues, and anti-patterns:
+
+```bash
+uv run yara_lint.py rule.yar
+uv run yara_lint.py --json rules/
+uv run yara_lint.py --strict rule.yar
+```
+
+### atom_analyzer.py
+
+Evaluates string quality for efficient atom extraction:
+
+```bash
+uv run atom_analyzer.py rule.yar
+uv run atom_analyzer.py --verbose rule.yar
+```
+
+## Reference Documentation
+
+| Document | Purpose |
+|----------|---------|
+| [style-guide.md](skills/yara-rule-authoring/references/style-guide.md) | Naming conventions, metadata requirements |
+| [performance.md](skills/yara-rule-authoring/references/performance.md) | Atom theory, optimization techniques |
+| [strings.md](skills/yara-rule-authoring/references/strings.md) | String selection judgment, good/bad patterns |
+| [testing.md](skills/yara-rule-authoring/references/testing.md) | Validation workflow, FP investigation |
+
+## Key Resources
+
+- [YARA-X Documentation](https://virustotal.github.io/yara-x/) (official)
+- [YARA-X GitHub](https://github.com/VirusTotal/yara-x)
+- [Neo23x0 YARA Style Guide](https://github.com/Neo23x0/YARA-Style-Guide)
+- [Neo23x0 Performance Guidelines](https://github.com/Neo23x0/YARA-Performance-Guidelines)
+- [signature-base Rule Collection](https://github.com/Neo23x0/signature-base)
+- [YARA-CI](https://yara-ci.cloud.virustotal.com/)
+
+## Requirements
+
+- Python 3.11+
+- [uv](https://github.com/astral-sh/uv) for running scripts
+- [YARA-X](https://virustotal.github.io/yara-x/) CLI (`yr`)
+
+The scripts use PEP 723 inline metadata, so dependencies are resolved automatically by `uv run`.
+
+## Migrating from Legacy YARA
+
+If you have existing rules written for legacy YARA:
+
+1. **Run validation:** `yr check --relaxed-re-syntax rules/`
+2. **Fix issues identified** (see SKILL.md migration section)
+3. **Validate without relaxed mode:** `yr check rules/`
+
+> **Note:** Use `--relaxed-re-syntax` only as a temporary diagnostic tool.
+> Fix all identified issues rather than relying on relaxed mode permanently.
+
+Common migration issues:
+- Unescaped `{` in regex patterns
+- Invalid escape sequences (`\R` → `\\R`)
+- Base64 patterns on strings < 3 characters
+- Negative array indexing