[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77J622P4EXAX3B5580TSRGV":3,"skill-same:01M77J622P4EXAX3B5580TSRGV":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M77J622P4EXAX3B5580TSRGV","diagnosing-mcp",null,"Use to diagnose and fix ZCode MCP (Model Context Protocol) server configuration problems in the ZCode client. Applies when an MCP server will not connect, its tools (mcp__server__tool) do not appear, it shows as disabled or failed, connections time out, a command cannot be found, template variables are not expanded, or a server defined in a configuration file has no effect. Provides configuration locations, how to inspect status in Settings, common pitfalls, and a step-by-step localization and repair workflow.","raaOS\u002Fsystem_prompts_leaks","raaOS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214067397?v=4","01M77HV6K4ZTA4BZAGX00GTW6J","01M77HV6KX55HVRY679V25JXF8",0,"CC0-1.0","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FGLM\u002Fskills\u002Fdiagnosing-mcp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: diagnosing-mcp\ndescription: Use to diagnose and fix ZCode MCP (Model Context Protocol) server configuration problems in the ZCode client. Applies when an MCP server will not connect, its tools (mcp__server__tool) do not appear, it shows as disabled or failed, connections time out, a command cannot be found, template variables are not expanded, or a server defined in a configuration file has no effect. Provides configuration locations, how to inspect status in Settings, common pitfalls, and a step-by-step localization and repair workflow.\n---\n\n# Diagnosing MCP Configuration\n\nGoal: reduce any MCP problem to a single concrete file-field edit. A person inspects status from the client; an agent reads and edits the configuration files directly.\n\n> Key points that are often misunderstood: the user configuration file is `~\u002F.zcode\u002Fcli\u002Fconfig.json`; `.agents\u002Fmcp.json` is a **compatibility fallback** (read only when the same scope's `.zcode` has no MCP servers); and in the desktop client, MCP status and repair live under **Settings → MCP**.\n\n## 1. Configuration locations and precedence\n\n| Scope | File | Field |\n|---|---|---|\n| User | `~\u002F.zcode\u002Fcli\u002Fconfig.json` | `mcp.servers` |\n| User (fallback) | `~\u002F.agents\u002Fmcp.json` | `mcpServers` (used only if `~\u002F.zcode\u002Fcli\u002Fconfig.json` has no MCP servers) |\n| Workspace | `\u003Crepo>\u002F.zcode\u002Fconfig.json` or `\u003Crepo>\u002Fzcode.json` (every directory from the repository root down to the working directory is read) | `mcp.servers` |\n| Workspace (fallback) | `\u003Crepo>\u002F.agents\u002Fmcp.json` | `mcpServers` (used only if the workspace `.zcode` has no MCP servers) |\n| Plugin | `\u003CpluginRoot>\u002F.mcp.json` or the manifest's `mcpServers` field | Keys are namespaced as `plugin:\u003Cplugin>:\u003Cserver>` |\n\nWithin each scope, `.zcode` takes priority and `.agents\u002Fmcp.json` is a same-scope fallback: if that scope's `.zcode` defines any MCP server, its `.agents\u002Fmcp.json` is ignored entirely. Note the different key shape — `.zcode` uses nested `mcp.servers`, while `.agents\u002Fmcp.json` uses a top-level `mcpServers`.\n\nOverride order across scopes for a same-named server: **CLI → environment → user → workspace → system**. In short, **user overrides workspace**. Plugin-provided servers form the base layer and are overridden by explicit configuration.\n\n**Auto-connect**: MCP servers from every scope — user, **workspace**, plugin, environment, and CLI — are **trusted and connected automatically** at session start. Workspace-scoped servers were previously untrusted (reported `Project MCP server requires explicit connection before use.`); they now connect by default like any other scope. Use **Settings → MCP** as the supported client surface for inspecting status and repairing configuration.\n\n## 2. Configuration schema\n\n- `stdio`: requires `command`; optional `args[]`, `cwd`, `env`, `enabled`, `timeoutMs`.\n- `http` \u002F `sse`: requires `url`; optional `headers`, `enabled`, `timeoutMs`.\n- Standard field names are `env` for stdio environment variables and `headers` for HTTP\u002FSSE request headers. `command` is a string and `args` is an array of strings; do not paste OpenCode-style `command: [\"npx\", \"-y\", \"...\"]` into ZCode's JSON editor.\n- When `type` is omitted it is inferred: a `command` implies `stdio`, a `url` implies `http`. Legacy forms are migrated automatically when the CLI reads config directly (`type: \"remote\"` → `http`, `environment` → `env`, `enable` → `enabled`, `http_headers` → `headers`). Desktop app-managed session creation may bypass part of that CLI file parser, so prefer canonical fields (`env`, `headers`, `enabled`, `type: \"http\"`) in files that the desktop Settings → MCP page reads.\n- The configuration-file server schema is **strict**: an **unknown key causes the server to be dropped**.\n- **Template variables `${...}` are expanded only for plugin-provided MCP servers** (for example `${CLAUDE_PLUGIN_ROOT}` \u002F `${ZCODE_PLUGIN_ROOT}`, `${CLAUDE_PROJECT_DIR}`, `${user_config.KEY}`). Configuration-file MCP servers do **not** expand templates — use absolute paths there.\n- The default timeout is 30000 ms.\n\nCanonical examples:\n\n```json\n{\n  \"mcp\": {\n    \"servers\": {\n      \"mysql-local\": {\n        \"type\": \"stdio\",\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"@benborla29\u002Fmcp-server-mysql\"],\n        \"env\": {\n          \"MYSQL_HOST\": \"127.0.0.1\",\n          \"MYSQL_PORT\": \"3306\"\n        }\n      },\n      \"remote-reader\": {\n        \"type\": \"http\",\n        \"url\": \"https:\u002F\u002Fexample.com\u002Fmcp\",\n        \"headers\": {\n          \"Authorization\": \"Bearer ...\"\n        }\n      }\n    }\n  }\n}\n```\n\n## 3. How to inspect status\n\n- **List and status**: open **Settings → MCP** in the client. Each entry shows whether the server is connected, disabled, disconnected, or failed, with any error inline. Plugin-provided servers are marked as built-in. (`untrusted` is a legacy status that no longer appears for normally configured servers now that every scope auto-connects.)\n- **After edits**: restart the affected session, or restart ZCode if the Settings page still shows stale data, then reopen **Settings → MCP** to confirm the server status.\n- **Standard-I\u002FO error output** (the root cause of most failures): a stdio server's captured error stream is written to the ZCode log. To see the full output, run the server's `command` with its arguments directly in a terminal.\n\n## 4. Common pitfalls (symptom → cause → fix)\n\n1. **Workspace server does not connect** — a server defined in `\u003Crepo>\u002F.zcode\u002Fconfig.json` (or `\u003Crepo>\u002F.agents\u002Fmcp.json`) is not connecting. Workspace servers now auto-connect like any other scope, so this is no longer a trust gate — the cause is a real config or startup problem. → Check its **Settings → MCP** status: `failed` → go to step 4; absent → the config was not loaded (pitfall 5\u002F9) or it is in `.agents\u002Fmcp.json` but shadowed (pitfall 12).\n2. **`command not found`** — the server shows `failed` with an error such as `spawn npx ENOENT`. The `command` is not on `PATH`, or a relative path was not resolved. → Use an absolute path, add `cwd` when needed, and on Windows point at the `.cmd`\u002F`.exe`.\n3. **`${...}` reaches the process literally** — configuration-file MCP servers do not expand templates. → Use concrete absolute paths (templates are a plugin-only feature).\n4. **Plugin is missing an environment value or secret** — the plugin reports a missing variable. → Set the plugin's configuration value (Plugin Management → the plugin's advanced settings) or export the required environment variable; sensitive values may only be placed in `env`\u002F`headers`, not in `command`\u002F`url`.\n5. **Wrong transport type or unknown key** — the server is silently dropped. → Make `type` match the fields, remove any extra top-level keys (the schema is strict), and ensure exactly one of `command` (stdio) or `url` (http\u002Fsse) is present.\n6. **Unexpected override** — editing the workspace `mcp.servers` entry has no effect. A same-named server in the user configuration is shadowing it (user overrides workspace for MCP). → Edit the user entry, or rename one of the servers.\n7. **Connection or tool-listing timeout** — `failed ... timed out after 30000ms`. → Add `\"timeoutMs\": 60000` to that server, and address the slow startup.\n8. **Only `Connection closed` with no cause** — the error stream was not surfaced in the status line. → Check the ZCode log for the captured error output, or run the `command` with its arguments in a terminal.\n9. **JSON syntax error in the configuration file** — MCP servers (and possibly the whole file) go missing. → Validate the JSON, then fix the syntax.\n10. **Server shows as disabled** — `enabled: false` (or legacy `enable: false`). → Set `\"enabled\": true` or remove the field.\n11. **A desktop-managed server list overrides the file** — edits to configuration files have no effect because the client is supplying the MCP list. → Manage MCP through **Settings → MCP** in that context.\n12. **`.agents\u002Fmcp.json` edits have no effect, or use the wrong key** — a server added to `.agents\u002Fmcp.json` never appears. Either the same scope's `.zcode` already defines MCP servers (so `.agents\u002Fmcp.json` is ignored entirely for that scope), or the servers were placed under `mcp.servers` instead of the top-level `mcpServers` that `.agents\u002Fmcp.json` expects. → Move the definition into the `.zcode` file for that scope, or ensure that scope's `.zcode` has no MCP servers and use the top-level `mcpServers` key in `.agents\u002Fmcp.json`.\n13. **Server name appears in logs but no MCP tools appear in the model request** — the desktop app read the server entry and passed its name to the runtime, but the server failed during startup, so `toolCount` and `registeredToolCount` are zero. A common cause is a legacy `environment` field in `~\u002F.zcode\u002Fcli\u002Fconfig.json`: CLI direct config parsing can migrate it, but the desktop app-managed path currently expects `env` when converting to protocol `mcpServers`. → Rename `environment` to `env`, keep the values unchanged, restart ZCode, and reopen **Settings → MCP**.\n14. **Settings → MCP crashes after JSON editing with `command.trim is not a function`** — the saved server has a non-string `command`, usually OpenCode-style `command: [\"npx\", \"-y\", \"server\"]`. → Edit `~\u002F.zcode\u002Fcli\u002Fconfig.json` manually: set `\"command\": \"npx\"` and move the rest into `\"args\": [\"-y\", \"server\"]`, then restart the app.\n\n## 5. Localization workflow (in order; stop when the cause is found)\n\n1. Confirm MCP is enabled (it is by default).\n2. Open **Settings → MCP** and read the status: `disabled` → pitfall 10; `failed (\u003Cerror>)` → read the inline error and go to step 4; **not listed at all** → step 3. (`untrusted` should no longer appear for a normally configured server.)\n3. Verify the configuration is loaded and valid: check the JSON validity of `~\u002F.zcode\u002Fcli\u002Fconfig.json` and `\u003Crepo>\u002F.zcode\u002Fconfig.json` (and `zcode.json`) — pitfall 9. A server that is in the file but not listed failed schema validation (pitfall 5 — look for unknown keys, wrong `type`, or a missing `command`\u002F`url`); a server defined only in `.agents\u002Fmcp.json` but not appearing points to the fallback shadowing or wrong-key issue (pitfall 12).\n4. Diagnose a `failed` server: `ENOENT` → pitfall 2; `timed out` → pitfall 7; `Connection closed` → pitfall 8; an http\u002Fsse network error → check proxy\u002FCA, URL reachability, and `headers`.\n5. If **Settings → MCP** or service logs show `mcpServerCount` \u002F server names but the model request has no `mcp__...` tools, check startup logs for `mcp.startup.completed` and `mcp.tools.registered`. If `toolCount=0` with failed statuses, inspect the config field names first (`env` vs `environment`, string `command` vs array `command`) before treating it as a model-selection issue.\n6. If edits have no effect → pitfall 6 (user overrides workspace) or pitfall 11 (desktop-managed list).\n7. If a `${...}` appears literally → pitfall 3 (configuration files do not expand templates) or pitfall 4 (an unset plugin variable).\n8. Apply the concrete fix — most commonly editing `~\u002F.zcode\u002Fcli\u002Fconfig.json` at `mcp.servers.\u003Cname>` (`command` \u002F `args` \u002F `cwd` \u002F `env` \u002F `headers` \u002F `timeoutMs` \u002F `enabled`) — then restart the session (every scope auto-connects) and reopen **Settings → MCP** to confirm.\n","# Diagnosing MCP Configuration\n\nGoal: reduce any MCP problem to a single concrete file-field edit. A person inspects status from the client; an agent reads and edits the configuration files directly.\n\n> Key points that are often misunderstood: the user configuration file is `~\u002F.zcode\u002Fcli\u002Fconfig.json`; `.agents\u002Fmcp.json` is a **compatibility fallback** (read only when the same scope's `.zcode` has no MCP servers); and in the desktop client, MCP status and repair live under **Settings → MCP**.\n\n## 1. Configuration locations and precedence\n\n| Scope | File | Field |\n|---|---|---|\n| User | `~\u002F.zcode\u002Fcli\u002Fconfig.json` | `mcp.servers` |\n| User (fallback) | `~\u002F.agents\u002Fmcp.json` | `mcpServers` (used only if `~\u002F.zcode\u002Fcli\u002Fconfig.json` has no MCP servers) |\n| Workspace | `\u003Crepo>\u002F.zcode\u002Fconfig.json` or `\u003Crepo>\u002Fzcode.json` (every directory from the repository root down to the working directory is read) | `mcp.servers` |\n| Workspace (fallback) | `\u003Crepo>\u002F.agents\u002Fmcp.json` | `mcpServers` (used only if the workspace `.zcode` has no MCP servers) |\n| Plugin | `\u003CpluginRoot>\u002F.mcp.json` or the manifest's `mcpServers` field | Keys are namespaced as `plugin:\u003Cplugin>:\u003Cserver>` |\n\nWithin each scope, `.zcode` takes priority and `.agents\u002Fmcp.json` is a same-scope fallback: if that scope's `.zcode` defines any MCP server, its `.agents\u002Fmcp.json` is ignored entirely. Note the different key shape — `.zcode` uses nested `mcp.servers`, while `.agents\u002Fmcp.json` uses a top-level `mcpServers`.\n\nOverride order across scopes for a same-named server: **CLI → environment → user → workspace → system**. In short, **user overrides workspace**. Plugin-provided servers form the base layer and are overridden by explicit configuration.\n\n**Auto-connect**: MCP servers from every scope — user, **workspace**, plugin, environment, and CLI — are **trusted and connected automatically** at session start. Workspace-scoped servers were previously untrusted (reported `Project MCP server requires explicit connection before use.`); they now connect by default like any other scope. Use **Settings → MCP** as the supported client surface for inspecting status and repairing configuration.\n\n## 2. Configuration schema\n\n- `stdio`: requires `command`; optional `args[]`, `cwd`, `env`, `enabled`, `timeoutMs`.\n- `http` \u002F `sse`: requires `url`; optional `headers`, `enabled`, `timeoutMs`.\n- Standard field names are `env` for stdio environment variables and `headers` for HTTP\u002FSSE request headers. `command` is a string and `args` is an array of strings; do not paste OpenCode-style `command: [\"npx\", \"-y\", \"...\"]` into ZCode's JSON editor.\n- When `type` is omitted it is inferred: a `command` implies `stdio`, a `url` implies `http`. Legacy forms are migrated automatically when the CLI reads config directly (`type: \"remote\"` → `http`, `environment` → `env`, `enable` → `enabled`, `http_headers` → `headers`). Desktop app-managed session creation may bypass part of that CLI file parser, so prefer canonical fields (`env`, `headers`, `enabled`, `type: \"http\"`) in files that the desktop Settings → MCP page reads.\n- The configuration-file server schema is **strict**: an **unknown key causes the server to be dropped**.\n- **Template variables `${...}` are expanded only for plugin-provided MCP servers** (for example `${CLAUDE_PLUGIN_ROOT}` \u002F `${ZCODE_PLUGIN_ROOT}`, `${CLAUDE_PROJECT_DIR}`, `${user_config.KEY}`). Configuration-file MCP servers do **not** expand templates — use absolute paths there.\n- The default timeout is 30000 ms.\n\nCanonical examples:\n\n```json\n{\n  \"mcp\": {\n    \"servers\": {\n      \"mysql-local\": {\n        \"type\": \"stdio\",\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"@benborla29\u002Fmcp-server-mysql\"],\n        \"env\": {\n          \"MYSQL_HOST\": \"127.0.0.1\",\n          \"MYSQL_PORT\": \"3306\"\n        }\n      },\n      \"remote-reader\": {\n        \"type\": \"http\",\n        \"url\": \"https:\u002F\u002Fexample.com\u002Fmcp\",\n        \"headers\": {\n          \"Authorization\": \"Bearer ...\"\n        }\n      }\n    }\n  }\n}\n```\n\n## 3. How to inspect status\n\n- **List and status**: open **Settings → MCP** in the client. Each entry shows whether the server is connected, disabled, disconnected, or failed, with any error inline. Plugin-provided servers are marked as built-in. (`untrusted` is a legacy status that no longer appears for normally configured servers now that every scope auto-connects.)\n- **After edits**: restart the affected session, or restart ZCode if the Settings page still shows stale data, then reopen **Settings → MCP** to confirm the server status.\n- **Standard-I\u002FO error output** (the root cause of most failures): a stdio server's captured error stream is written to the ZCode log. To see the full output, run the server's `command` with its arguments directly in a terminal.\n\n## 4. Common pitfalls (symptom → cause → fix)\n\n1. **Workspace server does not connect** — a server defined in `\u003Crepo>\u002F.zcode\u002Fconfig.json` (or `\u003Crepo>\u002F.agents\u002Fmcp.json`) is not connecting. Workspace servers now auto-connect like any other scope, so this is no longer a trust gate — the cause is a real config or startup problem. → Check its **Settings → MCP** status: `failed` → go to step 4; absent → the config was not loaded (pitfall 5\u002F9) or it is in `.agents\u002Fmcp.json` but shadowed (pitfall 12).\n2. **`command not found`** — the server shows `failed` with an error such as `spawn npx ENOENT`. The `command` is not on `PATH`, or a relative path was not resolved. → Use an absolute path, add `cwd` when needed, and on Windows point at the `.cmd`\u002F`.exe`.\n3. **`${...}` reaches the process literally** — configuration-file MCP servers do not expand templates. → Use concrete absolute paths (templates are a plugin-only feature).\n4. **Plugin is missing an environment value or secret** — the plugin reports a missing variable. → Set the plugin's configuration value (Plugin Management → the plugin's advanced settings) or export the required environment variable; sensitive values may only be placed in `env`\u002F`headers`, not in `command`\u002F`url`.\n5. **Wrong transport type or unknown key** — the server is silently dropped. → Make `type` match the fields, remove any extra top-level keys (the schema is strict), and ensure exactly one of `command` (stdio) or `url` (http\u002Fsse) is present.\n6. **Unexpected override** — editing the workspace `mcp.servers` entry has no effect. A same-named server in the user configuration is shadowing it (user overrides workspace for MCP). → Edit the user entry, or rename one of the servers.\n7. **Connection or tool-listing timeout** — `failed ... timed out after 30000ms`. → Add `\"timeoutMs\": 60000` to that server, and address the slow startup.\n8. **Only `Connection closed` with no cause** — the error stream was not surfaced in the status line. → Check the ZCode log for the captured error output, or run the `command` with its arguments in a terminal.\n9. **JSON syntax error in the configuration file** — MCP servers (and possibly the whole file) go missing. → Validate the JSON, then fix the syntax.\n10. **Server shows as disabled** — `enabled: false` (or legacy `enable: false`). → Set `\"enabled\": true` or remove the field.\n11. **A desktop-managed server list overrides the file** — edits to configuration files have no effect because the client is supplying the MCP list. → Manage MCP through **Settings → MCP** in that context.\n12. **`.agents\u002Fmcp.json` edits have no effect, or use the wrong key** — a server added to `.agents\u002Fmcp.json` never appears. Either the same scope's `.zcode` already defines MCP servers (so `.agents\u002Fmcp.json` is ignored entirely for that scope), or the servers were placed under `mcp.servers` instead of the top-level `mcpServers` that `.agents\u002Fmcp.json` expects. → Move the definition into the `.zcode` file for that scope, or ensure that scope's `.zcode` has no MCP servers and use the top-level `mcpServers` key in `.agents\u002Fmcp.json`.\n13. **Server name appears in logs but no MCP tools appear in the model request** — the desktop app read the server entry and passed its name to the runtime, but the server failed during startup, so `toolCount` and `registeredToolCount` are zero. A common cause is a legacy `environment` field in `~\u002F.zcode\u002Fcli\u002Fconfig.json`: CLI direct config parsing can migrate it, but the desktop app-managed path currently expects `env` when converting to protocol `mcpServers`. → Rename `environment` to `env`, keep the values unchanged, restart ZCode, and reopen **Settings → MCP**.\n14. **Settings → MCP crashes after JSON editing with `command.trim is not a function`** — the saved server has a non-string `command`, usually OpenCode-style `command: [\"npx\", \"-y\", \"server\"]`. → Edit `~\u002F.zcode\u002Fcli\u002Fconfig.json` manually: set `\"command\": \"npx\"` and move the rest into `\"args\": [\"-y\", \"server\"]`, then restart the app.\n\n## 5. Localization workflow (in order; stop when the cause is found)\n\n1. Confirm MCP is enabled (it is by default).\n2. Open **Settings → MCP** and read the status: `disabled` → pitfall 10; `failed (\u003Cerror>)` → read the inline error and go to step 4; **not listed at all** → step 3. (`untrusted` should no longer appear for a normally configured server.)\n3. Verify the configuration is loaded and valid: check the JSON validity of `~\u002F.zcode\u002Fcli\u002Fconfig.json` and `\u003Crepo>\u002F.zcode\u002Fconfig.json` (and `zcode.json`) — pitfall 9. A server that is in the file but not listed failed schema validation (pitfall 5 — look for unknown keys, wrong `type`, or a missing `command`\u002F`url`); a server defined only in `.agents\u002Fmcp.json` but not appearing points to the fallback shadowing or wrong-key issue (pitfall 12).\n4. Diagnose a `failed` server: `ENOENT` → pitfall 2; `timed out` → pitfall 7; `Connection closed` → pitfall 8; an http\u002Fsse network error → check proxy\u002FCA, URL reachability, and `headers`.\n5. If **Settings → MCP** or service logs show `mcpServerCount` \u002F server names but the model request has no `mcp__...` tools, check startup logs for `mcp.startup.completed` and `mcp.tools.registered`. If `toolCount=0` with failed statuses, inspect the config field names first (`env` vs `environment`, string `command` vs array `command`) before treating it as a model-selection issue.\n6. If edits have no effect → pitfall 6 (user overrides workspace) or pitfall 11 (desktop-managed list).\n7. If a `${...}` appears literally → pitfall 3 (configuration files do not expand templates) or pitfall 4 (an unset plugin variable).\n8. Apply the concrete fix — most commonly editing `~\u002F.zcode\u002Fcli\u002Fconfig.json` at `mcp.servers.\u003Cname>` (`command` \u002F `args` \u002F `cwd` \u002F `env` \u002F `headers` \u002F `timeoutMs` \u002F `enabled`) — then restart the session (every scope auto-connects) and reopen **Settings → MCP** to confirm.\n",{"name":5,"description":7},"main","2975a5ac469614541ae22929d43b6da2635e1ee9","GLM\u002Fskills\u002Fdiagnosing-mcp","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks","https:\u002F\u002Fgithub.com\u002FraaOS","2026-11-14 21:19:17",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add raaOS\u002Fsystem_prompts_leaks --skill diagnosing-mcp",{"tool":35,"command":36},"bunx","bunx skills add raaOS\u002Fsystem_prompts_leaks --skill diagnosing-mcp",{"tool":38,"command":39},"pnpm","pnpm dlx skills add raaOS\u002Fsystem_prompts_leaks --skill diagnosing-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FGLM\u002Fskills\u002Fdiagnosing-mcp\u002FSKILL.md",true,[],[44,50,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":47,"categories":48,"keywords":49,"publishedAt":18},"01M77JV1M0ZZTZZREM9Q96TKZZ","model-council","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FPerplexity\u002Fskills\u002Fmodel-council\u002FSKILL.md",[],[],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M77JTYND3ETS9EGCX3B9CW6E","writing-style","Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwriting-style\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M77JTVWEHY80JC2H1JG1JMQB","write-page","Create or edit requested Page\u002FSpace content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwrite-page\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M77JTQ5ND23QPF6RJYJPXHSZ","software-engineering","For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fsoftware-engineering\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M77JTM3ZDPCYE8C1FW7G7S2B","slides-artifact","Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslides-artifact\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M77JTHTWZN2J27KD2H66XDBZ","slack","Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslack\u002FSKILL.md",[],[]]