[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K2W3YK7B8GD155FVV2S1FV":3,"skill-same:01M6K2W3YK7B8GD155FVV2S1FV":63},{"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":23,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":40,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6K2W3YK7B8GD155FVV2S1FV","setup-mcp",null,"在 cosh 中添加、配置 MCP 服务器，自动转换格式并保证 JSON 正确。触发词：配置MCP、添加工具、安装MCP服务、粘贴MCP配置JSON","agentic-os-org\u002FANOLISA","agentic-os-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F326861446?v=4","01M6K2QGJPXKNJFSPNB3FYW1R3","Agentic OS","01M6K2QGQ6W3S1A9J9DR1G88NZ",665,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fai\u002Fsetup-mcp\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28],"MCP","setup","setup mcp","json","工具","2026-11-10 10:12:30",false,"---\nname: setup-mcp\ndescription: 在 cosh 中添加、配置 MCP 服务器，自动转换格式并保证 JSON 正确。触发词：配置MCP、添加工具、安装MCP服务、粘贴MCP配置JSON\nversion: 1.0.0\n---\n# 配置 MCP\n\n帮用户在 cosh 中配置 MCP 服务器。\n\n用户经常从 Claude Desktop、VS Code、GitHub README 等地方复制 MCP 配置粘贴过来，但这些格式和 cosh 不兼容——多了 `type` 字段、顶层 key 不对、甚至 JSON 本身就有语法错误。不要试图把用户粘贴的内容直接塞给验证脚本赌运气，而是从用户的输入中理解他们要配什么，然后你自己按 cosh 的格式写出正确的配置。验证脚本只用来做最后的合并写入和校验。\n\n## cosh 的配置格式\n\ncosh 不用 `type` 或 `transport` 字段——它看配置里有哪些字段来判断传输方式。这是最重要的一点，因为几乎所有外部来源的配置都会带一个 `\"type\": \"stdio\"` 之类的字段，而 cosh 不认这个。\n\n三种传输方式，由字段决定：\n\n**本地进程（stdio）较少出现**\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@modelcontextprotocol\u002Fserver-filesystem\", \"\u002FUsers\u002Fme\u002Fprojects\"],\n      \"env\": { \"DEBUG\": \"true\" }\n    }\n  }\n}\n```\n\n**远程 HTTP**——用户提到 `streamableHttp` 、`streamable`等字段就是 HTTP Streamable：\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"httpUrl\": \"https:\u002F\u002Fmcp.example.com\u002Fv1\",\n      \"headers\": { \"Authorization\": \"Bearer $MY_API_TOKEN\" }\n    }\n  }\n}\n```\n\n**远程 SSE（旧版）**—— 用户提供的  `url`  尾部是 `\u002Fsse` 字段就是 SSE：\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"url\": \"http:\u002F\u002Flocalhost:8080\u002Fsse\"\n    }\n  }\n}\n```\n\n其他可选字段（三种传输通用）：`timeout`、`trust`、`includeTools`、`excludeTools`。stdio 还可以用 `cwd`。\n\n## 怎么做\n\n### 1. 弄清用户要什么\n\n用户的输入五花八门。可能是一段 JSON、一句\"帮我配下 filesystem 的 MCP\"、一个 npm 包名、甚至一张截图。不管输入是什么形式，你需要搞清楚三件事：\n\n1. **用什么连接？** 如果用户提到了 `npx`\u002F`uvx`\u002F`node`\u002F`python`\u002F`docker` 这些命令，那就是 stdio。如果给了一个 URL，那是远程服务（HTTP 优先，除非用户明确说 SSE）。\n2. **怎么认证？** 有些服务需要 API key 或 token。如果需要，密钥用 `$VAR_NAME` 的形式引用环境变量，别把真实密钥写进配置文件。\n3. **叫什么名字？** 服务器需要一个标识名。通常可以从包名或 URL 推断出来，比如 `@modelcontextprotocol\u002Fserver-filesystem` 就叫 `filesystem`。\n\n**示例 1** — 用户说\"帮我配置 filesystem MCP\"：\n→ 你知道这是 `npx -y @modelcontextprotocol\u002Fserver-filesystem`，问用户想暴露哪个目录，然后构建配置。\n\n**示例 2** — 用户粘贴了一段 Claude Desktop 的配置：\n\n```json\n{\"mcpServers\": {\"github\": {\"type\": \"stdio\", \"command\": \"npx\", \"args\": [\"-y\", \"@modelcontextprotocol\u002Fserver-github\"], \"env\": {\"GITHUB_TOKEN\": \"ghp_xxxx\"}}}}\n```\n\n→ 从中提取有用信息：command 是 `npx`，args 是 `[\"-y\", \"@modelcontextprotocol\u002Fserver-github\"]`，需要 `GITHUB_TOKEN`。忽略 `type` 字段。注意到 token 是明文的——改成 `$GITHUB_TOKEN`，提醒用户设置环境变量。\n\n**示例 3** — 用户给了一个 URL `https:\u002F\u002Fmcp.linear.app\u002Fsse` 和一个 API key：\n→ 用户给的是 URL，先确认是 HTTP 还是 SSE。路径里有 `\u002Fsse` 说明是 SSE，和用户确认后用 `url` 字段。\n\n如果信息不够（比如不知道要连哪个服务，或者不确定认证方式），直接问用户。不要猜。\n\n### 2. 写出配置 JSON\n\n你自己构建，不要依赖脚本做格式转换。模板就这么简单：\n\nstdio → `{\"mcpServers\": {\"\u003C名称>\": {\"command\": \"...\", \"args\": [...]}}}`\nHTTP → `{\"mcpServers\": {\"\u003C名称>\": {\"httpUrl\": \"...\"}}}`\nSSE → `{\"mcpServers\": {\"\u003C名称>\": {\"url\": \"...\"}}}`\n\n需要认证就加 `headers`（远程）或 `env`（本地）。\n\n不要加 `type`、`transport`、`disabled`、`alwaysAllow`、`scope` 这些字段——cosh 不认，加了只会出问题。\n\n### 3. 写入配置文件\n\n用脚本合并写入，这样不会覆盖用户已有的其他配置：\n\n```bash\npython3 __SKILL_DIR__\u002Fscripts\u002Fvalidate_mcp.py '\u003Cjson>' --merge \u003Cconfig_path>\n```\n\n配置文件位置：\n\n- 默认写项目级：`.copilot-shell\u002Fsettings.json`（当前工作目录下）\n- 用户说\"全局\"或\"所有项目\"时写用户级：`~\u002F.copilot-shell\u002Fsettings.json`\n\n脚本会自动处理目录创建、已有配置保留和新条目合并。如果脚本报错，看错误信息自己修正 JSON 后重试，不要把错误丢给用户。\n\n### 4. 确认结果\n\n写入后跑一下检查：\n\n```bash\npython3 __SKILL_DIR__\u002Fscripts\u002Fvalidate_mcp.py --check \u003Cconfig_path>\n```\n\n没问题就告诉用户配置完成，提醒他们：\n\n- 用 `\u002Fmcp` 看服务器是否正常加载\n- 如果配置里用了 `$VAR_NAME`，确保对应的环境变量已设置\n\n## 处理各种来源的配置\n\n用户粘贴的 JSON 几乎不可能直接用。常见情况：\n\n- **Claude Desktop** 的配置带 `\"type\": \"stdio\"` → 提取 `command`\u002F`args`\u002F`env`，丢掉 `type`\n- **VS Code** 的配置顶层是 `\"servers\"` 而不是 `\"mcpServers\"` → 把内容搬到 `mcpServers` 下\n- **GitHub README** 可能带 `\"transport\": \"sse\"` → 提取 `url`\u002F`command`，丢掉 `transport`\n- **裸对象**（没有 `mcpServers` 包裹）→ 加上名称和包裹\n- **语法有错的 JSON**（尾逗号、缺引号）→ 尝试理解意图，和用户确认关键信息后自己重写\n\n核心原则：从用户输入中提取意图和关键参数，然后自己重建正确配置。\n","# 配置 MCP\n\n帮用户在 cosh 中配置 MCP 服务器。\n\n用户经常从 Claude Desktop、VS Code、GitHub README 等地方复制 MCP 配置粘贴过来，但这些格式和 cosh 不兼容——多了 `type` 字段、顶层 key 不对、甚至 JSON 本身就有语法错误。不要试图把用户粘贴的内容直接塞给验证脚本赌运气，而是从用户的输入中理解他们要配什么，然后你自己按 cosh 的格式写出正确的配置。验证脚本只用来做最后的合并写入和校验。\n\n## cosh 的配置格式\n\ncosh 不用 `type` 或 `transport` 字段——它看配置里有哪些字段来判断传输方式。这是最重要的一点，因为几乎所有外部来源的配置都会带一个 `\"type\": \"stdio\"` 之类的字段，而 cosh 不认这个。\n\n三种传输方式，由字段决定：\n\n**本地进程（stdio）较少出现**\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@modelcontextprotocol\u002Fserver-filesystem\", \"\u002FUsers\u002Fme\u002Fprojects\"],\n      \"env\": { \"DEBUG\": \"true\" }\n    }\n  }\n}\n```\n\n**远程 HTTP**——用户提到 `streamableHttp` 、`streamable`等字段就是 HTTP Streamable：\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"httpUrl\": \"https:\u002F\u002Fmcp.example.com\u002Fv1\",\n      \"headers\": { \"Authorization\": \"Bearer $MY_API_TOKEN\" }\n    }\n  }\n}\n```\n\n**远程 SSE（旧版）**—— 用户提供的  `url`  尾部是 `\u002Fsse` 字段就是 SSE：\n\n```json\n{\n  \"mcpServers\": {\n    \"mcp-name\": {\n      \"url\": \"http:\u002F\u002Flocalhost:8080\u002Fsse\"\n    }\n  }\n}\n```\n\n其他可选字段（三种传输通用）：`timeout`、`trust`、`includeTools`、`excludeTools`。stdio 还可以用 `cwd`。\n\n## 怎么做\n\n### 1. 弄清用户要什么\n\n用户的输入五花八门。可能是一段 JSON、一句\"帮我配下 filesystem 的 MCP\"、一个 npm 包名、甚至一张截图。不管输入是什么形式，你需要搞清楚三件事：\n\n1. **用什么连接？** 如果用户提到了 `npx`\u002F`uvx`\u002F`node`\u002F`python`\u002F`docker` 这些命令，那就是 stdio。如果给了一个 URL，那是远程服务（HTTP 优先，除非用户明确说 SSE）。\n2. **怎么认证？** 有些服务需要 API key 或 token。如果需要，密钥用 `$VAR_NAME` 的形式引用环境变量，别把真实密钥写进配置文件。\n3. **叫什么名字？** 服务器需要一个标识名。通常可以从包名或 URL 推断出来，比如 `@modelcontextprotocol\u002Fserver-filesystem` 就叫 `filesystem`。\n\n**示例 1** — 用户说\"帮我配置 filesystem MCP\"：\n→ 你知道这是 `npx -y @modelcontextprotocol\u002Fserver-filesystem`，问用户想暴露哪个目录，然后构建配置。\n\n**示例 2** — 用户粘贴了一段 Claude Desktop 的配置：\n\n```json\n{\"mcpServers\": {\"github\": {\"type\": \"stdio\", \"command\": \"npx\", \"args\": [\"-y\", \"@modelcontextprotocol\u002Fserver-github\"], \"env\": {\"GITHUB_TOKEN\": \"ghp_xxxx\"}}}}\n```\n\n→ 从中提取有用信息：command 是 `npx`，args 是 `[\"-y\", \"@modelcontextprotocol\u002Fserver-github\"]`，需要 `GITHUB_TOKEN`。忽略 `type` 字段。注意到 token 是明文的——改成 `$GITHUB_TOKEN`，提醒用户设置环境变量。\n\n**示例 3** — 用户给了一个 URL `https:\u002F\u002Fmcp.linear.app\u002Fsse` 和一个 API key：\n→ 用户给的是 URL，先确认是 HTTP 还是 SSE。路径里有 `\u002Fsse` 说明是 SSE，和用户确认后用 `url` 字段。\n\n如果信息不够（比如不知道要连哪个服务，或者不确定认证方式），直接问用户。不要猜。\n\n### 2. 写出配置 JSON\n\n你自己构建，不要依赖脚本做格式转换。模板就这么简单：\n\nstdio → `{\"mcpServers\": {\"\u003C名称>\": {\"command\": \"...\", \"args\": [...]}}}`\nHTTP → `{\"mcpServers\": {\"\u003C名称>\": {\"httpUrl\": \"...\"}}}`\nSSE → `{\"mcpServers\": {\"\u003C名称>\": {\"url\": \"...\"}}}`\n\n需要认证就加 `headers`（远程）或 `env`（本地）。\n\n不要加 `type`、`transport`、`disabled`、`alwaysAllow`、`scope` 这些字段——cosh 不认，加了只会出问题。\n\n### 3. 写入配置文件\n\n用脚本合并写入，这样不会覆盖用户已有的其他配置：\n\n```bash\npython3 __SKILL_DIR__\u002Fscripts\u002Fvalidate_mcp.py '\u003Cjson>' --merge \u003Cconfig_path>\n```\n\n配置文件位置：\n\n- 默认写项目级：`.copilot-shell\u002Fsettings.json`（当前工作目录下）\n- 用户说\"全局\"或\"所有项目\"时写用户级：`~\u002F.copilot-shell\u002Fsettings.json`\n\n脚本会自动处理目录创建、已有配置保留和新条目合并。如果脚本报错，看错误信息自己修正 JSON 后重试，不要把错误丢给用户。\n\n### 4. 确认结果\n\n写入后跑一下检查：\n\n```bash\npython3 __SKILL_DIR__\u002Fscripts\u002Fvalidate_mcp.py --check \u003Cconfig_path>\n```\n\n没问题就告诉用户配置完成，提醒他们：\n\n- 用 `\u002Fmcp` 看服务器是否正常加载\n- 如果配置里用了 `$VAR_NAME`，确保对应的环境变量已设置\n\n## 处理各种来源的配置\n\n用户粘贴的 JSON 几乎不可能直接用。常见情况：\n\n- **Claude Desktop** 的配置带 `\"type\": \"stdio\"` → 提取 `command`\u002F`args`\u002F`env`，丢掉 `type`\n- **VS Code** 的配置顶层是 `\"servers\"` 而不是 `\"mcpServers\"` → 把内容搬到 `mcpServers` 下\n- **GitHub README** 可能带 `\"transport\": \"sse\"` → 提取 `url`\u002F`command`，丢掉 `transport`\n- **裸对象**（没有 `mcpServers` 包裹）→ 加上名称和包裹\n- **语法有错的 JSON**（尾逗号、缺引号）→ 尝试理解意图，和用户确认关键信息后自己重写\n\n核心原则：从用户输入中提取意图和关键参数，然后自己重建正确配置。\n",{"name":5,"version":34,"description":7},"1.0.0","main","d2c8a75e03a304c97d2b049d59f85c2ef0b08519","src\u002Fos-skills\u002Fai\u002Fsetup-mcp",195,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA","https:\u002F\u002Fagentic-os.sh\u002F","https:\u002F\u002Fgithub.com\u002Fagentic-os-org","2026-11-14 23:49:17",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add agentic-os-org\u002FANOLISA --skill setup-mcp",{"tool":49,"command":50},"bunx","bunx skills add agentic-os-org\u002FANOLISA --skill setup-mcp",{"tool":52,"command":53},"pnpm","pnpm dlx skills add agentic-os-org\u002FANOLISA --skill setup-mcp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fai\u002Fsetup-mcp\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fvalidate_mcp.py","SCRIPT","脚本",3520,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fai\u002Fsetup-mcp\u002Fscripts\u002Fvalidate_mcp.py",[64,79,109,126,144,157],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":29},"01M6K30MJVPNFF4VA778AZC512","ws-ckpt","Linux 工作区快照(ws-ckpt)。用户想保存或备份工作区当前状态(\"保存一下\"、\"留个底\"、\"先备份\"), 想撤销或恢复文件改动(\"回滚\"、\"撤销\"、\"改回去\"、\"恢复到之前\"、\"刚才那版\"), 想查看、对比或删除历史版本,或要开启\u002F关闭每回合自动快照、定时快照、快照保留策略时使用。 用户没提\"快照\"、只表达保存或恢复工作区文件的意图时同样适用;用户点名 git 操作(commit、branch、reset 到某提交)时不适用。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fws-ckpt\u002Fsrc\u002Fskills\u002Fws-ckpt\u002FSKILL.md",[],[71,72,73,74,75,76,77,78],"ws ckpt","linux","commit","git","branch","reset","定时","文件",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":86,"publishedAt":29},"01M6K30G7BBZB1VCPE3NE08KZP","skillfs-mount","Help users configure, mount, and unmount a skillfs FUSE virtual filesystem on their local machine (e.g. for openclaw). Covers analyzing existing skill usage to suggest view configuration, generating skillfs-views.toml, mounting, and graceful unmount. Use this skill when the user asks to: set up skillfs, configure skill views, mount or unmount skillfs, check if skillfs is running, or get help organizing their skills directory (especially for openclaw users).","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fskillfs\u002Fdocs\u002Fskills\u002Fskillfs-mount\u002FSKILL.md",[85],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"skillfs mount","mount","virtual","get","local","existing skill","up","use","view","filesystem","toml","configure","skill usage","SET","analyzing","openclaw","machine","usage","for","when","running","directory",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":119,"publishedAt":29},"01M6K30CJW0X3V5PG4GP26TB63","test-skill","A test skill used in integration tests.","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fskillfs\u002Fcrates\u002Fskillfs-fuse\u002Ftests\u002Ffixtures\u002Ftest-skill\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,125],"test","Test Skill","true","integration tests","integration","tests",{"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":29},"01M6K304VCM7N6AR4PMYNDP3A7","storage-resize","Linux 磁盘扩容技能（RPM 包管理系统），实现云盘扩容后自动完成分区调整和文件系统扩容。支持系统盘\u002F数据盘在线扩容，适配 XFS\u002FEXT4\u002FBtrfs 文件系统。适用于 RPM 包管理的 Linux 系统（如 Alibaba Cloud Linux）。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fstorage-resize\u002FSKILL.md",[],[133,134,135,72,136,137,138,139,140,78,141,142,143],"storage resize","storage","system","cloud","operations","btrfs","ecs","aliyun","rpm","alibaba","数据",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":29},"01M6K2ZJEGANYH9TGGG25H7WVF","ktuner","内核参数自动调优。分析系统配置，输出调优建议并可一键应用，支持自动回滚。使用场景：系统性能优化、安全加固、内核参数诊断。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fktuner\u002FSKILL.md",[],[146,151,152,153,154,155,156],"core","run","Production","shell","安全","command",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":29},"01M6K2ZD5K40XCX8R1EA85MS7P","backup-restore","处理所有备份与恢复任务，覆盖四个层面：工作区（项目\u002F数据库\u002F代码）、用户数据（家目录\u002Fdotfiles\u002F密钥）、操作系统（全量系统\u002F磁盘镜像\u002FLVM 快照）、阿里云快照（云盘快照\u002F自动策略\u002F跨地域复制\u002F整机镜像）。适用于 RPM 包管理的 Linux 系统（如 Alibaba Cloud Linux）纯命令行环境，使用 yum 包管理器。当用户提到备份、恢复、快照、归档、回滚、克隆、迁移、容灾等任何涉及数据保存或恢复的请求时触发此技能，即使请求看起来很简单也应使用。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fbackup-restore\u002FSKILL.md",[],[164,165,166,136,167,168,169,141,142,170,143,171,172,72,140],"backup restore","backup","restore","beta","release","lvm","runtime","maintenance","dotfiles"]