@intent-systems/nexus 2026.1.5-3

package/skills/discord/SKILL.md

@@ -0,0 +1,370 @@
+---
+name: discord
+description: Use when you need to control Discord from Nexus via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
+metadata: {"nexus":{"type":"connector","provides":["chat-read","chat-send"],"requires":{"credentials":["discord"]}}}
+---
+
+# Discord Actions
+
+## Overview
+
+Use `discord` to manage messages, reactions, threads, polls, and moderation. You can disable groups via `discord.actions.*` (defaults to enabled, except roles/moderation). The tool uses the bot token configured for Nexus.
+
+## Inputs to collect
+
+- For reactions: `channelId`, `messageId`, and an `emoji`.
+- For stickers/polls/sendMessage: a `to` target (`channel:<id>` or `user:<id>`). Optional `content` text.
+- Polls also need a `question` plus 2–10 `answers`.
+- For media: `mediaUrl` with `file:///path` for local files or `https://...` for remote.
+- For emoji uploads: `guildId`, `name`, `mediaUrl`, optional `roleIds` (limit 256KB, PNG/JPG/GIF).
+- For sticker uploads: `guildId`, `name`, `description`, `tags`, `mediaUrl` (limit 512KB, PNG/APNG/Lottie JSON).
+
+Message context lines include `discord message id` and `channel` fields you can reuse directly.
+
+**Note:** `sendMessage` uses `to: "channel:<id>"` format, not `channelId`. Other actions like `react`, `readMessages`, `editMessage` use `channelId` directly.
+
+## Actions
+
+### React to a message
+
+```json
+{
+  "action": "react",
+  "channelId": "123",
+  "messageId": "456",
+  "emoji": "✅"
+}
+```
+
+### List reactions + users
+
+```json
+{
+  "action": "reactions",
+  "channelId": "123",
+  "messageId": "456",
+  "limit": 100
+}
+```
+
+### Send a sticker
+
+```json
+{
+  "action": "sticker",
+  "to": "channel:123",
+  "stickerIds": ["9876543210"],
+  "content": "Nice work!"
+}
+```
+
+- Up to 3 sticker IDs per message.
+- `to` can be `user:<id>` for DMs.
+
+### Upload a custom emoji
+
+```json
+{
+  "action": "emojiUpload",
+  "guildId": "999",
+  "name": "party_blob",
+  "mediaUrl": "file:///tmp/party.png",
+  "roleIds": ["222"]
+}
+```
+
+- Emoji images must be PNG/JPG/GIF and <= 256KB.
+- `roleIds` is optional; omit to make the emoji available to everyone.
+
+### Upload a sticker
+
+```json
+{
+  "action": "stickerUpload",
+  "guildId": "999",
+  "name": "nexus_wave",
+  "description": "Nexus waving hello",
+  "tags": "👋",
+  "mediaUrl": "file:///tmp/wave.png"
+}
+```
+
+- Stickers require `name`, `description`, and `tags`.
+- Uploads must be PNG/APNG/Lottie JSON and <= 512KB.
+
+### Create a poll
+
+```json
+{
+  "action": "poll",
+  "to": "channel:123",
+  "question": "Lunch?",
+  "answers": ["Pizza", "Sushi", "Salad"],
+  "allowMultiselect": false,
+  "durationHours": 24,
+  "content": "Vote now"
+}
+```
+
+- `durationHours` defaults to 24; max 32 days (768 hours).
+
+### Check bot permissions for a channel
+
+```json
+{
+  "action": "permissions",
+  "channelId": "123"
+}
+```
+
+## Ideas to try
+
+- React with ✅/⚠️ to mark status updates.
+- Post a quick poll for release decisions or meeting times.
+- Send celebratory stickers after successful deploys.
+- Upload new emojis/stickers for release moments.
+- Run weekly “priority check” polls in team channels.
+- DM stickers as acknowledgements when a user’s request is completed.
+
+## Action gating
+
+Use `discord.actions.*` to disable action groups:
+- `reactions` (react + reactions list + emojiList)
+- `stickers`, `polls`, `permissions`, `messages`, `threads`, `pins`, `search`
+- `emojiUploads`, `stickerUploads`
+- `memberInfo`, `roleInfo`, `channelInfo`, `voiceStatus`, `events`
+- `roles` (role add/remove, default `false`)
+- `moderation` (timeout/kick/ban, default `false`)
+### Read recent messages
+
+```json
+{
+  "action": "readMessages",
+  "channelId": "123",
+  "limit": 20
+}
+```
+
+### Send/edit/delete a message
+
+```json
+{
+  "action": "sendMessage",
+  "to": "channel:123",
+  "content": "Hello from Nexus"
+}
+```
+
+**With media attachment:**
+
+```json
+{
+  "action": "sendMessage",
+  "to": "channel:123",
+  "content": "Check out this audio!",
+  "mediaUrl": "file:///tmp/audio.mp3"
+}
+```
+
+- `to` uses format `channel:<id>` or `user:<id>` for DMs (not `channelId`!)
+- `mediaUrl` supports local files (`file:///path/to/file`) and remote URLs (`https://...`)
+- Optional `replyTo` with a message ID to reply to a specific message
+
+```json
+{
+  "action": "editMessage",
+  "channelId": "123",
+  "messageId": "456",
+  "content": "Fixed typo"
+}
+```
+
+```json
+{
+  "action": "deleteMessage",
+  "channelId": "123",
+  "messageId": "456"
+}
+```
+
+### Threads
+
+```json
+{
+  "action": "threadCreate",
+  "channelId": "123",
+  "name": "Bug triage",
+  "messageId": "456"
+}
+```
+
+```json
+{
+  "action": "threadList",
+  "guildId": "999"
+}
+```
+
+```json
+{
+  "action": "threadReply",
+  "channelId": "777",
+  "content": "Replying in thread"
+}
+```
+
+### Pins
+
+```json
+{
+  "action": "pinMessage",
+  "channelId": "123",
+  "messageId": "456"
+}
+```
+
+```json
+{
+  "action": "listPins",
+  "channelId": "123"
+}
+```
+
+### Search messages
+
+```json
+{
+  "action": "searchMessages",
+  "guildId": "999",
+  "content": "release notes",
+  "channelIds": ["123", "456"],
+  "limit": 10
+}
+```
+
+### Member + role info
+
+```json
+{
+  "action": "memberInfo",
+  "guildId": "999",
+  "userId": "111"
+}
+```
+
+```json
+{
+  "action": "roleInfo",
+  "guildId": "999"
+}
+```
+
+### List available custom emojis
+
+```json
+{
+  "action": "emojiList",
+  "guildId": "999"
+}
+```
+
+### Role changes (disabled by default)
+
+```json
+{
+  "action": "roleAdd",
+  "guildId": "999",
+  "userId": "111",
+  "roleId": "222"
+}
+```
+
+### Channel info
+
+```json
+{
+  "action": "channelInfo",
+  "channelId": "123"
+}
+```
+
+```json
+{
+  "action": "channelList",
+  "guildId": "999"
+}
+```
+
+### Voice status
+
+```json
+{
+  "action": "voiceStatus",
+  "guildId": "999",
+  "userId": "111"
+}
+```
+
+### Scheduled events
+
+```json
+{
+  "action": "eventList",
+  "guildId": "999"
+}
+```
+
+### Moderation (disabled by default)
+
+```json
+{
+  "action": "timeout",
+  "guildId": "999",
+  "userId": "111",
+  "durationMinutes": 10
+}
+```
+
+## Discord Writing Style Guide
+
+**Keep it conversational!** Discord is a chat platform, not documentation.
+
+### Do
+- Short, punchy messages (1-3 sentences ideal)
+- Multiple quick replies > one wall of text
+- Use emoji for tone/emphasis 🦞
+- Lowercase casual style is fine
+- Break up info into digestible chunks
+- Match the energy of the conversation
+
+### Don't
+- No markdown tables (Discord renders them as ugly raw `| text |`)
+- No `## Headers` for casual chat (use **bold** or CAPS for emphasis)
+- Avoid multi-paragraph essays
+- Don't over-explain simple things
+- Skip the "I'd be happy to help!" fluff
+
+### Formatting that works
+- **bold** for emphasis
+- `code` for technical terms
+- Lists for multiple items
+- > quotes for referencing
+- Wrap multiple links in `<>` to suppress embeds
+
+### Example transformations
+
+❌ Bad:
+```
+I'd be happy to help with that! Here's a comprehensive overview of the versioning strategies available:
+
+## Semantic Versioning
+Semver uses MAJOR.MINOR.PATCH format where...
+
+## Calendar Versioning
+CalVer uses date-based versions like...
+```
+
+✅ Good:
+```
+versioning options: semver (1.2.3), calver (2026.01.04), or yolo (`latest` forever). what fits your release cadence?
+```

package/skills/eightctl/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: eightctl
+description: Control Eight Sleep pods (status, temperature, alarms, schedules).
+homepage: https://eightctl.sh
+metadata: {"nexus":{"emoji":"🎛️","requires":{"bins":["eightctl"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/eightctl/cmd/eightctl@latest","bins":["eightctl"],"label":"Install eightctl (go)"}]}}
+---
+
+# eightctl
+
+Use `eightctl` for Eight Sleep pod control. Requires auth.
+
+Auth
+- Config: `~/.config/eightctl/config.yaml`
+- Env: `EIGHTCTL_EMAIL`, `EIGHTCTL_PASSWORD`
+
+Quick start
+- `eightctl status`
+- `eightctl on|off`
+- `eightctl temp 20`
+
+Common tasks
+- Alarms: `eightctl alarm list|create|dismiss`
+- Schedules: `eightctl schedule list|create|update`
+- Audio: `eightctl audio state|play|pause`
+- Base: `eightctl base info|angle`
+
+Notes
+- API is unofficial and rate-limited; avoid repeated logins.
+- Confirm before changing temperature or alarms.

package/skills/eve/SKILL.md

@@ -0,0 +1,215 @@
+---
+name: eve
+description: Query Eve's local iMessage database using raw SQL via the eve CLI
+homepage: https://github.com/Napageneral/eve
+metadata: {"nexus":{"emoji":"💬","type":"tool","provides":["messaging-read","personal-insights","relationship-insights"],"requires":{"bins":["eve"]},"install":[{"id":"brew","kind":"brew","formula":"Napageneral/tap/eve"},{"id":"go","kind":"go","module":"github.com/Napageneral/eve/cmd/eve@latest"}]}}
+---
+
+# Eve DB Skill
+
+Query Eve's local database (`eve.db`) directly using **raw SQL** via the `eve db query` command.
+
+## Docs
+
+- `docs/setup.md` (read + send setup)
+- `docs/intelligence.md` (Gemini-powered analysis)
+- `docs/dual-account.md` (agent identity / dual-account)
+- `docs/troubleshooting.md`
+- `scripts/setup-dual-account.sh`
+
+## Quick Start
+
+```bash
+# Initialize Eve (creates eve.db and queue.db)
+eve init
+
+# Sync messages from macOS Messages database
+eve sync
+
+# Query the database
+eve db query --sql "SELECT COUNT(*) AS c FROM messages"
+```
+
+## Where the DB lives
+
+- **Default path (macOS):** `~/Library/Application Support/Eve/eve.db`
+- **Override:** set `EVE_APP_DIR` (Eve will use `EVE_APP_DIR/eve.db`)
+
+## CLI Commands
+
+### Database Operations
+
+```bash
+# Query with raw SQL (read-only by default)
+eve db query --sql "SELECT * FROM chats LIMIT 5"
+
+# Allow write operations (use with caution)
+eve db query --sql "UPDATE ..." --write
+
+# Query the queue database
+eve db query --sql "SELECT * FROM jobs" --db queue
+
+# Query a specific database file
+eve db query --sql "SELECT * FROM messages" --db /path/to/other.db
+```
+
+### Sync Operations
+
+```bash
+# Dry run - see what would be synced
+eve sync --dry-run
+
+# Full sync from chat.db
+eve sync
+```
+
+### Utility Commands
+
+```bash
+# Show Eve paths
+eve paths
+
+# Who am I? (name/phones/emails)
+eve whoami
+
+# Show version
+eve version
+```
+
+## Core tables (iMessage domain)
+
+- **`contacts`**: resolved people (includes "Me" where `is_me=1`)
+- **`contact_identifiers`**: phone/email identifiers mapped to contacts
+- **`chats`**: conversation threads (one-on-one or group)
+- **`chat_participants`**: join table linking chats ↔ contacts
+- **`conversations`**: "conversation windows" inside a chat (90-minute gap heuristic)
+- **`messages`**: normalized messages
+- **`attachments`**: attachment metadata linked to `messages`
+- **`reactions`**: tapback/reaction rows
+
+## Common query patterns
+
+### List chats (most recent first)
+
+```sql
+SELECT
+  c.id,
+  c.chat_name,
+  c.is_group,
+  c.last_message_date,
+  c.total_messages
+FROM chats c
+ORDER BY c.last_message_date DESC
+LIMIT 50;
+```
+
+### Find chats by name (substring match)
+
+```sql
+SELECT id, chat_name, is_group
+FROM chats
+WHERE chat_name LIKE '%' || :q || '%'
+ORDER BY last_message_date DESC
+LIMIT 50;
+```
+
+(If you're using `eve db query`, inline the value instead of `:q`.)
+
+### Find contacts by name
+
+```sql
+SELECT id, name
+FROM contacts
+WHERE name LIKE '%' || :q || '%'
+ORDER BY name
+LIMIT 50;
+```
+
+### Get chats involving a contact (via participants join)
+
+```sql
+SELECT c.id, c.chat_name, c.last_message_date
+FROM chats c
+JOIN chat_participants cp ON cp.chat_id = c.id
+WHERE cp.contact_id = :contact_id
+ORDER BY c.last_message_date DESC
+LIMIT 50;
+```
+
+### Get most recent conversation for a chat
+
+```sql
+SELECT id, start_time, end_time, message_count
+FROM conversations
+WHERE chat_id = :chat_id
+ORDER BY end_time DESC
+LIMIT 1;
+```
+
+### Fetch messages for a conversation (for transcript building)
+
+```sql
+SELECT
+  m.timestamp,
+  COALESCE(ct.name, CASE WHEN m.is_from_me = 1 THEN 'Me' ELSE 'Unknown' END) AS sender_name,
+  m.is_from_me,
+  m.content
+FROM messages m
+LEFT JOIN contacts ct ON ct.id = m.sender_id
+WHERE m.conversation_id = :conversation_id
+ORDER BY m.timestamp ASC;
+```
+
+### Quick "search messages" (lexical substring; slow on huge DB)
+
+```sql
+SELECT m.id, m.chat_id, m.timestamp, m.content
+FROM messages m
+WHERE m.content LIKE '%' || :q || '%'
+ORDER BY m.timestamp DESC
+LIMIT 50;
+```
+
+## Live sync state (incremental ingestion)
+
+Watermarks live in `live_sync_state`:
+
+```sql
+SELECT key, value FROM live_sync_state;
+```
+
+Keys you'll see:
+- `last_message_rowid`
+- `last_attachment_rowid`
+- `apple_epoch_ns`
+
+## Optional: Context Engine server
+
+Eve also ships a TypeScript "Context Engine" server (HTTP) that provides:
+- `/engine/encode` – canonical encoding output for analysis/embeddings
+- `/engine/execute` – prompt + context-pack assembly with budget fitting
+
+This is **optional** for agents. It's mainly valuable for the **compute plane** (Celery) because it avoids spawning a new Bun process for every encode/execute call and caches the prompt/pack registry.
+
+## Installation
+
+### Via Homebrew (recommended)
+
+```bash
+brew install Napageneral/tap/eve
+```
+
+### Via Go Install
+
+```bash
+go install github.com/Napageneral/eve/cmd/eve@latest
+```
+
+### From Source
+
+```bash
+git clone https://github.com/Napageneral/eve.git
+cd eve
+make build
+# binary at ./bin/eve
+```

package/skills/eve/docs/dual-account.md

@@ -0,0 +1,84 @@
+# Eve Dual-Account (Agent Identity)
+
+This setup gives your agent its own iMessage identity on the same Mac.
+
+## Prerequisites
+
+- Admin access on the Mac
+- Separate Apple ID for the agent
+- Fast User Switching enabled
+- Remote Login (SSH) allowed
+
+## Step 1: Create an agent Apple ID (manual)
+
+Create a new Apple ID at https://appleid.apple.com/account.
+
+Use this address for the agent (example): `echo.nexus@icloud.com`.
+
+## Step 2: Create the agent macOS user (automated)
+
+Run the setup script from this skill:
+
+```bash
+bash scripts/setup-dual-account.sh "Echo"
+```
+
+The script:
+- Creates the `nexus-agent` user
+- Enables Fast User Switching
+- Sets up SSH keys and helper scripts
+- Creates `~/bin/eve-agent` and `~/bin/send-as-agent`
+- Disables sleep to keep the agent session active
+
+Save the generated password when prompted.
+
+## Step 3: Sign into Messages as the agent (manual)
+
+1. Switch to the `nexus-agent` user
+2. Open Messages.app and sign in with the agent Apple ID
+3. Grant Full Disk Access to the terminal app
+4. Switch back to your main user
+
+## Step 4: Ensure chat.db permissions
+
+After the agent has signed in:
+
+```bash
+sudo chmod 644 /Users/nexus-agent/Library/Messages/chat.db
+```
+
+## Using both accounts
+
+Read agent messages:
+
+```bash
+EVE_SOURCE_CHAT_DB=/Users/nexus-agent/Library/Messages/chat.db eve messages
+```
+
+Helper alias created by the script:
+
+```bash
+eve-agent messages
+```
+
+Send as the agent:
+
+```bash
+send-as-agent "+15551234567" "Hello from the agent"
+```
+
+## Verify the dual-account flow
+
+1. Text the agent Apple ID from your phone.
+2. Verify the message arrives:
+
+```bash
+EVE_SOURCE_CHAT_DB=/Users/nexus-agent/Library/Messages/chat.db eve messages --limit 1
+```
+
+3. Send a reply as the agent with `send-as-agent`.
+
+## Security notes
+
+- `chat.db` permissions are relaxed for cross-user reads; treat this as a sensitive machine.
+- SSH keys grant message-sending access; keep them local and protected.