@symerian/symi 3.0.17 → 3.0.19

package/extensions/thread-ownership/index.ts

@@ -1,133 +0,0 @@
-import type { SymiConfig, SymiPluginApi } from "symi/plugin-sdk";
-
-type ThreadOwnershipConfig = {
-  forwarderUrl?: string;
-  abTestChannels?: string[];
-};
-
-type AgentEntry = NonNullable<NonNullable<SymiConfig["agents"]>["list"]>[number];
-
-// In-memory set of {channel}:{thread} keys where this agent was @-mentioned.
-// Entries expire after 5 minutes.
-const mentionedThreads = new Map<string, number>();
-const MENTION_TTL_MS = 5 * 60 * 1000;
-
-function cleanExpiredMentions(): void {
-  const now = Date.now();
-  for (const [key, ts] of mentionedThreads) {
-    if (now - ts > MENTION_TTL_MS) {
-      mentionedThreads.delete(key);
-    }
-  }
-}
-
-function resolveOwnershipAgent(config: SymiConfig): { id: string; name: string } {
-  const list = Array.isArray(config.agents?.list)
-    ? config.agents.list.filter((entry): entry is AgentEntry =>
-        Boolean(entry && typeof entry === "object"),
-      )
-    : [];
-  const selected = list.find((entry) => entry.default === true) ?? list[0];
-
-  const id =
-    typeof selected?.id === "string" && selected.id.trim() ? selected.id.trim() : "unknown";
-  const identityName =
-    typeof selected?.identity?.name === "string" ? selected.identity.name.trim() : "";
-  const fallbackName = typeof selected?.name === "string" ? selected.name.trim() : "";
-  const name = identityName || fallbackName;
-
-  return { id, name };
-}
-
-export default function register(api: SymiPluginApi) {
-  const pluginCfg = (api.pluginConfig ?? {}) as ThreadOwnershipConfig;
-  const forwarderUrl = (
-    pluginCfg.forwarderUrl ??
-    process.env.SLACK_FORWARDER_URL ??
-    "http://slack-forwarder:8750"
-  ).replace(/\/$/, "");
-
-  const abTestChannels = new Set(
-    pluginCfg.abTestChannels ??
-      process.env.THREAD_OWNERSHIP_CHANNELS?.split(",").filter(Boolean) ??
-      [],
-  );
-
-  const { id: agentId, name: agentName } = resolveOwnershipAgent(api.config);
-  const botUserId = process.env.SLACK_BOT_USER_ID ?? "";
-
-  // ---------------------------------------------------------------------------
-  // message_received: track @-mentions so the agent can reply even if it
-  // doesn't own the thread.
-  // ---------------------------------------------------------------------------
-  api.on("message_received", async (event, ctx) => {
-    if (ctx.channelId !== "slack") return;
-
-    const text = event.content ?? "";
-    const threadTs = (event.metadata?.threadTs as string) ?? "";
-    const channelId = (event.metadata?.channelId as string) ?? ctx.conversationId ?? "";
-
-    if (!threadTs || !channelId) return;
-
-    // Check if this agent was @-mentioned.
-    const mentioned =
-      (agentName && text.includes(`@${agentName}`)) ||
-      (botUserId && text.includes(`<@${botUserId}>`));
-
-    if (mentioned) {
-      cleanExpiredMentions();
-      mentionedThreads.set(`${channelId}:${threadTs}`, Date.now());
-    }
-  });
-
-  // ---------------------------------------------------------------------------
-  // message_sending: check thread ownership before sending to Slack.
-  // Returns { cancel: true } if another agent owns the thread.
-  // ---------------------------------------------------------------------------
-  api.on("message_sending", async (event, ctx) => {
-    if (ctx.channelId !== "slack") return;
-
-    const threadTs = (event.metadata?.threadTs as string) ?? "";
-    const channelId = (event.metadata?.channelId as string) ?? event.to;
-
-    // Top-level messages (no thread) are always allowed.
-    if (!threadTs) return;
-
-    // Only enforce in A/B test channels (if set is empty, skip entirely).
-    if (abTestChannels.size > 0 && !abTestChannels.has(channelId)) return;
-
-    // If this agent was @-mentioned in this thread recently, skip ownership check.
-    cleanExpiredMentions();
-    if (mentionedThreads.has(`${channelId}:${threadTs}`)) return;
-
-    // Try to claim ownership via the forwarder HTTP API.
-    try {
-      const resp = await fetch(`${forwarderUrl}/api/v1/ownership/${channelId}/${threadTs}`, {
-        method: "POST",
-        headers: { "Content-Type": "application/json" },
-        body: JSON.stringify({ agent_id: agentId }),
-        signal: AbortSignal.timeout(3000),
-      });
-
-      if (resp.ok) {
-        // We own it (or just claimed it), proceed.
-        return;
-      }
-
-      if (resp.status === 409) {
-        // Another agent owns this thread — cancel the send.
-        const body = (await resp.json()) as { owner?: string };
-        api.logger.info?.(
-          `thread-ownership: cancelled send to ${channelId}:${threadTs} — owned by ${body.owner}`,
-        );
-        return { cancel: true };
-      }
-
-      // Unexpected status — fail open.
-      api.logger.warn?.(`thread-ownership: unexpected status ${resp.status}, allowing send`);
-    } catch (err) {
-      // Network error — fail open.
-      api.logger.warn?.(`thread-ownership: ownership check failed (${String(err)}), allowing send`);
-    }
-  });
-}

package/extensions/thread-ownership/symi.plugin.json

@@ -1,28 +0,0 @@
-{
-  "id": "thread-ownership",
-  "name": "Thread Ownership",
-  "description": "Prevents multiple agents from responding in the same Slack thread. Uses HTTP calls to the slack-forwarder ownership API.",
-  "configSchema": {
-    "type": "object",
-    "additionalProperties": false,
-    "properties": {
-      "forwarderUrl": {
-        "type": "string"
-      },
-      "abTestChannels": {
-        "type": "array",
-        "items": { "type": "string" }
-      }
-    }
-  },
-  "uiHints": {
-    "forwarderUrl": {
-      "label": "Forwarder URL",
-      "help": "Base URL of the slack-forwarder ownership API (default: http://slack-forwarder:8750)"
-    },
-    "abTestChannels": {
-      "label": "A/B Test Channels",
-      "help": "Slack channel IDs where thread ownership is enforced"
-    }
-  }
-}

package/skills/1password/SKILL.md

@@ -1,71 +0,0 @@
----
-name: 1password
-description: Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
-homepage: https://developer.1password.com/docs/cli/get-started/
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "🔐",
-        "requires": { "bins": ["op"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "1password-cli",
-              "bins": ["op"],
-              "label": "Install 1Password CLI (brew)",
-            },
-          ],
-      },
-  }
-triggers: [1password]
----
-
-# 1Password CLI
-
-Follow the official CLI get-started steps. Don't guess install commands.
-
-## References
-
-- `references/get-started.md` (install + app integration + sign-in flow)
-- `references/cli-examples.md` (real `op` examples)
-
-## Workflow
-
-1. Check OS + shell.
-2. Verify CLI present: `op --version`.
-3. Confirm desktop app integration is enabled (per get-started) and the app is unlocked.
-4. REQUIRED: create a fresh tmux session for all `op` commands (no direct `op` calls outside tmux).
-5. Sign in / authorize inside tmux: `op signin` (expect app prompt).
-6. Verify access inside tmux: `op whoami` (must succeed before any secret read).
-7. If multiple accounts: use `--account` or `OP_ACCOUNT`.
-
-## REQUIRED tmux session (T-Max)
-
-The shell tool uses a fresh TTY per command. To avoid re-prompts and failures, always run `op` inside a dedicated tmux session with a fresh socket/session name.
-
-Example (see `tmux` skill for socket conventions, do not reuse old session names):
-
-```bash
-SOCKET_DIR="${SYMI_TMUX_SOCKET_DIR:-${SYMI_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/symi-tmux-sockets}}"
-mkdir -p "$SOCKET_DIR"
-SOCKET="$SOCKET_DIR/symi-op.sock"
-SESSION="op-auth-$(date +%Y%m%d-%H%M%S)"
-
-tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
-tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Enter
-tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op whoami" Enter
-tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Enter
-tmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200
-tmux -S "$SOCKET" kill-session -t "$SESSION"
-```
-
-## Guardrails
-
-- Never paste secrets into logs, chat, or code.
-- Prefer `op run` / `op inject` over writing secrets to disk.
-- If sign-in without app integration is needed, use `op account add`.
-- If a command returns "account is not signed in", re-run `op signin` inside tmux and authorize in the app.
-- Do not run `op` outside tmux; stop and ask if tmux is unavailable.

package/skills/1password/references/cli-examples.md

@@ -1,29 +0,0 @@
-# op CLI examples (from op help)
-
-## Sign in
-
-- `op signin`
-- `op signin --account <shorthand|signin-address|account-id|user-id>`
-
-## Read
-
-- `op read op://app-prod/db/password`
-- `op read "op://app-prod/db/one-time password?attribute=otp"`
-- `op read "op://app-prod/ssh key/private key?ssh-format=openssh"`
-- `op read --out-file ./key.pem op://app-prod/server/ssh/key.pem`
-
-## Run
-
-- `export DB_PASSWORD="op://app-prod/db/password"`
-- `op run --no-masking -- printenv DB_PASSWORD`
-- `op run --env-file="./.env" -- printenv DB_PASSWORD`
-
-## Inject
-
-- `echo "db_password: {{ op://app-prod/db/password }}" | op inject`
-- `op inject -i config.yml.tpl -o config.yml`
-
-## Whoami / accounts
-
-- `op whoami`
-- `op account list`

package/skills/1password/references/get-started.md

@@ -1,17 +0,0 @@
-# 1Password CLI get-started (summary)
-
-- Works on macOS, Windows, and Linux.
-  - macOS/Linux shells: bash, zsh, sh, fish.
-  - Windows shell: PowerShell.
-- Requires a 1Password subscription and the desktop app to use app integration.
-- macOS requirement: Big Sur 11.0.0 or later.
-- Linux app integration requires PolKit + an auth agent.
-- Install the CLI per the official doc for your OS.
-- Enable desktop app integration in the 1Password app:
-  - Open and unlock the app, then select your account/collection.
-  - macOS: Settings > Developer > Integrate with 1Password CLI (Touch ID optional).
-  - Windows: turn on Windows Hello, then Settings > Developer > Integrate.
-  - Linux: Settings > Security > Unlock using system authentication, then Settings > Developer > Integrate.
-- After integration, run any command to sign in (example in docs: `op vault list`).
-- If multiple accounts: use `op signin` to pick one, or `--account` / `OP_ACCOUNT`.
-- For non-integration auth, use `op account add`.

package/skills/apple-notes/SKILL.md

@@ -1,78 +0,0 @@
----
-name: apple-notes
-description: Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Symi to add a note, list notes, search notes, or manage note folders.
-homepage: https://github.com/antoniorodr/memo
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "📝",
-        "os": ["darwin"],
-        "requires": { "bins": ["memo"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "antoniorodr/memo/memo",
-              "bins": ["memo"],
-              "label": "Install memo via Homebrew",
-            },
-          ],
-      },
-  }
-triggers: [apple-notes, apple, notes]
----
-
-# Apple Notes CLI
-
-Use `memo notes` to manage Apple Notes directly from the terminal. Create, view, edit, delete, search, move notes between folders, and export to HTML/Markdown.
-
-Setup
-
-- Install (Homebrew): `brew tap antoniorodr/memo && brew install antoniorodr/memo/memo`
-- Manual (pip): `pip install .` (after cloning the repo)
-- macOS-only; if prompted, grant Automation access to Notes.app.
-
-View Notes
-
-- List all notes: `memo notes`
-- Filter by folder: `memo notes -f "Folder Name"`
-- Search notes (fuzzy): `memo notes -s "query"`
-
-Create Notes
-
-- Add a new note: `memo notes -a`
-  - Opens an interactive editor to compose the note.
-- Quick add with title: `memo notes -a "Note Title"`
-
-Edit Notes
-
-- Edit existing note: `memo notes -e`
-  - Interactive selection of note to edit.
-
-Delete Notes
-
-- Delete a note: `memo notes -d`
-  - Interactive selection of note to delete.
-
-Move Notes
-
-- Move note to folder: `memo notes -m`
-  - Interactive selection of note and destination folder.
-
-Export Notes
-
-- Export to HTML/Markdown: `memo notes -ex`
-  - Exports selected note; uses Mistune for markdown processing.
-
-Limitations
-
-- Cannot edit notes containing images or attachments.
-- Interactive prompts may require terminal access.
-
-Notes
-
-- macOS-only.
-- Requires Apple Notes.app to be accessible.
-- For automation, grant permissions in System Settings > Privacy & Security > Automation.

package/skills/apple-reminders/SKILL.md

@@ -1,119 +0,0 @@
----
-name: apple-reminders
-description: Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
-homepage: https://github.com/steipete/remindctl
-metadata:
-  {
-    "symi":
-      {
-        "emoji": "⏰",
-        "os": ["darwin"],
-        "requires": { "bins": ["remindctl"] },
-        "install":
-          [
-            {
-              "id": "brew",
-              "kind": "brew",
-              "formula": "steipete/tap/remindctl",
-              "bins": ["remindctl"],
-              "label": "Install remindctl via Homebrew",
-            },
-          ],
-      },
-  }
-triggers: [apple-reminders, apple, reminders]
----
-
-# Apple Reminders CLI (remindctl)
-
-Use `remindctl` to manage Apple Reminders directly from the terminal.
-
-## When to Use
-
-✅ **USE this skill when:**
-
-- User explicitly mentions "reminder" or "Reminders app"
-- Creating personal to-dos with due dates that sync to iOS
-- Managing Apple Reminders lists
-- User wants tasks to appear in their iPhone/iPad Reminders app
-
-## When NOT to Use
-
-❌ **DON'T use this skill when:**
-
-- Scheduling Symi tasks or alerts → use `cron` tool with systemEvent instead
-- Calendar events or appointments → use Apple Calendar
-- Project/work task management → use Notion, GitHub Issues, or task queue
-- One-time notifications → use `cron` tool for timed alerts
-- User says "remind me" but means a Symi alert → clarify first
-
-## Setup
-
-- Install: `brew install steipete/tap/remindctl`
-- macOS-only; grant Reminders permission when prompted
-- Check status: `remindctl status`
-- Request access: `remindctl authorize`
-
-## Common Commands
-
-### View Reminders
-
-```bash
-remindctl                    # Today's reminders
-remindctl today              # Today
-remindctl tomorrow           # Tomorrow
-remindctl week               # This week
-remindctl overdue            # Past due
-remindctl all                # Everything
-remindctl 2026-01-04         # Specific date
-```
-
-### Manage Lists
-
-```bash
-remindctl list               # List all lists
-remindctl list Work          # Show specific list
-remindctl list Projects --create    # Create list
-remindctl list Work --delete        # Delete list
-```
-
-### Create Reminders
-
-```bash
-remindctl add "Buy milk"
-remindctl add --title "Call mom" --list Personal --due tomorrow
-remindctl add --title "Meeting prep" --due "2026-02-15 09:00"
-```
-
-### Complete/Delete
-
-```bash
-remindctl complete 1 2 3     # Complete by ID
-remindctl delete 4A83 --force  # Delete by ID
-```
-
-### Output Formats
-
-```bash
-remindctl today --json       # JSON for scripting
-remindctl today --plain      # TSV format
-remindctl today --quiet      # Counts only
-```
-
-## Date Formats
-
-Accepted by `--due` and date filters:
-
-- `today`, `tomorrow`, `yesterday`
-- `YYYY-MM-DD`
-- `YYYY-MM-DD HH:mm`
-- ISO 8601 (`2026-01-04T12:34:56Z`)
-
-## Example: Clarifying User Intent
-
-User: "Remind me to check on the deploy in 2 hours"
-
-**Ask:** "Do you want this in Apple Reminders (syncs to your phone) or as a Symi alert (I'll message you here)?"
-
-- Apple Reminders → use this skill
-- Symi alert → use `cron` tool with systemEvent

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.