[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H3S76SW9780DS2PY96Z963":3,"skill-same:01M6H3S76SW9780DS2PY96Z963":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":60},"01M6H3S76SW9780DS2PY96Z963","add-telegram",null,"Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).","sliamh11\u002FDeus","sliamh11","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68326628?v=4","01M6H3PPFXQ6C98QV1RJA5W72S","Liam Steiner","01M6H3PPM81GJC6KYCNTY9A3AT",51,"MIT","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-telegram\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"add telegram","telegram","add","whatsapp","run","notifications","actions","channel","only","control","triggers","as","passive","it","true","can","2026-11-10 10:12:30",false,"---\nname: add-telegram\ndescription: Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).\ndisable-model-invocation: true\n---\n\n# Add Telegram Channel\n\nThis skill adds Telegram support to Deus, then walks through interactive setup.\n\n**IMPORTANT:** Do NOT add git remotes, fetch from external repos, or install npm packages from the public registry during this skill. All channel code is already in the repo under `packages\u002F` and `src\u002Fchannels\u002F`.\n\n## Phase 1: Pre-flight\n\n### Check if already applied\n\nCheck if Telegram is already configured. If `TELEGRAM_BOT_TOKEN` exists in `.env`, skip to Phase 4 (Registration) or Phase 5 (Verify).\n\n### Ask the user\n\nUse `AskUserQuestion` to collect configuration:\n\nAskUserQuestion: Do you have a Telegram bot token, or do you need to create one?\n\nIf they have one, collect it now. If not, we'll create one in Phase 3.\n\n## Phase 2: Build Local Packages\n\nThe Telegram channel is a local MCP server in `packages\u002F`. Build the packages in order (core first, then telegram):\n\n```bash\ncd packages\u002Fmcp-channel-core && npm install && npm run build && cd ..\u002F..\ncd packages\u002Fmcp-telegram && npm install && npm run build && cd ..\u002F..\n```\n\n### Validate\n\n```bash\nnpm run build\n```\n\nBuild must be clean before proceeding.\n\n## Phase 3: Setup\n\n### Create Telegram Bot (if needed)\n\nIf the user doesn't have a bot token, tell them:\n\n> I need you to create a Telegram bot:\n>\n> 1. Open Telegram and search for `@BotFather`\n> 2. Send `\u002Fnewbot` and follow prompts:\n>    - Bot name: Something friendly (e.g., \"Deus Assistant\")\n>    - Bot username: Must end with \"bot\" (e.g., \"andy_ai_bot\")\n> 3. Copy the bot token (looks like `123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11`)\n\nWait for the user to provide the token.\n\n### Configure environment\n\nAdd to `.env`:\n\n```bash\nTELEGRAM_BOT_TOKEN=\u003Ctheir-token>\n```\n\nChannels auto-enable when their credentials are present — no extra configuration needed.\n\nSync to container environment:\n\n```bash\nmkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv\n```\n\nThe container reads environment from `data\u002Fenv\u002Fenv`, not `.env` directly.\n\n### Disable Group Privacy (for group chats)\n\nTell the user:\n\n> **Important for group chats**: By default, Telegram bots only see @mentions and commands in groups. To let the bot see all messages:\n>\n> 1. Open Telegram and search for `@BotFather`\n> 2. Send `\u002Fmybots` and select your bot\n> 3. Go to **Bot Settings** > **Group Privacy** > **Turn off**\n>\n> This is optional if you only want trigger-based responses via @mentioning the bot.\n\n### Build and restart\n\n```bash\nnpm run build\n```\n\nRestart the service (platform-specific):\n- macOS: `launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus`\n- Linux: `systemctl --user restart deus`\n- Windows: `nssm restart deus` or `servy-cli restart --name=deus`\n\n## Phase 4: Registration\n\n### Get Chat ID\n\nTell the user:\n\n> 1. Open your bot in Telegram (search for its username)\n> 2. Send `\u002Fchatid` — it will reply with the chat ID\n> 3. For groups: add the bot to the group first, then send `\u002Fchatid` in the group\n\nWait for the user to provide the chat ID (format: `tg:123456789` or `tg:-1001234567890`).\n\n### Register the chat\n\nThe chat ID, name, and folder name are needed. Use `npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main chat (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"tg:\u003Cchat-id>\" --name \"\u003Cchat-name>\" --folder \"telegram_main\" --trigger \"@${ASSISTANT_NAME}\" --channel telegram --no-trigger-required --is-main\n```\n\nFor additional chats (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"tg:\u003Cchat-id>\" --name \"\u003Cchat-name>\" --folder \"telegram_\u003Cgroup-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel telegram\n```\n\n## Phase 5: Verify\n\n### Test the connection\n\nTell the user:\n\n> Send a message to your registered Telegram chat:\n> - For main chat: Any message works\n> - For non-main: `@Deus hello` or @mention the bot\n>\n> The bot should respond within a few seconds.\n\n### Smoke test\n\nRun the automated smoke test to verify service, DB, and channel connection:\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel telegram\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread works, and channel connection appears in logs.\n\nIf the smoke test passes, tell the user \"Telegram channel is working.\"\n\nIf it fails, check the STATUS output for the specific failure (service down, no registered group, DB error, or no log connection). Guide the user to fix the issue before proceeding.\n\nAfter the automated check, also ask the user to send a test message to verify real-time delivery:\n\n> Send a message to your registered Telegram chat to confirm real-time delivery.\n> - For main chat: Any message works\n> - For non-main: `@Deus hello` or @mention the bot\n\n### Check logs if needed\n\n```bash\ntail -f logs\u002Fdeus.log\n```\n\n## Troubleshooting\n\n### Bot not responding\n\nCheck:\n1. `TELEGRAM_BOT_TOKEN` is set in `.env` AND synced to `data\u002Fenv\u002Fenv`\n2. Chat is registered in SQLite (check with: `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'tg:%'\"`)\n3. For non-main chats: message includes trigger pattern\n4. Service is running: `launchctl list | grep deus` (macOS) or `systemctl --user status deus` (Linux)\n\n### Bot only responds to @mentions in groups\n\nGroup Privacy is enabled (default). Fix:\n1. `@BotFather` > `\u002Fmybots` > select bot > **Bot Settings** > **Group Privacy** > **Turn off**\n2. Remove and re-add the bot to the group (required for the change to take effect)\n\n### Getting chat ID\n\nIf `\u002Fchatid` doesn't work:\n- Verify token: `curl -s \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TELEGRAM_BOT_TOKEN}\u002FgetMe\"`\n- Check bot is started: `tail -f logs\u002Fdeus.log`\n\n## After Setup\n\nIf running `npm run dev` while the service is active:\n```bash\n# macOS:\nlaunchctl unload ~\u002FLibrary\u002FLaunchAgents\u002Fcom.deus.plist\nnpm run dev\n# When done testing:\nlaunchctl load ~\u002FLibrary\u002FLaunchAgents\u002Fcom.deus.plist\n# Linux:\n# systemctl --user stop deus\n# npm run dev\n# systemctl --user start deus\n```\n\n## Agent Swarms (Teams)\n\nAfter completing the Telegram setup, use `AskUserQuestion`:\n\nAskUserQuestion: Would you like to add Agent Swarm support? Without it, Agent Teams still work — they just operate behind the scenes. With Swarm support, each subagent appears as a different bot in the Telegram group so you can see who's saying what and have interactive team sessions.\n\nIf they say yes, tell the user to run the `\u002Fadd-telegram-swarm` skill themselves (it is a user-invoked setup skill and cannot be triggered automatically).\n\n## Troubleshooting: Re-authentication\n\nIf the bot stops responding or the token becomes invalid:\n\n1. Verify the token is still valid:\n   ```bash\n   curl -s \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TELEGRAM_BOT_TOKEN}\u002FgetMe\" | grep -q '\"ok\":true' && echo \"Token valid\" || echo \"Token invalid\"\n   ```\n2. If the token is invalid, generate a new one via `@BotFather` > `\u002Fmybots` > select bot > **API Token** > **Revoke current token**\n3. Update the token in `.env` and sync: `mkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv`\n4. Restart the service — no re-registration needed (the chat ID stays the same)\n\nCommon causes of bot failure:\n- Token was revoked via BotFather\n- Bot was deleted and recreated (new token needed, chat IDs may change for private chats)\n- Telegram API rate limiting (wait a few minutes and retry)\n\n## Removal\n\nTo remove Telegram integration:\n\n1. Remove import from `src\u002Fchannels\u002Findex.ts`\n2. Remove `TELEGRAM_BOT_TOKEN` from `.env`\n3. Remove Telegram registrations: `sqlite3 store\u002Fmessages.db \"DELETE FROM registered_groups WHERE jid LIKE 'tg:%'\"`\n4. Rebuild and restart\n","# Add Telegram Channel\n\nThis skill adds Telegram support to Deus, then walks through interactive setup.\n\n**IMPORTANT:** Do NOT add git remotes, fetch from external repos, or install npm packages from the public registry during this skill. All channel code is already in the repo under `packages\u002F` and `src\u002Fchannels\u002F`.\n\n## Phase 1: Pre-flight\n\n### Check if already applied\n\nCheck if Telegram is already configured. If `TELEGRAM_BOT_TOKEN` exists in `.env`, skip to Phase 4 (Registration) or Phase 5 (Verify).\n\n### Ask the user\n\nUse `AskUserQuestion` to collect configuration:\n\nAskUserQuestion: Do you have a Telegram bot token, or do you need to create one?\n\nIf they have one, collect it now. If not, we'll create one in Phase 3.\n\n## Phase 2: Build Local Packages\n\nThe Telegram channel is a local MCP server in `packages\u002F`. Build the packages in order (core first, then telegram):\n\n```bash\ncd packages\u002Fmcp-channel-core && npm install && npm run build && cd ..\u002F..\ncd packages\u002Fmcp-telegram && npm install && npm run build && cd ..\u002F..\n```\n\n### Validate\n\n```bash\nnpm run build\n```\n\nBuild must be clean before proceeding.\n\n## Phase 3: Setup\n\n### Create Telegram Bot (if needed)\n\nIf the user doesn't have a bot token, tell them:\n\n> I need you to create a Telegram bot:\n>\n> 1. Open Telegram and search for `@BotFather`\n> 2. Send `\u002Fnewbot` and follow prompts:\n>    - Bot name: Something friendly (e.g., \"Deus Assistant\")\n>    - Bot username: Must end with \"bot\" (e.g., \"andy_ai_bot\")\n> 3. Copy the bot token (looks like `123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11`)\n\nWait for the user to provide the token.\n\n### Configure environment\n\nAdd to `.env`:\n\n```bash\nTELEGRAM_BOT_TOKEN=\u003Ctheir-token>\n```\n\nChannels auto-enable when their credentials are present — no extra configuration needed.\n\nSync to container environment:\n\n```bash\nmkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv\n```\n\nThe container reads environment from `data\u002Fenv\u002Fenv`, not `.env` directly.\n\n### Disable Group Privacy (for group chats)\n\nTell the user:\n\n> **Important for group chats**: By default, Telegram bots only see @mentions and commands in groups. To let the bot see all messages:\n>\n> 1. Open Telegram and search for `@BotFather`\n> 2. Send `\u002Fmybots` and select your bot\n> 3. Go to **Bot Settings** > **Group Privacy** > **Turn off**\n>\n> This is optional if you only want trigger-based responses via @mentioning the bot.\n\n### Build and restart\n\n```bash\nnpm run build\n```\n\nRestart the service (platform-specific):\n- macOS: `launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus`\n- Linux: `systemctl --user restart deus`\n- Windows: `nssm restart deus` or `servy-cli restart --name=deus`\n\n## Phase 4: Registration\n\n### Get Chat ID\n\nTell the user:\n\n> 1. Open your bot in Telegram (search for its username)\n> 2. Send `\u002Fchatid` — it will reply with the chat ID\n> 3. For groups: add the bot to the group first, then send `\u002Fchatid` in the group\n\nWait for the user to provide the chat ID (format: `tg:123456789` or `tg:-1001234567890`).\n\n### Register the chat\n\nThe chat ID, name, and folder name are needed. Use `npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main chat (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"tg:\u003Cchat-id>\" --name \"\u003Cchat-name>\" --folder \"telegram_main\" --trigger \"@${ASSISTANT_NAME}\" --channel telegram --no-trigger-required --is-main\n```\n\nFor additional chats (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"tg:\u003Cchat-id>\" --name \"\u003Cchat-name>\" --folder \"telegram_\u003Cgroup-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel telegram\n```\n\n## Phase 5: Verify\n\n### Test the connection\n\nTell the user:\n\n> Send a message to your registered Telegram chat:\n> - For main chat: Any message works\n> - For non-main: `@Deus hello` or @mention the bot\n>\n> The bot should respond within a few seconds.\n\n### Smoke test\n\nRun the automated smoke test to verify service, DB, and channel connection:\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel telegram\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread works, and channel connection appears in logs.\n\nIf the smoke test passes, tell the user \"Telegram channel is working.\"\n\nIf it fails, check the STATUS output for the specific failure (service down, no registered group, DB error, or no log connection). Guide the user to fix the issue before proceeding.\n\nAfter the automated check, also ask the user to send a test message to verify real-time delivery:\n\n> Send a message to your registered Telegram chat to confirm real-time delivery.\n> - For main chat: Any message works\n> - For non-main: `@Deus hello` or @mention the bot\n\n### Check logs if needed\n\n```bash\ntail -f logs\u002Fdeus.log\n```\n\n## Troubleshooting\n\n### Bot not responding\n\nCheck:\n1. `TELEGRAM_BOT_TOKEN` is set in `.env` AND synced to `data\u002Fenv\u002Fenv`\n2. Chat is registered in SQLite (check with: `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'tg:%'\"`)\n3. For non-main chats: message includes trigger pattern\n4. Service is running: `launchctl list | grep deus` (macOS) or `systemctl --user status deus` (Linux)\n\n### Bot only responds to @mentions in groups\n\nGroup Privacy is enabled (default). Fix:\n1. `@BotFather` > `\u002Fmybots` > select bot > **Bot Settings** > **Group Privacy** > **Turn off**\n2. Remove and re-add the bot to the group (required for the change to take effect)\n\n### Getting chat ID\n\nIf `\u002Fchatid` doesn't work:\n- Verify token: `curl -s \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TELEGRAM_BOT_TOKEN}\u002FgetMe\"`\n- Check bot is started: `tail -f logs\u002Fdeus.log`\n\n## After Setup\n\nIf running `npm run dev` while the service is active:\n```bash\n# macOS:\nlaunchctl unload ~\u002FLibrary\u002FLaunchAgents\u002Fcom.deus.plist\nnpm run dev\n# When done testing:\nlaunchctl load ~\u002FLibrary\u002FLaunchAgents\u002Fcom.deus.plist\n# Linux:\n# systemctl --user stop deus\n# npm run dev\n# systemctl --user start deus\n```\n\n## Agent Swarms (Teams)\n\nAfter completing the Telegram setup, use `AskUserQuestion`:\n\nAskUserQuestion: Would you like to add Agent Swarm support? Without it, Agent Teams still work — they just operate behind the scenes. With Swarm support, each subagent appears as a different bot in the Telegram group so you can see who's saying what and have interactive team sessions.\n\nIf they say yes, tell the user to run the `\u002Fadd-telegram-swarm` skill themselves (it is a user-invoked setup skill and cannot be triggered automatically).\n\n## Troubleshooting: Re-authentication\n\nIf the bot stops responding or the token becomes invalid:\n\n1. Verify the token is still valid:\n   ```bash\n   curl -s \"https:\u002F\u002Fapi.telegram.org\u002Fbot${TELEGRAM_BOT_TOKEN}\u002FgetMe\" | grep -q '\"ok\":true' && echo \"Token valid\" || echo \"Token invalid\"\n   ```\n2. If the token is invalid, generate a new one via `@BotFather` > `\u002Fmybots` > select bot > **API Token** > **Revoke current token**\n3. Update the token in `.env` and sync: `mkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv`\n4. Restart the service — no re-registration needed (the chat ID stays the same)\n\nCommon causes of bot failure:\n- Token was revoked via BotFather\n- Bot was deleted and recreated (new token needed, chat IDs may change for private chats)\n- Telegram API rate limiting (wait a few minutes and retry)\n\n## Removal\n\nTo remove Telegram integration:\n\n1. Remove import from `src\u002Fchannels\u002Findex.ts`\n2. Remove `TELEGRAM_BOT_TOKEN` from `.env`\n3. Remove Telegram registrations: `sqlite3 store\u002Fmessages.db \"DELETE FROM registered_groups WHERE jid LIKE 'tg:%'\"`\n4. Rebuild and restart\n",{"name":5,"description":7,"disable-model-invocation":40},true,"main","2f24c38a2ae42d3161492f0729975b286452f4b4",".claude\u002Fskills\u002Fadd-telegram",7,"https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus","https:\u002F\u002Fgithub.com\u002Fsliamh11","2026-11-10 03:41:56",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":40},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sliamh11\u002FDeus --skill add-telegram",{"tool":54,"command":55},"bunx","bunx skills add sliamh11\u002FDeus --skill add-telegram",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sliamh11\u002FDeus --skill add-telegram","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-telegram\u002FSKILL.md",[],[62,87,107,121,131,145],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":35},"01M6H3ZC87AJDM8566RP3CQ6BF","status","Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs \u002Fstatus.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fstatus\u002FSKILL.md",[],[64,69,70,71,72,73,74,75,76,77,27,78,79,80,81,82,83,84,85,86],"health","snapshot","for","read-only","quick","availability","session context","task","health check","use","session","user","context","read","check","workspace","tool","system",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":35},"01M6H3Z8SK38PVH2B0W7NBP6ZP","resume","Load context from permanent memory and recent session logs. Tiered loading — CLAUDE.md full, session logs frontmatter-only by default.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fresume\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[89,99,100,101,102,103,104,27,79,81,105,106],"memory","load","loading","full","session logs","default","logs","frontmatter",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":35},"01M6H3Z56ZBPKX77THMWSSHZCW","preserve","Scan the current conversation and silently save anything worth permanent memory to CLAUDE.md. Keeps the file compact — structured key:value, no prose.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fpreserve\u002FSKILL.md",[],[109,114,115,116,117,118,119,120,99],"structured","compact","scan","conversation","prose","save","file",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":35},"01M6H3Z1AKK58CWWY762YD3X9A","compress","Save the current session to the vault. Writes a compact session log with a TL;DR frontmatter (always) and full details below (when useful).","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fcompress\u002FSKILL.md",[],[123,128,106,102,115,129,79,119,130],"with","log","vault",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":35},"01M6H3YX6STE1ZJC06EKWMY0M6","capabilities","Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs \u002Fcapabilities.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fcapabilities\u002FSKILL.md",[],[133,138,139,86,72,34,140,141,142,143,144,27,78,80,82],"Tools","bot","system info","info","what the","do","show",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":156,"publishedAt":35},"01M6H3YSNXYAR7NC1TZPFCANZN","agent-browser","Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fagent-browser\u002FSKILL.md",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[157,158,159,71,128,160,161,162,76,163,78,82,164,165,166,167,168,169,170,171],"agent browser","browser","take","apps","pages","forms","test web","just","Bash","browse","data","web","test","research","screenshots"]