@symerian/symi 3.0.17 → 3.0.18

package/skills/bear-notes/SKILL.md

@@ -1,108 +0,0 @@
----
-name: bear-notes
-description: Create, search, and manage Bear notes via grizzly CLI.
-homepage: https://bear.app
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "🐻",
-        "os": ["darwin"],
-        "requires": { "bins": ["grizzly"] },
-        "install":
-          [
-            {
-              "id": "go",
-              "kind": "go",
-              "module": "github.com/tylerwince/grizzly/cmd/grizzly@latest",
-              "bins": ["grizzly"],
-              "label": "Install grizzly (go)",
-            },
-          ],
-      },
-  }
-triggers: [bear-notes, bear, notes]
----
-
-# Bear Notes
-
-Use `grizzly` to create, read, and manage notes in Bear on macOS.
-
-Requirements
-
-- Bear app installed and running
-- For some operations (add-text, tags, open-note --selected), a Bear app token (stored in `~/.config/grizzly/token`)
-
-## Getting a Bear Token
-
-For operations that require a token (add-text, tags, open-note --selected), you need an authentication token:
-
-1. Open Bear → Help → API Token → Copy Token
-2. Save it: `echo "YOUR_TOKEN" > ~/.config/grizzly/token`
-
-## Common Commands
-
-Create a note
-
-```bash
-echo "Note content here" | grizzly create --title "My Note" --tag work
-grizzly create --title "Quick Note" --tag inbox < /dev/null
-```
-
-Open/read a note by ID
-
-```bash
-grizzly open-note --id "NOTE_ID" --enable-callback --json
-```
-
-Append text to a note
-
-```bash
-echo "Additional content" | grizzly add-text --id "NOTE_ID" --mode append --token-file ~/.config/grizzly/token
-```
-
-List all tags
-
-```bash
-grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token
-```
-
-Search notes (via open-tag)
-
-```bash
-grizzly open-tag --name "work" --enable-callback --json
-```
-
-## Options
-
-Common flags:
-
-- `--dry-run` — Preview the URL without executing
-- `--print-url` — Show the x-callback-url
-- `--enable-callback` — Wait for Bear's response (needed for reading data)
-- `--json` — Output as JSON (when using callbacks)
-- `--token-file PATH` — Path to Bear API token file
-
-## Configuration
-
-Grizzly reads config from (in priority order):
-
-1. CLI flags
-2. Environment variables (`GRIZZLY_TOKEN_FILE`, `GRIZZLY_CALLBACK_URL`, `GRIZZLY_TIMEOUT`)
-3. `.grizzly.toml` in current directory
-4. `~/.config/grizzly/config.toml`
-
-Example `~/.config/grizzly/config.toml`:
-
-```toml
-token_file = "~/.config/grizzly/token"
-callback_url = "http://127.0.0.1:42123/success"
-timeout = "5s"
-```
-
-## Notes
-
-- Bear must be running for commands to work
-- Note IDs are Bear's internal identifiers (visible in note info or via callbacks)
-- Use `--enable-callback` when you need to read data back from Bear
-- Some operations require a valid token (add-text, tags, open-note --selected)

package/skills/blogwatcher/SKILL.md

@@ -1,70 +0,0 @@
----
-name: blogwatcher
-description: Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.
-homepage: https://github.com/Hyaxia/blogwatcher
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "📰",
-        "requires": { "bins": ["blogwatcher"] },
-        "install":
-          [
-            {
-              "id": "go",
-              "kind": "go",
-              "module": "github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest",
-              "bins": ["blogwatcher"],
-              "label": "Install blogwatcher (go)",
-            },
-          ],
-      },
-  }
-triggers: [blogwatcher]
----
-
-# 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/skills/blucli/SKILL.md

@@ -1,48 +0,0 @@
----
-name: blucli
-description: BluOS CLI (blu) for discovery, playback, grouping, and volume.
-homepage: https://blucli.sh
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "🫐",
-        "requires": { "bins": ["blu"] },
-        "install":
-          [
-            {
-              "id": "go",
-              "kind": "go",
-              "module": "github.com/steipete/blucli/cmd/blu@latest",
-              "bins": ["blu"],
-              "label": "Install blucli (go)",
-            },
-          ],
-      },
-  }
-triggers: [blucli]
----
-
-# 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/skills/bluebubbles/SKILL.md

@@ -1,132 +0,0 @@
----
-name: bluebubbles
-description: Use when you need to send or manage iMessages via BlueBubbles (recommended iMessage integration). Calls go through the generic message tool with channel="bluebubbles".
-metadata: { "symi": { "emoji": "🫧", "requires": { "config": ["channels.bluebubbles"] } } }
-triggers: [bluebubbles]
----
-
-# BlueBubbles Actions
-
-## Overview
-
-BlueBubbles is Symi’s recommended iMessage integration. Use the `message` tool with `channel: "bluebubbles"` to send messages and manage iMessage conversations: send texts and attachments, react (tapbacks), edit/unsend, reply in threads, and manage group participants/names/icons.
-
-## Inputs to collect
-
-- `target` (prefer `chat_guid:...`; also `+15551234567` in E.164 or `user@example.com`)
-- `message` text for send/edit/reply
-- `messageId` for react/edit/unsend/reply
-- Attachment `path` for local files, or `buffer` + `filename` for base64
-
-If the user is vague ("text my mom"), ask for the recipient handle or chat guid and the exact message content.
-
-## Actions
-
-### Send a message
-
-```json
-{
-  "action": "send",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "message": "hello from Symi"
-}
-```
-
-### React (tapback)
-
-```json
-{
-  "action": "react",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "messageId": "<message-guid>",
-  "emoji": "❤️"
-}
-```
-
-### Remove a reaction
-
-```json
-{
-  "action": "react",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "messageId": "<message-guid>",
-  "emoji": "❤️",
-  "remove": true
-}
-```
-
-### Edit a previously sent message
-
-```json
-{
-  "action": "edit",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "messageId": "<message-guid>",
-  "message": "updated text"
-}
-```
-
-### Unsend a message
-
-```json
-{
-  "action": "unsend",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "messageId": "<message-guid>"
-}
-```
-
-### Reply to a specific message
-
-```json
-{
-  "action": "reply",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "replyTo": "<message-guid>",
-  "message": "replying to that"
-}
-```
-
-### Send an attachment
-
-```json
-{
-  "action": "sendAttachment",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "path": "/tmp/photo.jpg",
-  "caption": "here you go"
-}
-```
-
-### Send with an iMessage effect
-
-```json
-{
-  "action": "sendWithEffect",
-  "channel": "bluebubbles",
-  "target": "+15551234567",
-  "message": "big news",
-  "effect": "balloons"
-}
-```
-
-## Notes
-
-- Requires gateway config `channels.bluebubbles` (serverUrl/password/webhookPath).
-- Prefer `chat_guid` targets when you have them (especially for group chats).
-- BlueBubbles supports rich actions, but some are macOS-version dependent (for example, edit may be broken on macOS 26 Tahoe).
-- The gateway may expose both short and full message ids; full ids are more durable across restarts.
-- Developer reference for the underlying plugin lives in `extensions/bluebubbles/README.md`.
-
-## Ideas to try
-
-- React with a tapback to acknowledge a request.
-- Reply in-thread when a user references a specific message.
-- Send a file attachment with a short caption.

package/skills/camsnap/SKILL.md

@@ -1,46 +0,0 @@
----
-name: camsnap
-description: Capture frames or clips from RTSP/ONVIF cameras.
-homepage: https://camsnap.ai
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "📸",
-        "requires": { "bins": ["camsnap"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "steipete/tap/camsnap",
-              "bins": ["camsnap"],
-              "label": "Install camsnap (brew)",
-            },
-          ],
-      },
-  }
-triggers: [camsnap]
----
-
-# camsnap
-
-Use `camsnap` to grab snapshots, clips, or motion events from configured cameras.
-
-Setup
-
-- Config file: `~/.config/camsnap/config.yaml`
-- Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass`
-
-Common commands
-
-- Discover: `camsnap discover --info`
-- Snapshot: `camsnap snap kitchen --out shot.jpg`
-- Clip: `camsnap clip kitchen --dur 5s --out clip.mp4`
-- Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'`
-- Doctor: `camsnap doctor --probe`
-
-Notes
-
-- Requires `ffmpeg` on PATH.
-- Prefer a short test capture before longer clips.

package/skills/canvas/SKILL.md

@@ -1,204 +0,0 @@
----
-name: canvas
-description: Display HTML content on connected Symi nodes (Mac app, iOS, Android). Use for games, visualizations, dashboards, generated HTML, and interactive demos.
-triggers: [canvas, display, html, visualize, dashboard, demo]
----
-
-# Canvas Skill
-
-Display HTML content on connected Symi nodes (Mac app, iOS, Android).
-
-## Overview
-
-The canvas tool lets you present web content on any connected node's canvas view. Great for:
-
-- Displaying games, visualizations, dashboards
-- Showing generated HTML content
-- Interactive demos
-
-## How It Works
-
-### Architecture
-
-```
-┌─────────────────┐     ┌──────────────────┐     ┌─────────────┐
-│  Canvas Host    │────▶│   Node Bridge    │────▶│  Node App   │
-│  (HTTP Server)  │     │  (TCP Server)    │     │ (Mac/iOS/   │
-│  Port 18793     │     │  Port 18790      │     │  Android)   │
-└─────────────────┘     └──────────────────┘     └─────────────┘
-```
-
-1. **Canvas Host Server**: Serves static HTML/CSS/JS files from `canvasHost.root` directory
-2. **Node Bridge**: Communicates canvas URLs to connected nodes
-3. **Node Apps**: Render the content in a WebView
-
-### Tailscale Integration
-
-The canvas host server binds based on `gateway.bind` setting:
-
-| Bind Mode  | Server Binds To     | Canvas URL Uses            |
-| ---------- | ------------------- | -------------------------- |
-| `loopback` | 127.0.0.1           | localhost (local only)     |
-| `lan`      | LAN interface       | LAN IP address             |
-| `tailnet`  | Tailscale interface | Tailscale hostname         |
-| `auto`     | Best available      | Tailscale > LAN > loopback |
-
-**Key insight:** The `canvasHostHostForBridge` is derived from `bridgeHost`. When bound to Tailscale, nodes receive URLs like:
-
-```
-http://<tailscale-hostname>:18793/__symi__/canvas/<file>.html
-```
-
-This is why localhost URLs don't work - the node receives the Tailscale hostname from the bridge!
-
-## Actions
-
-| Action     | Description                          |
-| ---------- | ------------------------------------ |
-| `present`  | Show canvas with optional target URL |
-| `hide`     | Hide the canvas                      |
-| `navigate` | Navigate to a new URL                |
-| `eval`     | Execute JavaScript in the canvas     |
-| `snapshot` | Capture screenshot of canvas         |
-
-## Configuration
-
-In `~/.symi/symi.json`:
-
-```json
-{
-  "canvasHost": {
-    "enabled": true,
-    "port": 18793,
-    "root": "/Users/you/symi/canvas",
-    "liveReload": true
-  },
-  "gateway": {
-    "bind": "auto"
-  }
-}
-```
-
-### Live Reload
-
-When `liveReload: true` (default), the canvas host:
-
-- Watches the root directory for changes (via chokidar)
-- Injects a WebSocket client into HTML files
-- Automatically reloads connected canvases when files change
-
-Great for development!
-
-## Workflow
-
-### 1. Create HTML content
-
-Place files in the canvas root directory (default `~/symi/canvas/`):
-
-```bash
-cat > ~/symi/canvas/my-game.html << 'HTML'
-<!DOCTYPE html>
-<html>
-<head><title>My Game</title></head>
-<body>
-  <h1>Hello Canvas!</h1>
-</body>
-</html>
-HTML
-```
-
-### 2. Find your canvas host URL
-
-Check how your gateway is bound:
-
-```bash
-cat ~/.symi/symi.json | jq '.gateway.bind'
-```
-
-Then construct the URL:
-
-- **loopback**: `http://127.0.0.1:18793/__symi__/canvas/<file>.html`
-- **lan/tailnet/auto**: `http://<hostname>:18793/__symi__/canvas/<file>.html`
-
-Find your Tailscale hostname:
-
-```bash
-tailscale status --json | jq -r '.Self.DNSName' | sed 's/\.$//'
-```
-
-### 3. Find connected nodes
-
-```bash
-symi nodes list
-```
-
-Look for Mac/iOS/Android nodes with canvas capability.
-
-### 4. Present content
-
-```
-canvas action:present node:<node-id> target:<full-url>
-```
-
-**Example:**
-
-```
-canvas action:present node:mac-63599bc4-b54d-4392-9048-b97abd58343a target:http://peters-mac-studio-1.sheep-coho.ts.net:18793/__symi__/canvas/snake.html
-```
-
-### 5. Navigate, snapshot, or hide
-
-```
-canvas action:navigate node:<node-id> url:<new-url>
-canvas action:snapshot node:<node-id>
-canvas action:hide node:<node-id>
-```
-
-## Debugging
-
-### White screen / content not loading
-
-**Cause:** URL mismatch between server bind and node expectation.
-
-**Debug steps:**
-
-1. Check server bind: `cat ~/.symi/symi.json | jq '.gateway.bind'`
-2. Check what port canvas is on: `lsof -i :18793`
-3. Test URL directly: `curl http://<hostname>:18793/__symi__/canvas/<file>.html`
-
-**Solution:** Use the full hostname matching your bind mode, not localhost.
-
-### "node required" error
-
-Always specify `node:<node-id>` parameter.
-
-### "node not connected" error
-
-Node is offline. Use `symi nodes list` to find online nodes.
-
-### Content not updating
-
-If live reload isn't working:
-
-1. Check `liveReload: true` in config
-2. Ensure file is in the canvas root directory
-3. Check for watcher errors in logs
-
-## URL Path Structure
-
-The canvas host serves from `/__symi__/canvas/` prefix:
-
-```
-http://<host>:18793/__symi__/canvas/index.html  → ~/symi/canvas/index.html
-http://<host>:18793/__symi__/canvas/games/snake.html → ~/symi/canvas/games/snake.html
-```
-
-The `/__symi__/canvas/` prefix is defined by `CANVAS_HOST_PATH` constant.
-
-## Tips
-
-- Keep HTML self-contained (inline CSS/JS) for best results
-- Use the default index.html as a test page (has bridge diagnostics)
-- The canvas persists until you `hide` it or navigate away
-- Live reload makes development fast - just save and it updates!
-- A2UI JSON push is WIP - use HTML files for now