[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H3RBJCF2F8XY4ADG5N69A3":3,"skill-same:01M6H3RBJCF2F8XY4ADG5N69A3":65},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":64},"01M6H3RBJCF2F8XY4ADG5N69A3","add-msft-teams",null,"Add Microsoft Teams as a channel. Can replace WhatsApp entirely or run alongside it. Uses the Azure Bot Service (Bot Framework) and requires a public HTTPS messaging endpoint.","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-msft-teams\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"add msft teams","teams","add","public","can","true","microsoft teams","azure bot service","as","service","channel","bot","endpoint","https","messaging","framework","run","azure","microsoft","whatsapp","2026-11-10 10:12:30",false,"---\nname: add-msft-teams\ndescription: Add Microsoft Teams as a channel. Can replace WhatsApp entirely or run alongside it. Uses the Azure Bot Service (Bot Framework) and requires a public HTTPS messaging endpoint.\ndisable-model-invocation: true\n---\n\n# Add Microsoft Teams Channel\n\n> **Status:** Available in-repo as `packages\u002Fmcp-teams\u002F` (`@deus-ai\u002Fteams-mcp`). The published npm package is not out yet, so the channel factory falls back to the in-repo build at `packages\u002Fmcp-teams\u002Fdist\u002Findex.js` — you build it locally (below).\n\nMicrosoft Teams is the chat-channel analog of Slack: a bot identity receives\nmessages and posts replies. Unlike Slack's Socket Mode, the Teams bot uses the\n**Azure Bot Service (Bot Framework)**, which delivers activities to a **public\nHTTPS messaging endpoint**. The channel runs its own HTTP server on `TEAMS_PORT`\n(default 3978) serving `\u002Fapi\u002Fmessages`; you must expose that port via a\n**dedicated public tunnel** (see below) — Deus's existing ingress tunnel forwards\nonly the gateway port and does **not** cover `TEAMS_PORT`.\n\n## Phase 1: Setup\n\n### Register the Azure app + bot (if needed)\n\nIf the user doesn't have an Azure Bot, walk them through it. Quick summary of\nwhat's needed:\n\n1. In the [Azure Portal](https:\u002F\u002Fportal.azure.com) → **Microsoft Entra ID** →\n   **App registrations** → **New registration**. Copy the **Application (client)\n   ID** and **Directory (tenant) ID**.\n2. **Certificates & secrets** → **New client secret** → copy the secret **value**\n   (shown once).\n3. Start a dedicated tunnel to the Teams port (any HTTPS tunnel works):\n\n   ```bash\n   ngrok http 3978   # → forwards a public https URL to http:\u002F\u002Flocalhost:3978\n   ```\n\n4. Create an **Azure Bot** resource (Azure Bot Service). Link it to the app\n   registration above (the Microsoft App ID). Set the **messaging endpoint** to\n   your tunnel's URL: `https:\u002F\u002F\u003Cyour-tunnel-domain>\u002Fapi\u002Fmessages`.\n5. On the bot resource → **Channels** → enable the **Microsoft Teams** channel.\n6. Create a Teams app (Developer Portal for Teams \u002F manifest) that references the\n   bot's App ID, then install it to a team or chat.\n\n> The messaging endpoint must be a **public HTTPS URL** reaching `TEAMS_PORT`.\n> A local-only endpoint (or the gateway tunnel) will not receive Bot Framework\n> activities — use a dedicated tunnel to port 3978.\n\n### Configure environment\n\nAdd to `.env` (use the values from the app registration — no personal tenant or\ndomain values belong in this skill):\n\n```bash\nTEAMS_APP_ID=\u003Cyour-application-client-id>\nTEAMS_APP_PASSWORD=\u003Cyour-client-secret-value>\n# Single-tenant only (omit for a multi-tenant bot):\nTEAMS_APP_TENANT_ID=\u003Cyour-directory-tenant-id>\n# Optional — defaults to 3978:\n# TEAMS_PORT=3978\n```\n\n### Build the package\n\nThe published npm package is not out yet, so build the in-repo package:\n\n```bash\ncd packages\u002Fmcp-teams && npm install && npm run build && cd ..\u002F..\n```\n\nThe channel runs **host-side** and auto-enables once `TEAMS_APP_ID` +\n`TEAMS_APP_PASSWORD` are present. Restart the service so the host picks it up:\n\n```bash\n# macOS\nlaunchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus\n# Linux (systemd)\nsudo systemctl restart deus\n```\n\n## Phase 2: Registration\n\n### Get the conversation ID\n\nTell the user:\n\n> 1. Add the bot to a Teams channel or chat (install the Teams app, then\n>    @mention the bot once so Teams creates a conversation reference).\n> 2. The conversation ID is the Bot Framework `conversation.id` for that\n>    channel\u002Fchat. The setup helper will capture it from the first inbound\n>    activity once the channel is live.\n>\n> The JID format for Deus is: `teams:\u003Cconversation-id>`\n\n### Register the channel\n\nThe conversation ID, name, and folder name are needed. Use\n`npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main channel (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"teams:\u003Cconversation-id>\" --name \"\u003Cchannel-name>\" --folder \"teams_main\" --trigger \"@${ASSISTANT_NAME}\" --channel teams --no-trigger-required --is-main\n```\n\nFor additional channels (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"teams:\u003Cconversation-id>\" --name \"\u003Cchannel-name>\" --folder \"teams_\u003Cchannel-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel teams\n```\n\n## Verify\n\n### Smoke test\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel teams\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread\nworks, and channel connection appears in logs.\n\nIf it passes, tell the user \"Microsoft Teams channel is working.\" Then ask them\nto send a test message:\n\n> Send a message in your registered Teams channel to confirm real-time delivery.\n> - For main channel: any message works\n> - For non-main: @mention the bot\n\n## Troubleshooting\n\n### Bot not responding\n\n1. Check `TEAMS_APP_ID`, `TEAMS_APP_PASSWORD`, and `TEAMS_APP_TENANT_ID` are set\n   in `.env`.\n2. Confirm the package is built: `ls packages\u002Fmcp-teams\u002Fdist\u002Findex.js`.\n3. Check the channel is registered:\n   `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'teams:%'\"`\n4. For non-main channels: the message must include the trigger pattern.\n5. Service is running: `launchctl list | grep deus` (macOS) \u002F\n   `systemctl status deus` (Linux).\n\n### Bot connected but not receiving messages\n\n1. Verify the messaging endpoint in the Azure Bot resource is your **dedicated\n   tunnel's** `https:\u002F\u002F...\u002Fapi\u002Fmessages` URL (reaching `TEAMS_PORT`), reachable\n   from the internet.\n2. Verify the **Microsoft Teams** channel is enabled on the bot resource.\n3. Verify the Teams app (manifest) referencing the bot is installed in the\n   target team\u002Fchat.\n4. Check the dedicated tunnel is up — a Bot Framework activity to an unreachable\n   endpoint is silently dropped by Azure. (The Deus ingress tunnel does NOT cover\n   `TEAMS_PORT` — Teams needs its own tunnel.)\n\n### Authorization \u002F 401 from the Bot Framework\n\n1. Confirm the client secret **value** (not the secret ID) is in\n   `TEAMS_APP_PASSWORD`, and that it has not expired (Azure secrets expire).\n2. Confirm `TEAMS_APP_TENANT_ID` matches the app registration's directory (for a\n   single-tenant bot).\n3. Regenerate the secret in **Certificates & secrets** if in doubt, update\n   `.env`, and restart (`launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus` on macOS \u002F\n   `sudo systemctl restart deus` on Linux).\n\n## After Setup\n\nThe Microsoft Teams channel will support:\n\n- **Team channels** — the bot must be installed in the team and @mentioned.\n- **Group chats** — the bot must be added to the chat.\n- **1:1 chats** — users can message the bot directly.\n- **Multi-channel** — can run alongside WhatsApp or other channels (auto-enabled\n  by credentials).\n\n## Known Limitations\n\n- **Dedicated public endpoint required** — unlike Slack's Socket Mode, the Bot\n  Framework pushes activities to a public HTTPS endpoint. The channel listens on\n  `TEAMS_PORT` (3978); you must expose it with a dedicated tunnel and point the\n  Azure Bot messaging endpoint at it. Deus's existing ingress tunnel covers only\n  the gateway port, not `TEAMS_PORT`.\n- **Reply needs a prior inbound** — outbound replies use Bot Framework proactive\n  messaging, which requires a conversation reference captured from a prior inbound\n  activity (persisted to `~\u002F.teams-mcp\u002Fconversations.json`). A reply to a\n  conversation the bot has never received a message from is logged and skipped.\n- **Threads \u002F replies** — Teams reply chains will be delivered as flat messages\n  unless thread-aware routing is added (database schema, `NewMessage` type, and\n  `Channel.sendMessage` interface changes), the same limitation the Slack channel\n  documents.\n- **Adaptive Cards \u002F attachments** — only text content is forwarded to the agent\n  in the initial integration. Adaptive Cards, files, and images are not handled.\n- **Secret expiry** — Azure client secrets expire; the channel will start\n  failing auth when the secret lapses, with no proactive warning until the\n  credential-probe maintenance script is extended to cover Teams.\n","# Add Microsoft Teams Channel\n\n> **Status:** Available in-repo as `packages\u002Fmcp-teams\u002F` (`@deus-ai\u002Fteams-mcp`). The published npm package is not out yet, so the channel factory falls back to the in-repo build at `packages\u002Fmcp-teams\u002Fdist\u002Findex.js` — you build it locally (below).\n\nMicrosoft Teams is the chat-channel analog of Slack: a bot identity receives\nmessages and posts replies. Unlike Slack's Socket Mode, the Teams bot uses the\n**Azure Bot Service (Bot Framework)**, which delivers activities to a **public\nHTTPS messaging endpoint**. The channel runs its own HTTP server on `TEAMS_PORT`\n(default 3978) serving `\u002Fapi\u002Fmessages`; you must expose that port via a\n**dedicated public tunnel** (see below) — Deus's existing ingress tunnel forwards\nonly the gateway port and does **not** cover `TEAMS_PORT`.\n\n## Phase 1: Setup\n\n### Register the Azure app + bot (if needed)\n\nIf the user doesn't have an Azure Bot, walk them through it. Quick summary of\nwhat's needed:\n\n1. In the [Azure Portal](https:\u002F\u002Fportal.azure.com) → **Microsoft Entra ID** →\n   **App registrations** → **New registration**. Copy the **Application (client)\n   ID** and **Directory (tenant) ID**.\n2. **Certificates & secrets** → **New client secret** → copy the secret **value**\n   (shown once).\n3. Start a dedicated tunnel to the Teams port (any HTTPS tunnel works):\n\n   ```bash\n   ngrok http 3978   # → forwards a public https URL to http:\u002F\u002Flocalhost:3978\n   ```\n\n4. Create an **Azure Bot** resource (Azure Bot Service). Link it to the app\n   registration above (the Microsoft App ID). Set the **messaging endpoint** to\n   your tunnel's URL: `https:\u002F\u002F\u003Cyour-tunnel-domain>\u002Fapi\u002Fmessages`.\n5. On the bot resource → **Channels** → enable the **Microsoft Teams** channel.\n6. Create a Teams app (Developer Portal for Teams \u002F manifest) that references the\n   bot's App ID, then install it to a team or chat.\n\n> The messaging endpoint must be a **public HTTPS URL** reaching `TEAMS_PORT`.\n> A local-only endpoint (or the gateway tunnel) will not receive Bot Framework\n> activities — use a dedicated tunnel to port 3978.\n\n### Configure environment\n\nAdd to `.env` (use the values from the app registration — no personal tenant or\ndomain values belong in this skill):\n\n```bash\nTEAMS_APP_ID=\u003Cyour-application-client-id>\nTEAMS_APP_PASSWORD=\u003Cyour-client-secret-value>\n# Single-tenant only (omit for a multi-tenant bot):\nTEAMS_APP_TENANT_ID=\u003Cyour-directory-tenant-id>\n# Optional — defaults to 3978:\n# TEAMS_PORT=3978\n```\n\n### Build the package\n\nThe published npm package is not out yet, so build the in-repo package:\n\n```bash\ncd packages\u002Fmcp-teams && npm install && npm run build && cd ..\u002F..\n```\n\nThe channel runs **host-side** and auto-enables once `TEAMS_APP_ID` +\n`TEAMS_APP_PASSWORD` are present. Restart the service so the host picks it up:\n\n```bash\n# macOS\nlaunchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus\n# Linux (systemd)\nsudo systemctl restart deus\n```\n\n## Phase 2: Registration\n\n### Get the conversation ID\n\nTell the user:\n\n> 1. Add the bot to a Teams channel or chat (install the Teams app, then\n>    @mention the bot once so Teams creates a conversation reference).\n> 2. The conversation ID is the Bot Framework `conversation.id` for that\n>    channel\u002Fchat. The setup helper will capture it from the first inbound\n>    activity once the channel is live.\n>\n> The JID format for Deus is: `teams:\u003Cconversation-id>`\n\n### Register the channel\n\nThe conversation ID, name, and folder name are needed. Use\n`npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main channel (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"teams:\u003Cconversation-id>\" --name \"\u003Cchannel-name>\" --folder \"teams_main\" --trigger \"@${ASSISTANT_NAME}\" --channel teams --no-trigger-required --is-main\n```\n\nFor additional channels (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"teams:\u003Cconversation-id>\" --name \"\u003Cchannel-name>\" --folder \"teams_\u003Cchannel-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel teams\n```\n\n## Verify\n\n### Smoke test\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel teams\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread\nworks, and channel connection appears in logs.\n\nIf it passes, tell the user \"Microsoft Teams channel is working.\" Then ask them\nto send a test message:\n\n> Send a message in your registered Teams channel to confirm real-time delivery.\n> - For main channel: any message works\n> - For non-main: @mention the bot\n\n## Troubleshooting\n\n### Bot not responding\n\n1. Check `TEAMS_APP_ID`, `TEAMS_APP_PASSWORD`, and `TEAMS_APP_TENANT_ID` are set\n   in `.env`.\n2. Confirm the package is built: `ls packages\u002Fmcp-teams\u002Fdist\u002Findex.js`.\n3. Check the channel is registered:\n   `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'teams:%'\"`\n4. For non-main channels: the message must include the trigger pattern.\n5. Service is running: `launchctl list | grep deus` (macOS) \u002F\n   `systemctl status deus` (Linux).\n\n### Bot connected but not receiving messages\n\n1. Verify the messaging endpoint in the Azure Bot resource is your **dedicated\n   tunnel's** `https:\u002F\u002F...\u002Fapi\u002Fmessages` URL (reaching `TEAMS_PORT`), reachable\n   from the internet.\n2. Verify the **Microsoft Teams** channel is enabled on the bot resource.\n3. Verify the Teams app (manifest) referencing the bot is installed in the\n   target team\u002Fchat.\n4. Check the dedicated tunnel is up — a Bot Framework activity to an unreachable\n   endpoint is silently dropped by Azure. (The Deus ingress tunnel does NOT cover\n   `TEAMS_PORT` — Teams needs its own tunnel.)\n\n### Authorization \u002F 401 from the Bot Framework\n\n1. Confirm the client secret **value** (not the secret ID) is in\n   `TEAMS_APP_PASSWORD`, and that it has not expired (Azure secrets expire).\n2. Confirm `TEAMS_APP_TENANT_ID` matches the app registration's directory (for a\n   single-tenant bot).\n3. Regenerate the secret in **Certificates & secrets** if in doubt, update\n   `.env`, and restart (`launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus` on macOS \u002F\n   `sudo systemctl restart deus` on Linux).\n\n## After Setup\n\nThe Microsoft Teams channel will support:\n\n- **Team channels** — the bot must be installed in the team and @mentioned.\n- **Group chats** — the bot must be added to the chat.\n- **1:1 chats** — users can message the bot directly.\n- **Multi-channel** — can run alongside WhatsApp or other channels (auto-enabled\n  by credentials).\n\n## Known Limitations\n\n- **Dedicated public endpoint required** — unlike Slack's Socket Mode, the Bot\n  Framework pushes activities to a public HTTPS endpoint. The channel listens on\n  `TEAMS_PORT` (3978); you must expose it with a dedicated tunnel and point the\n  Azure Bot messaging endpoint at it. Deus's existing ingress tunnel covers only\n  the gateway port, not `TEAMS_PORT`.\n- **Reply needs a prior inbound** — outbound replies use Bot Framework proactive\n  messaging, which requires a conversation reference captured from a prior inbound\n  activity (persisted to `~\u002F.teams-mcp\u002Fconversations.json`). A reply to a\n  conversation the bot has never received a message from is logged and skipped.\n- **Threads \u002F replies** — Teams reply chains will be delivered as flat messages\n  unless thread-aware routing is added (database schema, `NewMessage` type, and\n  `Channel.sendMessage` interface changes), the same limitation the Slack channel\n  documents.\n- **Adaptive Cards \u002F attachments** — only text content is forwarded to the agent\n  in the initial integration. Adaptive Cards, files, and images are not handled.\n- **Secret expiry** — Azure client secrets expire; the channel will start\n  failing auth when the secret lapses, with no proactive warning until the\n  credential-probe maintenance script is extended to cover Teams.\n",{"name":5,"description":7,"disable-model-invocation":44},true,"main","2f24c38a2ae42d3161492f0729975b286452f4b4",".claude\u002Fskills\u002Fadd-msft-teams",7,"https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus","https:\u002F\u002Fgithub.com\u002Fsliamh11","2026-11-13 20:39:27",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":44},[54,57,60],{"tool":55,"command":56},"npx","npx skills add sliamh11\u002FDeus --skill add-msft-teams",{"tool":58,"command":59},"bunx","bunx skills add sliamh11\u002FDeus --skill add-msft-teams",{"tool":61,"command":62},"pnpm","pnpm dlx skills add sliamh11\u002FDeus --skill add-msft-teams","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-msft-teams\u002FSKILL.md",[],[66,92,112,126,136,149],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":39},"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",[],[68,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91],"health","snapshot","for","read-only","quick","availability","session context","task","health check","only","use","session","user","context","read","check","workspace","tool","system",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":103,"publishedAt":39},"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",[98],{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[94,104,105,106,107,108,109,82,84,86,110,111],"memory","load","loading","full","session logs","default","logs","frontmatter",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":39},"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",[],[114,119,120,121,122,123,124,125,104],"structured","compact","scan","conversation","prose","save","file",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":39},"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",[],[128,133,111,107,120,134,84,124,135],"with","log","vault",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":39},"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",[],[138,143,30,91,76,23,144,145,146,147,148,82,83,85,87],"Tools","system info","info","what the","do","show",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":160,"publishedAt":39},"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",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":158,"taxonomyTypeDesc":159},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[161,162,163,75,133,164,165,166,80,167,83,87,168,169,170,171,172,173,174,175],"agent browser","browser","take","apps","pages","forms","test web","just","Bash","browse","data","web","test","research","screenshots"]