cowork-os 0.3.21

package/package.json

@@ -0,0 +1,159 @@
+{
+  "name": "cowork-os",
+  "version": "0.3.21",
+  "description": "CoWork OS - The operating system for personal AI assistants",
+  "overrides": {
+    "undici": "^7.0.0"
+  },
+  "main": "dist/electron/electron/main.js",
+  "author": "CoWork OS Contributors",
+  "license": "MIT",
+  "homepage": "https://github.com/CoWork-OS/CoWork-OS#readme",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/CoWork-OS/CoWork-OS.git"
+  },
+  "bugs": {
+    "url": "https://github.com/CoWork-OS/CoWork-OS/issues"
+  },
+  "keywords": [
+    "ai-assistant",
+    "personal-ai",
+    "self-hosted",
+    "ai-gateway",
+    "whatsapp-bot",
+    "telegram-bot",
+    "discord-bot",
+    "slack-bot",
+    "ai-automation",
+    "llm",
+    "claude",
+    "gpt",
+    "gemini",
+    "ollama",
+    "mcp",
+    "electron",
+    "macos",
+    "security",
+    "local-first",
+    "byok"
+  ],
+  "private": false,
+  "scripts": {
+    "postinstall": "electron-rebuild -f -w better-sqlite3",
+    "dev": "concurrently \"npm run dev:react\" \"npm run dev:electron\"",
+    "dev:react": "vite",
+    "dev:electron": "tsc -p tsconfig.electron.json && cross-env NODE_ENV=development electron .",
+    "build": "npm run build:react && npm run build:electron",
+    "build:react": "vite build",
+    "build:electron": "tsc -p tsconfig.electron.json",
+    "package": "npm run build && electron-builder",
+    "lint": "eslint src --ext ts,tsx",
+    "type-check": "tsc --noEmit",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "test:coverage": "vitest run --coverage"
+  },
+  "dependencies": {
+    "@anthropic-ai/sdk": "^0.72.1",
+    "@aws-sdk/client-bedrock": "^3.980.0",
+    "@aws-sdk/client-bedrock-runtime": "^3.980.0",
+    "@google/generative-ai": "^0.24.1",
+    "@grammyjs/runner": "^2.0.3",
+    "@grammyjs/transformer-throttler": "^1.2.1",
+    "@mariozechner/pi-ai": "^0.51.0",
+    "@slack/bolt": "^4.6.0",
+    "@types/jszip": "^3.4.1",
+    "@whiskeysockets/baileys": "^6.7.16",
+    "better-sqlite3": "^12.6.2",
+    "botbuilder": "^4.23.3",
+    "chokidar": "^5.0.0",
+    "discord.js": "^14.25.1",
+    "docx": "^9.5.1",
+    "electron-updater": "^6.3.9",
+    "eventsource": "^4.1.0",
+    "exceljs": "^4.4.0",
+    "grammy": "^1.39.3",
+    "jszip": "^3.10.1",
+    "mammoth": "^1.11.0",
+    "mime-types": "^3.0.2",
+    "openai": "^6.17.0",
+    "pdf-parse": "^2.4.5",
+    "pdfkit": "^0.17.2",
+    "playwright": "^1.58.1",
+    "pptxgenjs": "^4.0.1",
+    "qrcode": "^1.5.4",
+    "qrcode-terminal": "^0.12.0",
+    "react": "^19.2.4",
+    "react-dom": "^19.2.4",
+    "react-markdown": "^10.1.0",
+    "remark-breaks": "^4.0.0",
+    "remark-gfm": "^4.0.1",
+    "uuid": "^13.0.0",
+    "ws": "^8.18.0",
+    "zod": "^4.3.6"
+  },
+  "devDependencies": {
+    "@electron/rebuild": "^4.0.3",
+    "@types/better-sqlite3": "^7.6.8",
+    "@types/mime-types": "^3.0.1",
+    "@types/node": "^25.2.0",
+    "@types/pdf-parse": "^1.1.5",
+    "@types/pdfkit": "^0.17.4",
+    "@types/qrcode": "^1.5.5",
+    "@types/react": "^19.2.10",
+    "@types/react-dom": "^19.2.3",
+    "@types/ws": "^8.5.13",
+    "@typescript-eslint/eslint-plugin": "^8.54.0",
+    "@typescript-eslint/parser": "^8.53.1",
+    "@vitejs/plugin-react": "^5.1.2",
+    "@vitest/coverage-v8": "^4.0.18",
+    "concurrently": "^9.2.1",
+    "cross-env": "^10.1.0",
+    "electron": "^40.1.0",
+    "electron-builder": "^26.7.0",
+    "electron-rebuild": "^3.2.9",
+    "eslint": "^9.39.2",
+    "globals": "^17.3.0",
+    "typescript": "^5.7.3",
+    "vite": "^7.3.1",
+    "vite-plugin-electron": "^0.29.0",
+    "vitest": "^4.0.18"
+  },
+  "build": {
+    "appId": "com.cowork-os.app",
+    "productName": "CoWork OS",
+    "directories": {
+      "output": "release"
+    },
+    "files": [
+      "dist/**/*",
+      "package.json"
+    ],
+    "extraResources": [
+      {
+        "from": "resources/skills",
+        "to": "skills",
+        "filter": [
+          "**/*.json"
+        ]
+      }
+    ],
+    "mac": {
+      "target": [
+        "dmg",
+        "zip"
+      ],
+      "category": "public.app-category.productivity",
+      "hardenedRuntime": true,
+      "gatekeeperAssess": false,
+      "entitlements": "build/entitlements.mac.plist",
+      "entitlementsInherit": "build/entitlements.mac.plist"
+    },
+    "publish": {
+      "provider": "github",
+      "owner": "CoWork-OS",
+      "repo": "CoWork-OS"
+    }
+  }
+}

package/resources/skills/1password.json

@@ -0,0 +1,10 @@
+{
+  "id": "1password",
+  "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.",
+  "icon": "🔐",
+  "category": "Tools",
+  "prompt": "# 1Password CLI\n\nFollow the official CLI get-started steps. Don't guess install commands.\n\n## References\n\n- `references/get-started.md` (install + app integration + sign-in flow)\n- `references/cli-examples.md` (real `op` examples)\n\n## Workflow\n\n1. Check OS + shell.\n2. Verify CLI present: `op --version`.\n3. Confirm desktop app integration is enabled (per get-started) and the app is unlocked.\n4. REQUIRED: create a fresh tmux session for all `op` commands (no direct `op` calls outside tmux).\n5. Sign in / authorize inside tmux: `op signin` (expect app prompt).\n6. Verify access inside tmux: `op whoami` (must succeed before any secret read).\n7. If multiple accounts: use `--account` or `OP_ACCOUNT`.\n\n## REQUIRED tmux session (T-Max)\n\nThe 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.\n\nExample (see `tmux` skill for socket conventions, do not reuse old session names):\n\n```bash\nSOCKET_DIR=\"${CoWork-OSS_TMUX_SOCKET_DIR:-${CoWork-OSSBOT_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/CoWork-OSS-tmux-sockets}}\"\nmkdir -p \"$SOCKET_DIR\"\nSOCKET=\"$SOCKET_DIR/CoWork-OSS-op.sock\"\nSESSION=\"op-auth-$(date +%Y%m%d-%H%M%S)\"\n\ntmux -S \"$SOCKET\" new -d -s \"$SESSION\" -n shell\ntmux -S \"$SOCKET\" send-keys -t \"$SESSION\":0.0 -- \"op signin --account my.1password.com\" Enter\ntmux -S \"$SOCKET\" send-keys -t \"$SESSION\":0.0 -- \"op whoami\" Enter\ntmux -S \"$SOCKET\" send-keys -t \"$SESSION\":0.0 -- \"op vault list\" Enter\ntmux -S \"$SOCKET\" capture-pane -p -J -t \"$SESSION\":0.0 -S -200\ntmux -S \"$SOCKET\" kill-session -t \"$SESSION\"\n```\n\n## Guardrails\n\n- Never paste secrets into logs, chat, or code.\n- Prefer `op run` / `op inject` over writing secrets to disk.\n- If sign-in without app integration is needed, use `op account add`.\n- If a command returns \"account is not signed in\", re-run `op signin` inside tmux and authorize in the app.\n- Do not run `op` outside tmux; stop and ask if tmux is unavailable.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/add-documentation.json

@@ -0,0 +1,31 @@
+{
+  "id": "add-documentation",
+  "name": "Add Documentation",
+  "description": "Generate JSDoc/docstrings for functions",
+  "icon": "📚",
+  "category": "Development",
+  "prompt": "Please add documentation to all functions in {{path}}.\n\nRequirements:\n- Use {{style}} documentation style\n- Document all parameters with types\n- Document return values\n- Add brief description of what each function does\n- Include @example where helpful\n- Note any side effects or exceptions\n\nPreserve existing documentation if it's accurate, enhance if needed.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the file to document",
+      "required": true
+    },
+    {
+      "name": "style",
+      "type": "select",
+      "description": "Documentation style",
+      "required": true,
+      "default": "JSDoc",
+      "options": [
+        "JSDoc",
+        "TSDoc",
+        "Python docstring",
+        "Javadoc",
+        "XML comments"
+      ]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/analyze-csv.json

@@ -0,0 +1,17 @@
+{
+  "id": "analyze-csv",
+  "name": "Analyze CSV",
+  "description": "Load a CSV and provide insights",
+  "icon": "📊",
+  "category": "Data",
+  "prompt": "Please analyze the CSV file at {{path}}.\n\nProvide:\n1. **Overview**: Number of rows, columns, file size\n2. **Columns**: List each column with data type and sample values\n3. **Statistics**: For numeric columns - min, max, mean, median\n4. **Missing Data**: Identify columns with null/empty values\n5. **Patterns**: Any notable patterns or anomalies\n6. **Insights**: Key findings and observations\n\nIf the file is large, analyze a representative sample.\nCreate visualizations or summary tables if helpful.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the CSV file",
+      "required": true
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/apple-notes.json

@@ -0,0 +1,10 @@
+{
+  "id": "apple-notes",
+  "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 CoWork-OSS to add a note, list notes, search notes, or manage note folders.",
+  "icon": "📝",
+  "category": "Tools",
+  "prompt": "# Apple Notes CLI\n\nUse `memo notes` to manage Apple Notes directly from the terminal. Create, view, edit, delete, search, move notes between folders, and export to HTML/Markdown.\n\nSetup\n\n- Install (Homebrew): `brew tap antoniorodr/memo && brew install antoniorodr/memo/memo`\n- Manual (pip): `pip install .` (after cloning the repo)\n- macOS-only; if prompted, grant Automation access to Notes.app.\n\nView Notes\n\n- List all notes: `memo notes`\n- Filter by folder: `memo notes -f \"Folder Name\"`\n- Search notes (fuzzy): `memo notes -s \"query\"`\n\nCreate Notes\n\n- Add a new note: `memo notes -a`\n  - Opens an interactive editor to compose the note.\n- Quick add with title: `memo notes -a \"Note Title\"`\n\nEdit Notes\n\n- Edit existing note: `memo notes -e`\n  - Interactive selection of note to edit.\n\nDelete Notes\n\n- Delete a note: `memo notes -d`\n  - Interactive selection of note to delete.\n\nMove Notes\n\n- Move note to folder: `memo notes -m`\n  - Interactive selection of note and destination folder.\n\nExport Notes\n\n- Export to HTML/Markdown: `memo notes -ex`\n  - Exports selected note; uses Mistune for markdown processing.\n\nLimitations\n\n- Cannot edit notes containing images or attachments.\n- Interactive prompts may require terminal access.\n\nNotes\n\n- macOS-only.\n- Requires Apple Notes.app to be accessible.\n- For automation, grant permissions in System Settings > Privacy & Security > Automation.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/apple-reminders.json

@@ -0,0 +1,10 @@
+{
+  "id": "apple-reminders",
+  "name": "Apple-reminders",
+  "description": "Manage Apple Reminders via the `remindctl` CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.",
+  "icon": "⏰",
+  "category": "Tools",
+  "prompt": "# Apple Reminders CLI (remindctl)\n\nUse `remindctl` to manage Apple Reminders directly from the terminal. It supports list filtering, date-based views, and scripting output.\n\nSetup\n\n- Install (Homebrew): `brew install steipete/tap/remindctl`\n- From source: `pnpm install && pnpm build` (binary at `./bin/remindctl`)\n- macOS-only; grant Reminders permission when prompted.\n\nPermissions\n\n- Check status: `remindctl status`\n- Request access: `remindctl authorize`\n\nView Reminders\n\n- Default (today): `remindctl`\n- Today: `remindctl today`\n- Tomorrow: `remindctl tomorrow`\n- Week: `remindctl week`\n- Overdue: `remindctl overdue`\n- Upcoming: `remindctl upcoming`\n- Completed: `remindctl completed`\n- All: `remindctl all`\n- Specific date: `remindctl 2026-01-04`\n\nManage Lists\n\n- List all lists: `remindctl list`\n- Show list: `remindctl list Work`\n- Create list: `remindctl list Projects --create`\n- Rename list: `remindctl list Work --rename Office`\n- Delete list: `remindctl list Work --delete`\n\nCreate Reminders\n\n- Quick add: `remindctl add \"Buy milk\"`\n- With list + due: `remindctl add --title \"Call mom\" --list Personal --due tomorrow`\n\nEdit Reminders\n\n- Edit title/due: `remindctl edit 1 --title \"New title\" --due 2026-01-04`\n\nComplete Reminders\n\n- Complete by id: `remindctl complete 1 2 3`\n\nDelete Reminders\n\n- Delete by id: `remindctl delete 4A83 --force`\n\nOutput Formats\n\n- JSON (scripting): `remindctl today --json`\n- Plain TSV: `remindctl today --plain`\n- Counts only: `remindctl today --quiet`\n\nDate Formats\nAccepted by `--due` and date filters:\n\n- `today`, `tomorrow`, `yesterday`\n- `YYYY-MM-DD`\n- `YYYY-MM-DD HH:mm`\n- ISO 8601 (`2026-01-04T12:34:56Z`)\n\nNotes\n\n- macOS-only.\n- If access is denied, enable Terminal/remindctl in System Settings → Privacy & Security → Reminders.\n- If running over SSH, grant access on the Mac that runs the command.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/auto-commenter.json

@@ -0,0 +1,10 @@
+{
+  "id": "auto-commenter",
+  "name": "Auto Commenter",
+  "description": "Generate authentic, personalized comments for Reddit and other online communities. Uses your writing style to create human-like engagement that builds community presence and identifies potential leads.",
+  "icon": "💬",
+  "category": "Marketing",
+  "prompt": "# Auto Commenter - Community Engagement Assistant\n\n## Overview\n\nYou are an authentic community engagement assistant that helps craft personalized, valuable comments for online platforms (Reddit, Twitter, LinkedIn, Discord). Your goal is to generate comments that feel genuinely human-written while providing real value to discussions.\n\n## Core Principles\n\n1. **Authenticity First**: Every comment must add genuine value to the conversation\n2. **Style Matching**: Adapt to the user's natural writing voice\n3. **Platform Awareness**: Respect community rules and culture\n4. **No Spam**: Quality over quantity - never post low-effort or generic responses\n\n## 16-Point Authenticity Checklist\n\nBefore finalizing any comment, verify:\n\n1. Does it directly address the post's main point?\n2. Does it add new information or perspective?\n3. Is it written conversationally (not corporate/robotic)?\n4. Does it match the user's established voice?\n5. Is the length appropriate for the platform?\n6. Does it avoid marketing buzzwords?\n7. Is it contextually relevant to the subreddit/community?\n8. Does it feel like a real person wrote it?\n9. Would you engage with this comment if you saw it?\n10. Does it respect community guidelines?\n11. Is it free of excessive emoji or formatting?\n12. Does it avoid direct product pitches?\n13. Could it spark meaningful discussion?\n14. Is the tone appropriate for the thread mood?\n15. Does it demonstrate genuine expertise/interest?\n16. Would the OP find this helpful?\n\n## Workflow\n\n### Step 1: Style Learning\n\nAsk the user to provide 5-10 of their existing comments to learn their voice:\n- Sentence structure preferences\n- Common phrases and expressions\n- Humor style (if any)\n- Technical depth level\n- Emoji/formatting habits\n\n### Step 2: Target Analysis\n\nFor each target community:\n- Research subreddit/community rules\n- Identify posting patterns and culture\n- Note what types of comments get engagement\n- Understand the audience demographics\n\n### Step 3: Post Evaluation\n\nWhen analyzing a post to comment on:\n- Summarize the main discussion point\n- Identify what kind of response would be valuable\n- Check if the topic aligns with expertise areas\n- Determine appropriate response depth\n\n### Step 4: Comment Generation\n\nGenerate comments that:\n- Lead with value (answer a question, share insight)\n- Use natural, conversational language\n- Include specific details when relevant\n- End with engagement hooks (questions, invitations to discuss)\n\n### Step 5: Lead Identification\n\nFlag potential leads when users:\n- Express pain points your product solves\n- Ask for tool/solution recommendations\n- Discuss budget or purchasing decisions\n- Show intent signals in their language\n\n## Output Format\n\nFor each generated comment, provide:\n\n```\n**Target**: [Subreddit/Community name]\n**Post**: [Brief summary]\n**Comment**:\n[The generated comment]\n\n**Authenticity Score**: [X/16 checks passed]\n**Lead Potential**: [None/Low/Medium/High]\n**Notes**: [Any relevant observations]\n```\n\n## Batch Mode\n\nFor batch operations, organize by:\n1. Group comments by community\n2. Vary posting times naturally\n3. Mix comment lengths and styles\n4. Track daily quotas per platform\n\n## Activity Logging\n\nMaintain logs including:\n- Timestamp\n- Platform and community\n- Post link\n- Comment text\n- Lead flagged (yes/no)\n- Engagement metrics (when available)\n\n## Best Practices\n\n- **Mix automated with manual**: Don't rely 100% on generated comments\n- **Respond to replies**: Engage with people who respond to your comments\n- **Stay topical**: Only comment where you have genuine expertise\n- **Respect rate limits**: Don't flood communities with comments\n- **Evolve your style**: Update voice samples periodically\n\n## Commands\n\n- `analyze style [comments]` - Learn from provided comment examples\n- `scout [subreddit]` - Research a community's culture and rules\n- `generate [post_url]` - Create a comment for a specific post\n- `batch [subreddit] [count]` - Generate multiple comments for a community\n- `review leads` - Show flagged potential leads\n- `log today` - Show today's commenting activity\n\n## Ethical Guidelines\n\n- Always disclose if asked if you're using AI assistance\n- Never impersonate other users or spread misinformation\n- Respect community bans and restrictions\n- Don't manipulate votes or engagement metrics\n- Prioritize genuine helpfulness over promotional goals",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/bear-notes.json

@@ -0,0 +1,10 @@
+{
+  "id": "bear-notes",
+  "name": "Bear-notes",
+  "description": "Create, search, and manage Bear notes via grizzly CLI.",
+  "icon": "🐻",
+  "category": "Tools",
+  "prompt": "# Bear Notes\n\nUse `grizzly` to create, read, and manage notes in Bear on macOS.\n\nRequirements\n\n- Bear app installed and running\n- For some operations (add-text, tags, open-note --selected), a Bear app token (stored in `~/.config/grizzly/token`)\n\n## Getting a Bear Token\n\nFor operations that require a token (add-text, tags, open-note --selected), you need an authentication token:\n\n1. Open Bear → Help → API Token → Copy Token\n2. Save it: `echo \"YOUR_TOKEN\" > ~/.config/grizzly/token`\n\n## Common Commands\n\nCreate a note\n\n```bash\necho \"Note content here\" | grizzly create --title \"My Note\" --tag work\ngrizzly create --title \"Quick Note\" --tag inbox < /dev/null\n```\n\nOpen/read a note by ID\n\n```bash\ngrizzly open-note --id \"NOTE_ID\" --enable-callback --json\n```\n\nAppend text to a note\n\n```bash\necho \"Additional content\" | grizzly add-text --id \"NOTE_ID\" --mode append --token-file ~/.config/grizzly/token\n```\n\nList all tags\n\n```bash\ngrizzly tags --enable-callback --json --token-file ~/.config/grizzly/token\n```\n\nSearch notes (via open-tag)\n\n```bash\ngrizzly open-tag --name \"work\" --enable-callback --json\n```\n\n## Options\n\nCommon flags:\n\n- `--dry-run` — Preview the URL without executing\n- `--print-url` — Show the x-callback-url\n- `--enable-callback` — Wait for Bear's response (needed for reading data)\n- `--json` — Output as JSON (when using callbacks)\n- `--token-file PATH` — Path to Bear API token file\n\n## Configuration\n\nGrizzly reads config from (in priority order):\n\n1. CLI flags\n2. Environment variables (`GRIZZLY_TOKEN_FILE`, `GRIZZLY_CALLBACK_URL`, `GRIZZLY_TIMEOUT`)\n3. `.grizzly.toml` in current directory\n4. `~/.config/grizzly/config.toml`\n\nExample `~/.config/grizzly/config.toml`:\n\n```toml\ntoken_file = \"~/.config/grizzly/token\"\ncallback_url = \"http://127.0.0.1:42123/success\"\ntimeout = \"5s\"\n```\n\n## Notes\n\n- Bear must be running for commands to work\n- Note IDs are Bear's internal identifiers (visible in note info or via callbacks)\n- Use `--enable-callback` when you need to read data back from Bear\n- Some operations require a valid token (add-text, tags, open-note --selected)",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/bird.json

@@ -0,0 +1,35 @@
+{
+  "id": "bird",
+  "name": "Bird",
+  "description": "X/Twitter CLI for reading, searching, posting, and engagement via cookies.",
+  "icon": "🐦",
+  "category": "Tools",
+  "prompt": "# bird 🐦\n\nFast X/Twitter CLI using GraphQL + cookie auth.\n\n## Install\n\n```bash\n# npm/pnpm/bun\nnpm install -g @steipete/bird\n\n# Homebrew (macOS, prebuilt binary)\nbrew install steipete/tap/bird\n\n# One-shot (no install)\nbunx @steipete/bird whoami\n```\n\n## Authentication\n\n`bird` uses cookie-based auth.\n\nUse `--auth-token` / `--ct0` to pass cookies directly, or `--cookie-source` for browser cookies.\n\nRun `bird check` to see which source is active. For Arc/Brave, use `--chrome-profile-dir <path>`.\n\n## Commands\n\n### Account & Auth\n\n```bash\nbird whoami                    # Show logged-in account\nbird check                     # Show credential sources\nbird query-ids --fresh         # Refresh GraphQL query ID cache\n```\n\n### Reading Tweets\n\n```bash\nbird read <url-or-id>          # Read a single tweet\nbird <url-or-id>               # Shorthand for read\nbird thread <url-or-id>        # Full conversation thread\nbird replies <url-or-id>       # List replies to a tweet\n```\n\n### Timelines\n\n```bash\nbird home                      # Home timeline (For You)\nbird home --following          # Following timeline\nbird user-tweets @handle -n 20 # User's profile timeline\nbird mentions                  # Tweets mentioning you\nbird mentions --user @handle   # Mentions of another user\n```\n\n### Search\n\n```bash\nbird search \"query\" -n 10\nbird search \"from:steipete\" --all --max-pages 3\n```\n\n### News & Trending\n\n```bash\nbird news -n 10                # AI-curated from Explore tabs\nbird news --ai-only            # Filter to AI-curated only\nbird news --sports             # Sports tab\nbird news --with-tweets        # Include related tweets\nbird trending                  # Alias for news\n```\n\n### Lists\n\n```bash\nbird lists                     # Your lists\nbird lists --member-of         # Lists you're a member of\nbird list-timeline <id> -n 20  # Tweets from a list\n```\n\n### Bookmarks & Likes\n\n```bash\nbird bookmarks -n 10\nbird bookmarks --folder-id <id>           # Specific folder\nbird bookmarks --include-parent           # Include parent tweet\nbird bookmarks --author-chain             # Author's self-reply chain\nbird bookmarks --full-chain-only          # Full reply chain\nbird unbookmark <url-or-id>\nbird likes -n 10\n```\n\n### Social Graph\n\n```bash\nbird following -n 20           # Users you follow\nbird followers -n 20           # Users following you\nbird following --user <id>     # Another user's following\nbird about @handle             # Account origin/location info\n```\n\n### Engagement Actions\n\n```bash\nbird follow @handle            # Follow a user\nbird unfollow @handle          # Unfollow a user\n```\n\n### Posting\n\n```bash\nbird tweet \"hello world\"\nbird reply <url-or-id> \"nice thread!\"\nbird tweet \"check this out\" --media image.png --alt \"description\"\n```\n\n**⚠️ Posting risks**: Posting is more likely to be rate limited; if blocked, use the browser tool instead.\n\n## Media Uploads\n\n```bash\nbird tweet \"hi\" --media img.png --alt \"description\"\nbird tweet \"pics\" --media a.jpg --media b.jpg  # Up to 4 images\nbird tweet \"video\" --media clip.mp4            # Or 1 video\n```\n\n## Pagination\n\nCommands supporting pagination: `replies`, `thread`, `search`, `bookmarks`, `likes`, `list-timeline`, `following`, `followers`, `user-tweets`\n\n```bash\nbird bookmarks --all                    # Fetch all pages\nbird bookmarks --max-pages 3            # Limit pages\nbird bookmarks --cursor <cursor>        # Resume from cursor\nbird replies <id> --all --delay 1000    # Delay between pages (ms)\n```\n\n## Output Options\n\n```bash\n--json          # JSON output\n--json-full     # JSON with raw API response\n--plain         # No emoji, no color (script-friendly)\n--no-emoji      # Disable emoji\n--no-color      # Disable ANSI colors (or set NO_COLOR=1)\n--quote-depth n # Max quoted tweet depth in JSON (default: 1)\n```\n\n## Global Options\n\n```bash\n--auth-token <token>       # Set auth_token cookie\n--ct0 <token>              # Set ct0 cookie\n--cookie-source <source>   # Cookie source for browser cookies (repeatable)\n--chrome-profile <name>    # Chrome profile name\n--chrome-profile-dir <path> # Chrome/Chromium profile dir or cookie DB path\n--firefox-profile <name>   # Firefox profile\n--timeout <ms>             # Request timeout\n--cookie-timeout <ms>      # Cookie extraction timeout\n```\n\n## Config File\n\n`~/.config/bird/config.json5` (global) or `./.birdrc.json5` (project):\n\n```json5\n{\n  cookieSource: [\"chrome\"],\n  chromeProfileDir: \"/path/to/Arc/Profile\",\n  timeoutMs: 20000,\n  quoteDepth: 1,\n}\n```\n\nEnvironment variables: `BIRD_TIMEOUT_MS`, `BIRD_COOKIE_TIMEOUT_MS`, `BIRD_QUOTE_DEPTH`\n\n## Troubleshooting\n\n### Query IDs stale (404 errors)\n\n```bash\nbird query-ids --fresh\n```\n\n### Cookie extraction fails\n\n- Check browser is logged into X\n- Try different `--cookie-source`\n- For Arc/Brave: use `--chrome-profile-dir`\n\n---\n\n**TL;DR**: Read/search/engage with CLI. Post carefully or use browser. 🐦",
+  "parameters": [],
+  "enabled": true,
+  "requires": {
+    "bins": ["bird"]
+  },
+  "install": [
+    {
+      "id": "brew",
+      "kind": "brew",
+      "formula": "steipete/tap/bird",
+      "bins": ["bird"],
+      "label": "Install bird (brew)",
+      "os": ["darwin"]
+    },
+    {
+      "id": "npm",
+      "kind": "npm",
+      "package": "@steipete/bird",
+      "bins": ["bird"],
+      "label": "Install bird (npm)"
+    }
+  ],
+  "metadata": {
+    "version": "1.0.0",
+    "homepage": "https://bird.fast",
+    "tags": ["x", "twitter", "cli"]
+  }
+}

package/resources/skills/blogwatcher.json

@@ -0,0 +1,10 @@
+{
+  "id": "blogwatcher",
+  "name": "Blogwatcher",
+  "description": "Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.",
+  "icon": "📰",
+  "category": "Tools",
+  "prompt": "# blogwatcher\n\nTrack blog and RSS/Atom feed updates with the `blogwatcher` CLI.\n\nInstall\n\n- Go: `go install github.com/Hyaxia/blogwatcher/cmd/blogwatcher@latest`\n\nQuick start\n\n- `blogwatcher --help`\n\nCommon commands\n\n- Add a blog: `blogwatcher add \"My Blog\" https://example.com`\n- List blogs: `blogwatcher blogs`\n- Scan for updates: `blogwatcher scan`\n- List articles: `blogwatcher articles`\n- Mark an article read: `blogwatcher read 1`\n- Mark all articles read: `blogwatcher read-all`\n- Remove a blog: `blogwatcher remove \"My Blog\"`\n\nExample output\n\n```\n$ blogwatcher blogs\nTracked blogs (1):\n\n  xkcd\n    URL: https://xkcd.com\n```\n\n```\n$ blogwatcher scan\nScanning 1 blog(s)...\n\n  xkcd\n    Source: RSS | Found: 4 | New: 4\n\nFound 4 new article(s) total!\n```\n\nNotes\n\n- Use `blogwatcher <command> --help` to discover flags and options.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/blucli.json

@@ -0,0 +1,10 @@
+{
+  "id": "blucli",
+  "name": "Blucli",
+  "description": "BluOS CLI (blu) for discovery, playback, grouping, and volume.",
+  "icon": "🫐",
+  "category": "Tools",
+  "prompt": "# blucli (blu)\n\nUse `blu` to control Bluesound/NAD players.\n\nQuick start\n\n- `blu devices` (pick target)\n- `blu --device <id> status`\n- `blu play|pause|stop`\n- `blu volume set 15`\n\nTarget selection (in priority order)\n\n- `--device <id|name|alias>`\n- `BLU_DEVICE`\n- config default (if set)\n\nCommon tasks\n\n- Grouping: `blu group status|add|remove`\n- TuneIn search/play: `blu tunein search \"query\"`, `blu tunein play \"query\"`\n\nPrefer `--json` for scripts. Confirm the target device before changing playback.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/bluebubbles.json

@@ -0,0 +1,10 @@
+{
+  "id": "bluebubbles",
+  "name": "Bluebubbles",
+  "description": "Build or update the BlueBubbles external channel plugin for CoWork-OSS (extension package, REST send/probe, webhook inbound).",
+  "icon": "💬",
+  "category": "Tools",
+  "prompt": "# BlueBubbles plugin\n\nUse this skill when working on the BlueBubbles channel plugin.\n\n## Layout\n\n- Extension package: `extensions/bluebubbles/` (entry: `index.ts`).\n- Channel implementation: `extensions/bluebubbles/src/channel.ts`.\n- Webhook handling: `extensions/bluebubbles/src/monitor.ts` (register via `api.registerHttpHandler`).\n- REST helpers: `extensions/bluebubbles/src/send.ts` + `extensions/bluebubbles/src/probe.ts`.\n- Runtime bridge: `extensions/bluebubbles/src/runtime.ts` (set via `api.runtime`).\n- Catalog entry for onboarding: `src/channels/plugins/catalog.ts`.\n\n## Internal helpers (use these, not raw API calls)\n\n- `probeBlueBubbles` in `extensions/bluebubbles/src/probe.ts` for health checks.\n- `sendMessageBlueBubbles` in `extensions/bluebubbles/src/send.ts` for text delivery.\n- `resolveChatGuidForTarget` in `extensions/bluebubbles/src/send.ts` for chat lookup.\n- `sendBlueBubblesReaction` in `extensions/bluebubbles/src/reactions.ts` for tapbacks.\n- `sendBlueBubblesTyping` + `markBlueBubblesChatRead` in `extensions/bluebubbles/src/chat.ts`.\n- `downloadBlueBubblesAttachment` in `extensions/bluebubbles/src/attachments.ts` for inbound media.\n- `buildBlueBubblesApiUrl` + `blueBubblesFetchWithTimeout` in `extensions/bluebubbles/src/types.ts` for shared REST plumbing.\n\n## Webhooks\n\n- BlueBubbles posts JSON to the gateway HTTP server.\n- Normalize sender/chat IDs defensively (payloads vary by version).\n- Skip messages marked as from self.\n- Route into core reply pipeline via the plugin runtime (`api.runtime`) and `CoWork-OSS/plugin-sdk` helpers.\n- For attachments/stickers, use `<media:...>` placeholders when text is empty and attach media paths via `MediaUrl(s)` in the inbound context.\n\n## Config (core)\n\n- `channels.bluebubbles.serverUrl` (base URL), `channels.bluebubbles.password`, `channels.bluebubbles.webhookPath`.\n- Action gating: `channels.bluebubbles.actions.reactions` (default true).\n\n## Message tool notes\n\n- **Reactions:** The `react` action requires a `target` (phone number or chat identifier) in addition to `messageId`. Example: `action=react target=+15551234567 messageId=ABC123 emoji=❤️`",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/camsnap.json

@@ -0,0 +1,10 @@
+{
+  "id": "camsnap",
+  "name": "Camsnap",
+  "description": "Capture frames or clips from RTSP/ONVIF cameras.",
+  "icon": "📸",
+  "category": "Tools",
+  "prompt": "# camsnap\n\nUse `camsnap` to grab snapshots, clips, or motion events from configured cameras.\n\nSetup\n\n- Config file: `~/.config/camsnap/config.yaml`\n- Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass`\n\nCommon commands\n\n- Discover: `camsnap discover --info`\n- Snapshot: `camsnap snap kitchen --out shot.jpg`\n- Clip: `camsnap clip kitchen --dur 5s --out clip.mp4`\n- Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'`\n- Doctor: `camsnap doctor --probe`\n\nNotes\n\n- Requires `ffmpeg` on PATH.\n- Prefer a short test capture before longer clips.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/clean-imports.json

@@ -0,0 +1,18 @@
+{
+  "id": "clean-imports",
+  "name": "Clean Imports",
+  "description": "Remove unused imports from files",
+  "icon": "🧹",
+  "category": "Utilities",
+  "prompt": "Please clean up imports in {{path}}.\n\nTasks:\n1. Remove unused imports\n2. Sort imports alphabetically\n3. Group imports by type:\n   - Built-in/standard library\n   - External packages\n   - Internal/local imports\n4. Remove duplicate imports\n5. Fix import paths if needed\n\nApply changes and report:\n- Number of imports removed\n- Files modified\n- Any potential issues found",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to file or folder",
+      "required": true,
+      "default": "."
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/code-review.json

@@ -0,0 +1,18 @@
+{
+  "id": "code-review",
+  "name": "Code Review",
+  "description": "Review code for best practices and potential issues",
+  "icon": "🔍",
+  "category": "Development",
+  "prompt": "Please review the code in {{path}} and provide feedback on:\n- Code quality and best practices\n- Potential bugs or issues\n- Performance considerations\n- Security concerns\n- Suggestions for improvement\n\nBe constructive and specific in your feedback.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the file or folder to review",
+      "required": true,
+      "default": "."
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/coding-agent.json

@@ -0,0 +1,10 @@
+{
+  "id": "coding-agent",
+  "name": "Coding-agent",
+  "description": "Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.",
+  "icon": "🧩",
+  "category": "Tools",
+  "prompt": "# Coding Agent (bash-first)\n\nUse **bash** (with optional background mode) for all coding agent work. Simple and effective.\n\n## ⚠️ PTY Mode Required!\n\nCoding agents (Codex, Claude Code, Pi) are **interactive terminal applications** that need a pseudo-terminal (PTY) to work correctly. Without PTY, you'll get broken output, missing colors, or the agent may hang.\n\n**Always use `pty:true`** when running coding agents:\n\n```bash\n# ✅ Correct - with PTY\nbash pty:true command:\"codex exec 'Your prompt'\"\n\n# ❌ Wrong - no PTY, agent may break\nbash command:\"codex exec 'Your prompt'\"\n```\n\n### Bash Tool Parameters\n\n| Parameter    | Type    | Description                                                                 |\n| ------------ | ------- | --------------------------------------------------------------------------- |\n| `command`    | string  | The shell command to run                                                    |\n| `pty`        | boolean | **Use for coding agents!** Allocates a pseudo-terminal for interactive CLIs |\n| `workdir`    | string  | Working directory (agent sees only this folder's context)                   |\n| `background` | boolean | Run in background, returns sessionId for monitoring                         |\n| `timeout`    | number  | Timeout in seconds (kills process on expiry)                                |\n| `elevated`   | boolean | Run on host instead of sandbox (if allowed)                                 |\n\n### Process Tool Actions (for background sessions)\n\n| Action      | Description                                          |\n| ----------- | ---------------------------------------------------- |\n| `list`      | List all running/recent sessions                     |\n| `poll`      | Check if session is still running                    |\n| `log`       | Get session output (with optional offset/limit)      |\n| `write`     | Send raw data to stdin                               |\n| `submit`    | Send data + newline (like typing and pressing Enter) |\n| `send-keys` | Send key tokens or hex bytes                         |\n| `paste`     | Paste text (with optional bracketed mode)            |\n| `kill`      | Terminate the session                                |\n\n---\n\n## Quick Start: One-Shot Tasks\n\nFor quick prompts/chats, create a temp git repo and run:\n\n```bash\n# Quick chat (Codex needs a git repo!)\nSCRATCH=$(mktemp -d) && cd $SCRATCH && git init && codex exec \"Your prompt here\"\n\n# Or in a real project - with PTY!\nbash pty:true workdir:~/Projects/myproject command:\"codex exec 'Add error handling to the API calls'\"\n```\n\n**Why git init?** Codex refuses to run outside a trusted git directory. Creating a temp repo solves this for scratch work.\n\n---\n\n## The Pattern: workdir + background + pty\n\nFor longer tasks, use background mode with PTY:\n\n```bash\n# Start agent in target directory (with PTY!)\nbash pty:true workdir:~/project background:true command:\"codex exec --full-auto 'Build a snake game'\"\n# Returns sessionId for tracking\n\n# Monitor progress\nprocess action:log sessionId:XXX\n\n# Check if done\nprocess action:poll sessionId:XXX\n\n# Send input (if agent asks a question)\nprocess action:write sessionId:XXX data:\"y\"\n\n# Submit with Enter (like typing \"yes\" and pressing Enter)\nprocess action:submit sessionId:XXX data:\"yes\"\n\n# Kill if needed\nprocess action:kill sessionId:XXX\n```\n\n**Why workdir matters:** Agent wakes up in a focused directory, doesn't wander off reading unrelated files (like your soul.md 😅).\n\n---\n\n## Codex CLI\n\n**Model:** `gpt-5.2-codex` is the default (set in ~/.codex/config.toml)\n\n### Flags\n\n| Flag            | Effect                                             |\n| --------------- | -------------------------------------------------- |\n| `exec \"prompt\"` | One-shot execution, exits when done                |\n| `--full-auto`   | Sandboxed but auto-approves in workspace           |\n| `--yolo`        | NO sandbox, NO approvals (fastest, most dangerous) |\n\n### Building/Creating\n\n```bash\n# Quick one-shot (auto-approves) - remember PTY!\nbash pty:true workdir:~/project command:\"codex exec --full-auto 'Build a dark mode toggle'\"\n\n# Background for longer work\nbash pty:true workdir:~/project background:true command:\"codex --yolo 'Refactor the auth module'\"\n```\n\n### Reviewing PRs\n\n**⚠️ CRITICAL: Never review PRs in CoWork-OSS's own project folder!**\nClone to temp folder or use git worktree.\n\n```bash\n# Clone to temp for safe review\nREVIEW_DIR=$(mktemp -d)\ngit clone https://github.com/user/repo.git $REVIEW_DIR\ncd $REVIEW_DIR && gh pr checkout 130\nbash pty:true workdir:$REVIEW_DIR command:\"codex review --base origin/main\"\n# Clean up after: trash $REVIEW_DIR\n\n# Or use git worktree (keeps main intact)\ngit worktree add /tmp/pr-130-review pr-130-branch\nbash pty:true workdir:/tmp/pr-130-review command:\"codex review --base main\"\n```\n\n### Batch PR Reviews (parallel army!)\n\n```bash\n# Fetch all PR refs first\ngit fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'\n\n# Deploy the army - one Codex per PR (all with PTY!)\nbash pty:true workdir:~/project background:true command:\"codex exec 'Review PR #86. git diff origin/main...origin/pr/86'\"\nbash pty:true workdir:~/project background:true command:\"codex exec 'Review PR #87. git diff origin/main...origin/pr/87'\"\n\n# Monitor all\nprocess action:list\n\n# Post results to GitHub\ngh pr comment <PR#> --body \"<review content>\"\n```\n\n---\n\n## Claude Code\n\n```bash\n# With PTY for proper terminal output\nbash pty:true workdir:~/project command:\"claude 'Your task'\"\n\n# Background\nbash pty:true workdir:~/project background:true command:\"claude 'Your task'\"\n```\n\n---\n\n## OpenCode\n\n```bash\nbash pty:true workdir:~/project command:\"opencode run 'Your task'\"\n```\n\n---\n\n## Pi Coding Agent\n\n```bash\n# Install: npm install -g @mariozechner/pi-coding-agent\nbash pty:true workdir:~/project command:\"pi 'Your task'\"\n\n# Non-interactive mode (PTY still recommended)\nbash pty:true command:\"pi -p 'Summarize src/'\"\n\n# Different provider/model\nbash pty:true command:\"pi --provider openai --model gpt-4o-mini -p 'Your task'\"\n```\n\n**Note:** Pi now has Anthropic prompt caching enabled (PR #584, merged Jan 2026)!\n\n---\n\n## Parallel Issue Fixing with git worktrees\n\nFor fixing multiple issues in parallel, use git worktrees:\n\n```bash\n# 1. Create worktrees for each issue\ngit worktree add -b fix/issue-78 /tmp/issue-78 main\ngit worktree add -b fix/issue-99 /tmp/issue-99 main\n\n# 2. Launch Codex in each (background + PTY!)\nbash pty:true workdir:/tmp/issue-78 background:true command:\"pnpm install && codex --yolo 'Fix issue #78: <description>. Commit and push.'\"\nbash pty:true workdir:/tmp/issue-99 background:true command:\"pnpm install && codex --yolo 'Fix issue #99: <description>. Commit and push.'\"\n\n# 3. Monitor progress\nprocess action:list\nprocess action:log sessionId:XXX\n\n# 4. Create PRs after fixes\ncd /tmp/issue-78 && git push -u origin fix/issue-78\ngh pr create --repo user/repo --head fix/issue-78 --title \"fix: ...\" --body \"...\"\n\n# 5. Cleanup\ngit worktree remove /tmp/issue-78\ngit worktree remove /tmp/issue-99\n```\n\n---\n\n## ⚠️ Rules\n\n1. **Always use pty:true** - coding agents need a terminal!\n2. **Respect tool choice** - if user asks for Codex, use Codex.\n   - Orchestrator mode: do NOT hand-code patches yourself.\n   - If an agent fails/hangs, respawn it or ask the user for direction, but don't silently take over.\n3. **Be patient** - don't kill sessions because they're \"slow\"\n4. **Monitor with process:log** - check progress without interfering\n5. **--full-auto for building** - auto-approves changes\n6. **vanilla for reviewing** - no special flags needed\n7. **Parallel is OK** - run many Codex processes at once for batch work\n8. **NEVER start Codex in ~/CoWork-OSS/** - it'll read your soul docs and get weird ideas about the org chart!\n9. **NEVER checkout branches in ~/Projects/CoWork-OSS/** - that's the LIVE CoWork-OSS instance!\n\n---\n\n## Progress Updates (Critical)\n\nWhen you spawn coding agents in the background, keep the user in the loop.\n\n- Send 1 short message when you start (what's running + where).\n- Then only update again when something changes:\n  - a milestone completes (build finished, tests passed)\n  - the agent asks a question / needs input\n  - you hit an error or need user action\n  - the agent finishes (include what changed + where)\n- If you kill a session, immediately say you killed it and why.\n\nThis prevents the user from seeing only \"Agent failed before reply\" and having no idea what happened.\n\n---\n\n## Auto-Notify on Completion\n\nFor long-running background tasks, append a wake trigger to your prompt so CoWork-OSS gets notified immediately when the agent finishes (instead of waiting for the next heartbeat):\n\n```\n... your task here.\n\nWhen completely finished, run this command to notify me:\nCoWork-OSS gateway wake --text \"Done: [brief summary of what was built]\" --mode now\n```\n\n**Example:**\n\n```bash\nbash pty:true workdir:~/project background:true command:\"codex --yolo exec 'Build a REST API for todos.\n\nWhen completely finished, run: CoWork-OSS gateway wake --text \\\"Done: Built todos REST API with CRUD endpoints\\\" --mode now'\"\n```\n\nThis triggers an immediate wake event — Skippy gets pinged in seconds, not 10 minutes.\n\n---\n\n## Learnings (Jan 2026)\n\n- **PTY is essential:** Coding agents are interactive terminal apps. Without `pty:true`, output breaks or agent hangs.\n- **Git repo required:** Codex won't run outside a git directory. Use `mktemp -d && git init` for scratch work.\n- **exec is your friend:** `codex exec \"prompt\"` runs and exits cleanly - perfect for one-shots.\n- **submit vs write:** Use `submit` to send input + Enter, `write` for raw data without newline.\n- **Sass works:** Codex responds well to playful prompts. Asked it to write a haiku about being second fiddle to a space lobster, got: _\"Second chair, I code / Space lobster sets the tempo / Keys glow, I follow\"_ 🦞",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/compare-files.json

@@ -0,0 +1,23 @@
+{
+  "id": "compare-files",
+  "name": "Compare Files",
+  "description": "Compare two files and show differences",
+  "icon": "⚖️",
+  "category": "Data",
+  "prompt": "Please compare these two files and show the differences:\n\nFile 1: {{file1}}\nFile 2: {{file2}}\n\nProvide:\n1. **Summary**: High-level overview of differences\n2. **Added**: Lines/sections only in File 2\n3. **Removed**: Lines/sections only in File 1\n4. **Modified**: Lines that changed between files\n5. **Statistics**: Number of additions, deletions, modifications\n\nFor code files, highlight semantic differences (not just whitespace).\nFor data files, compare structure and content.",
+  "parameters": [
+    {
+      "name": "file1",
+      "type": "string",
+      "description": "Path to the first file",
+      "required": true
+    },
+    {
+      "name": "file2",
+      "type": "string",
+      "description": "Path to the second file",
+      "required": true
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/convert-code.json

@@ -0,0 +1,34 @@
+{
+  "id": "convert-code",
+  "name": "Convert Code",
+  "description": "Convert code from one language to another",
+  "icon": "🔄",
+  "category": "Development",
+  "prompt": "Please convert the code in {{path}} from its current language to {{targetLanguage}}.\n\nRequirements:\n- Maintain the same functionality\n- Use idiomatic patterns for the target language\n- Preserve comments (translated if needed)\n- Handle language-specific differences appropriately\n- Add type annotations if the target language supports them\n\nSave the converted code to a new file with the appropriate extension.",
+  "parameters": [
+    {
+      "name": "path",
+      "type": "string",
+      "description": "Path to the source file",
+      "required": true
+    },
+    {
+      "name": "targetLanguage",
+      "type": "select",
+      "description": "Target programming language",
+      "required": true,
+      "default": "TypeScript",
+      "options": [
+        "TypeScript",
+        "JavaScript",
+        "Python",
+        "Go",
+        "Rust",
+        "Java",
+        "C#",
+        "Ruby"
+      ]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/create-changelog.json

@@ -0,0 +1,24 @@
+{
+  "id": "create-changelog",
+  "name": "Create Changelog",
+  "description": "Generate changelog from git commits",
+  "icon": "📰",
+  "category": "Project",
+  "prompt": "Please generate a CHANGELOG.md from the git history.\n\nSteps:\n1. Run `git log --oneline` to get recent commits\n2. Group commits by type (Features, Bug Fixes, etc.)\n3. Format according to Keep a Changelog standard\n4. Include version numbers if tags exist\n5. Add dates for each version\n\nFormat:\n## [Version] - YYYY-MM-DD\n### Added\n### Changed\n### Fixed\n### Removed\n\nGenerate for the last {{commits}} commits.",
+  "parameters": [
+    {
+      "name": "commits",
+      "type": "select",
+      "description": "Number of commits to include",
+      "required": true,
+      "default": "50",
+      "options": [
+        "20",
+        "50",
+        "100",
+        "all"
+      ]
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/debug-error.json

@@ -0,0 +1,17 @@
+{
+  "id": "debug-error",
+  "name": "Debug Error",
+  "description": "Analyze an error message and suggest fixes",
+  "icon": "🐛",
+  "category": "Development",
+  "prompt": "Please help me debug this error:\n\n{{error}}\n\nSteps:\n1. Analyze the error message and stack trace\n2. Identify the root cause\n3. Search for the relevant code in the project\n4. Suggest specific fixes with code examples\n5. Explain why the error occurred and how to prevent it\n\nIf you need more context, ask me to provide relevant files.",
+  "parameters": [
+    {
+      "name": "error",
+      "type": "string",
+      "description": "The error message or stack trace",
+      "required": true
+    }
+  ],
+  "enabled": true
+}

package/resources/skills/dependency-check.json

@@ -0,0 +1,10 @@
+{
+  "id": "dependency-check",
+  "name": "Dependency Check",
+  "description": "Audit dependencies for updates and vulnerabilities",
+  "icon": "📦",
+  "category": "Project",
+  "prompt": "Please audit the project dependencies.\n\nSteps:\n1. Identify the package manager (npm, yarn, pip, etc.)\n2. List all dependencies with current versions\n3. Check for available updates\n4. Run security audit if available (npm audit, pip-audit, etc.)\n5. Identify deprecated packages\n\nReport:\n- Outdated packages with latest versions\n- Security vulnerabilities with severity\n- Deprecated packages that need replacement\n- Recommendations for updates\n\nBe careful about breaking changes in major version updates.",
+  "parameters": [],
+  "enabled": true
+}

package/resources/skills/discord.json

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