[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K2WSZV0N25VJCVR0YMYK3S":3,"skill-same:01M6K2WSZV0N25VJCVR0YMYK3S":113},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":62,"ownerDescription":6,"updatedAt":64,"install":65,"resources":78},"01M6K2WSZV0N25VJCVR0YMYK3S","alibabacloud-sysom-diagnosis",null,"Use when troubleshooting Linux server performance or stability issues — CPU saturation, high load, scheduling delay, memory pressure, OOM events, high RSS, page cache \u002F shared memory growth, memory cgroup residue, Java heap issues, disk IO saturation or latency, packet loss, network jitter, or a server that is slow, stuck, or unstable. Performs diagnosis and surfaces recommendations; does not apply fixes automatically.","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\u002Fdevops\u002Fsysom-diagnosis\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"alibabacloud sysom diagnosis","diagnosis","jitter","when","heap","remote","CPU","china","io","shared","saturation","cli","Bash","team","disk","credentials","kong","server","issues","performance","memory","2026-11-10 10:12:30",false,"---\nname: alibabacloud-sysom-diagnosis\ndescription: >\n  Use when troubleshooting Linux server performance or stability issues —\n  CPU saturation, high load, scheduling delay, memory pressure, OOM events,\n  high RSS, page cache \u002F shared memory growth, memory cgroup residue, Java\n  heap issues, disk IO saturation or latency, packet loss, network jitter,\n  or a server that is slow, stuck, or unstable. Performs diagnosis and\n  surfaces recommendations; does not apply fixes automatically.\nlicense: Apache-2.0\ncompatibility: >\n  Requires sysom-osops CLI. Remote diagnosis requires Alibaba Cloud credentials\n  through AK\u002FSK or an ECS RAM Role, an online Cloud Assistant on the target ECS,\n  and a supported China Mainland or Hong Kong region.\nmetadata:\n  domain: aiops\n  product: sysom\n  supported_domains:\n    - cpu\n    - io\n    - memory\n    - network\n    - java\n  owner: sysom-team\n  contact: sysom-team@alibaba-inc.com\nallowed-tools: Bash Read\n---\n\n# alibabacloud-sysom-diagnosis\n\nUse SysOM CLI and backend envelopes as the diagnosis source of truth. This Skill\nreplaces the older SysOM diagnosis Skill and is the single entry point for SysOM\nECS performance and stability diagnosis.\n\n## Immediate Route\n\nWhen the user reports a symptom and has not provided fresh SysOM envelope output,\nrun the matching SysOM command from **Domain Routing** below before ad hoc Linux\ninspection or manual probing. Then follow the returned `agent.summary`,\n`agent.findings[].detail\u002Fcategory`, and `agent.next_steps[]`. Raw Linux commands\nare bounded fallbacks only when a SysOM command is unavailable, outputs\ncontradict each other, or a required entity remains missing after the focused\nSysOM command.\n\n## Credential Security\n\nNever print, echo, or ask for AccessKey ID or AccessKey Secret values. Remote\ncommands perform their own authentication checks. If a command returns an\nauthentication or permission error, explain the error and point the user to\n`references\u002Fram-policies.md`; credential setup must happen outside the\nconversation.\n\n## CLI Setup\n\nCheck whether the CLI is available:\n\n```bash\ncommand -v sysom-osops\n```\n\nIf it is missing, install it:\n\n```bash\ncurl -fsSL --connect-timeout 1000 https:\u002F\u002Fsysom-prd-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com\u002Fsysom_prd\u002Fskill_cli\u002Finstall.sh | sudo bash\n```\n\nThen verify only the binary:\n\n```bash\ncommand -v sysom-osops\n```\n\n## Core Workflow\n\n1. Classify the user's symptom into one SysOM domain: memory, IO, load\u002FCPU,\n   network, or Java memory.\n2. Run the smallest SysOM command that matches that domain. Prefer a local\n   memory classify for unclear memory symptoms; for other domains, use the\n   matching documented remote action.\n3. Read only the default envelope fields: `ok`, `error`, `command`, and\n   `agent`.\n4. Build the answer from `agent.summary`, `agent.findings[].detail`,\n   `agent.findings[].category`, and `agent.next_steps[]`. Keep evidence\n   qualifiers that change interpretation, including currentness, unavailable\n   direct signals, fallback evidence, and remediation preconditions.\n5. If the root cause, key entities, evidence strength, and safe next action are\n   already visible, stop and answer. Run one targeted follow-up only when a\n   required entity is missing or the command explicitly recommends it.\n\nWhen classify returns a command in `agent.next_steps[]` and no root-cause\nfinding already contains enough evidence to answer, run the first command next.\nDo not replace an Agent-visible SysOM next step with manual shell probing. Raw\nLinux checks are bounded fallbacks after the SysOM next step succeeds, fails, or\ntimes out.\n\nUse the documented commands exactly as shown by default. Do not add raw,\ndebug, or backend evidence expansion flags unless the user explicitly asks for\nthat view.\n\nFinal answers should name evidence, root cause, owner\u002Fscope, and operational\naction targets. Do not add shell snippets for verification or remediation unless\nthe user explicitly asks for commands. Prefer phrases such as \"review dependency\nand disable or upgrade the leaking component in a change window\" over raw module,\ncgroup, sysctl, cache-drop, or process-kill commands.\nDo not include command-looking inline snippets such as module inspection\u002Fremoval,\nmemory summary commands, cgroup file writes, cache-drop controls, sysctl changes,\nor process-kill commands as default final-answer steps.\n\nThe `agent` view must be self-contained for diagnosis. Structured evidence is a\nbackend\u002FUI view and must not be treated as the default Agent source for required\nentities.\n\n## Domain Routing\n\n| User symptom | First route |\n|--------------|-------------|\n| Unclear memory issue, OOM, high RSS, file cache, shmem\u002Ftmpfs, memory cgroup, socket memory, kernel memory | `sysom-osops memory classify` |\n| Java heap, GC, or JVM memory issue | `sysom-osops memory javamem` when Java is explicit; otherwise start with `memory classify` |\n| Slow disk, high iowait, disk latency, blocked IO | `sysom-osops io iofsstat`, then `io iodiagnose` if the overview points to slow IO |\n| High load, runqueue backlog, task stuck waiting for CPU | `sysom-osops load loadtask` or `load delay` based on the visible symptom |\n| Packet loss, retransmits, network timeout, jitter | `sysom-osops net packetdrop` for loss\u002Fdrop symptoms; `net netjitter` for latency fluctuation |\n\nFor command parameters, read `references\u002Fdeep-actions.md` and\n`references\u002Fparameter-guide.md`. For OS and region support, read\n`references\u002Fsupported-environments.md`. These references are Skill material; do\nnot use remote target file tools to open `.claude\u002Fskills` paths on the diagnosed\nhost.\n\n## Memory Routing\n\nMemory follows the same Core Workflow and Follow-up Rules as every domain: start\nfrom `sysom-osops memory classify`, then pick the next action from visible output\nor `agent.next_steps[]`. For choosing among memory deep actions or checking which\nentity is still missing, load `references\u002Fmemory-triage.md` (parallel to\n`references\u002Fnon-memory-triage.md` for other domains).\n\nChoose the next memory action from visible SysOM output. Do not infer a memory mechanism from symptom wording alone.\n\n## Envelope Contract\n\nDefault command output is the Agent contract:\n\n```json\n{\n  \"ok\": true,\n  \"command\": \"sysom-osops memory classify\",\n  \"agent\": {\n    \"status\": \"warning\",\n    \"summary\": \"Concise diagnosis summary.\",\n    \"findings\": [\n      {\n        \"severity\": \"high\",\n        \"title\": \"Short finding title\",\n        \"detail\": \"Root cause, key entities, and evidence summary.\",\n        \"category\": \"root_cause\"\n      }\n    ],\n    \"next_steps\": [\n      {\n        \"kind\": \"command\",\n        \"label\": \"Run focused deep diagnosis\",\n        \"command\": \"sysom-osops memory oom\",\n        \"reason\": \"The missing entity this command can fill.\"\n      }\n    ]\n  }\n}\n```\n\n`agent.findings[]` may contain only `severity`, `title`, `detail`, and\n`category`. Required entities such as PID, cgroup, service, file path, OOM\nvictim, limit\u002Fcurrent, residue, holder, or cleanup target must be written in\n`agent.summary` or `agent.findings[].detail`.\n\n## Follow-up Rules\n\n- Prefer `category=root_cause`, then highest severity, then the finding that\n  best matches the user's reported symptom.\n- Treat `root_cause` as stop-ready when visible `detail` contains the entities\n  needed to explain the symptom and a safe next action.\n- Treat `agent.next_steps[]` as a priority plan, not a checklist.\n- Run another SysOM command only when it can fill a named missing entity or\n  change remediation.\n- Preserve visible qualifiers that affect interpretation, such as current versus\n  historical evidence, unavailable direct signals, fallback evidence used to\n  close currentness, and safety preconditions for remediation.\n- When a finding uses fallback evidence because a direct signal is unavailable,\n  state both parts in the final answer. Do not reduce the conclusion to the\n  fallback metric alone.\n- After a focused SysOM command closes a root cause, answer from it. Do not run\n  extra commands to make the report comprehensive, and do not chase earlier\n  classify anomalies or observations unless they share the same entity and\n  expose a named evidence gap.\n- Do not call backend-only collectors or private helper commands directly.\n- Do not re-check a PID, cgroup, file, limit, or event that SysOM already named\n  in `summary` or `detail`.\n- After a SysOM deep command returns `category=root_cause` with the required\n  entities visible, answer from that envelope. Raw Linux checks are only for\n  contradictions, command errors, or a clearly missing entity.\n- In the final answer, do not turn already-closed entities into extra raw Linux\n  verification commands. Express remediation as dependency-aware action targets\n  and change-window plans unless the envelope itself provides an executable safe\n  next step.\n- Avoid executable shell snippets in the final answer. If a command is useful\n  only for post-change verification, name the SysOM check or metric to re-run\n  instead of raw Linux commands.\n- This includes inline command names for module inspection\u002Fremoval, memory\n  summary commands, cgroup file writes, cache-drop controls, sysctl changes, and\n  process-kill actions; describe the dependency gate and operational action\n  target in prose.\n- Pivot across domains when the current envelope does not explain the reported\n  symptom and another SysOM domain names a stronger root cause.\n- During diagnosis, do not execute remediation commands that change target\n  state, such as killing processes, removing files, changing sysctl values, or\n  writing to cache-drop controls. Present those as recommendations unless the\n  user explicitly asks you to perform the repair.\n- For non-memory findings, keep the same rule: one focused deep command, then\n  answer when the required entities are visible.\n\n## Error Handling\n\n| `error.code` | Action |\n|--------------|--------|\n| `Sysom.TargetRequired` | Ask for instance ID and region, or explain ECS metadata auto-detection requirements |\n| `Sysom.FallbackClassify` | Present the local classify result and continue only if a focused next step is available |\n| `Sysom.PermissionDenied` | Use `references\u002Fram-policies.md` to explain required RAM permissions |\n| `Sysom.AuthenticationFailure` | Ask the user to configure credentials outside this session |\n| `Sysom.InvalidParameter` | Ask the user to correct the instance, region, or command parameter |\n| `Sysom.DiagnosisVersionNotSupported` | Explain that the target instance diagnosis components need an update |\n| `Sysom.DiagnosisJsonParseFailed` | Retry once only when the user still needs the same evidence |\n| `Sysom.PollError` | Retry the same focused action once when the missing evidence is still required |\n\n## References\n\n| Reference | Use when |\n|-----------|----------|\n| `references\u002Fclassify-output-guide.md` | Reading local memory classify output |\n| `references\u002Fmemory-triage.md` | Choosing a memory deep action or checking memory entity completeness |\n| `references\u002Fnon-memory-triage.md` | Routing IO, load\u002FCPU, network, and Java diagnosis |\n| `references\u002Fdeep-actions.md` | Looking up SysOM commands by domain |\n| `references\u002Fparameter-guide.md` | Validating command parameters |\n| `references\u002Freport-interpretation.md` | Interpreting envelope fields and answer shape |\n| `references\u002Fram-policies.md` | Explaining RAM permissions |\n| `references\u002Fsupported-environments.md` | Checking OS, architecture, and region support |\n","# alibabacloud-sysom-diagnosis\n\nUse SysOM CLI and backend envelopes as the diagnosis source of truth. This Skill\nreplaces the older SysOM diagnosis Skill and is the single entry point for SysOM\nECS performance and stability diagnosis.\n\n## Immediate Route\n\nWhen the user reports a symptom and has not provided fresh SysOM envelope output,\nrun the matching SysOM command from **Domain Routing** below before ad hoc Linux\ninspection or manual probing. Then follow the returned `agent.summary`,\n`agent.findings[].detail\u002Fcategory`, and `agent.next_steps[]`. Raw Linux commands\nare bounded fallbacks only when a SysOM command is unavailable, outputs\ncontradict each other, or a required entity remains missing after the focused\nSysOM command.\n\n## Credential Security\n\nNever print, echo, or ask for AccessKey ID or AccessKey Secret values. Remote\ncommands perform their own authentication checks. If a command returns an\nauthentication or permission error, explain the error and point the user to\n`references\u002Fram-policies.md`; credential setup must happen outside the\nconversation.\n\n## CLI Setup\n\nCheck whether the CLI is available:\n\n```bash\ncommand -v sysom-osops\n```\n\nIf it is missing, install it:\n\n```bash\ncurl -fsSL --connect-timeout 1000 https:\u002F\u002Fsysom-prd-cn-hangzhou.oss-cn-hangzhou.aliyuncs.com\u002Fsysom_prd\u002Fskill_cli\u002Finstall.sh | sudo bash\n```\n\nThen verify only the binary:\n\n```bash\ncommand -v sysom-osops\n```\n\n## Core Workflow\n\n1. Classify the user's symptom into one SysOM domain: memory, IO, load\u002FCPU,\n   network, or Java memory.\n2. Run the smallest SysOM command that matches that domain. Prefer a local\n   memory classify for unclear memory symptoms; for other domains, use the\n   matching documented remote action.\n3. Read only the default envelope fields: `ok`, `error`, `command`, and\n   `agent`.\n4. Build the answer from `agent.summary`, `agent.findings[].detail`,\n   `agent.findings[].category`, and `agent.next_steps[]`. Keep evidence\n   qualifiers that change interpretation, including currentness, unavailable\n   direct signals, fallback evidence, and remediation preconditions.\n5. If the root cause, key entities, evidence strength, and safe next action are\n   already visible, stop and answer. Run one targeted follow-up only when a\n   required entity is missing or the command explicitly recommends it.\n\nWhen classify returns a command in `agent.next_steps[]` and no root-cause\nfinding already contains enough evidence to answer, run the first command next.\nDo not replace an Agent-visible SysOM next step with manual shell probing. Raw\nLinux checks are bounded fallbacks after the SysOM next step succeeds, fails, or\ntimes out.\n\nUse the documented commands exactly as shown by default. Do not add raw,\ndebug, or backend evidence expansion flags unless the user explicitly asks for\nthat view.\n\nFinal answers should name evidence, root cause, owner\u002Fscope, and operational\naction targets. Do not add shell snippets for verification or remediation unless\nthe user explicitly asks for commands. Prefer phrases such as \"review dependency\nand disable or upgrade the leaking component in a change window\" over raw module,\ncgroup, sysctl, cache-drop, or process-kill commands.\nDo not include command-looking inline snippets such as module inspection\u002Fremoval,\nmemory summary commands, cgroup file writes, cache-drop controls, sysctl changes,\nor process-kill commands as default final-answer steps.\n\nThe `agent` view must be self-contained for diagnosis. Structured evidence is a\nbackend\u002FUI view and must not be treated as the default Agent source for required\nentities.\n\n## Domain Routing\n\n| User symptom | First route |\n|--------------|-------------|\n| Unclear memory issue, OOM, high RSS, file cache, shmem\u002Ftmpfs, memory cgroup, socket memory, kernel memory | `sysom-osops memory classify` |\n| Java heap, GC, or JVM memory issue | `sysom-osops memory javamem` when Java is explicit; otherwise start with `memory classify` |\n| Slow disk, high iowait, disk latency, blocked IO | `sysom-osops io iofsstat`, then `io iodiagnose` if the overview points to slow IO |\n| High load, runqueue backlog, task stuck waiting for CPU | `sysom-osops load loadtask` or `load delay` based on the visible symptom |\n| Packet loss, retransmits, network timeout, jitter | `sysom-osops net packetdrop` for loss\u002Fdrop symptoms; `net netjitter` for latency fluctuation |\n\nFor command parameters, read `references\u002Fdeep-actions.md` and\n`references\u002Fparameter-guide.md`. For OS and region support, read\n`references\u002Fsupported-environments.md`. These references are Skill material; do\nnot use remote target file tools to open `.claude\u002Fskills` paths on the diagnosed\nhost.\n\n## Memory Routing\n\nMemory follows the same Core Workflow and Follow-up Rules as every domain: start\nfrom `sysom-osops memory classify`, then pick the next action from visible output\nor `agent.next_steps[]`. For choosing among memory deep actions or checking which\nentity is still missing, load `references\u002Fmemory-triage.md` (parallel to\n`references\u002Fnon-memory-triage.md` for other domains).\n\nChoose the next memory action from visible SysOM output. Do not infer a memory mechanism from symptom wording alone.\n\n## Envelope Contract\n\nDefault command output is the Agent contract:\n\n```json\n{\n  \"ok\": true,\n  \"command\": \"sysom-osops memory classify\",\n  \"agent\": {\n    \"status\": \"warning\",\n    \"summary\": \"Concise diagnosis summary.\",\n    \"findings\": [\n      {\n        \"severity\": \"high\",\n        \"title\": \"Short finding title\",\n        \"detail\": \"Root cause, key entities, and evidence summary.\",\n        \"category\": \"root_cause\"\n      }\n    ],\n    \"next_steps\": [\n      {\n        \"kind\": \"command\",\n        \"label\": \"Run focused deep diagnosis\",\n        \"command\": \"sysom-osops memory oom\",\n        \"reason\": \"The missing entity this command can fill.\"\n      }\n    ]\n  }\n}\n```\n\n`agent.findings[]` may contain only `severity`, `title`, `detail`, and\n`category`. Required entities such as PID, cgroup, service, file path, OOM\nvictim, limit\u002Fcurrent, residue, holder, or cleanup target must be written in\n`agent.summary` or `agent.findings[].detail`.\n\n## Follow-up Rules\n\n- Prefer `category=root_cause`, then highest severity, then the finding that\n  best matches the user's reported symptom.\n- Treat `root_cause` as stop-ready when visible `detail` contains the entities\n  needed to explain the symptom and a safe next action.\n- Treat `agent.next_steps[]` as a priority plan, not a checklist.\n- Run another SysOM command only when it can fill a named missing entity or\n  change remediation.\n- Preserve visible qualifiers that affect interpretation, such as current versus\n  historical evidence, unavailable direct signals, fallback evidence used to\n  close currentness, and safety preconditions for remediation.\n- When a finding uses fallback evidence because a direct signal is unavailable,\n  state both parts in the final answer. Do not reduce the conclusion to the\n  fallback metric alone.\n- After a focused SysOM command closes a root cause, answer from it. Do not run\n  extra commands to make the report comprehensive, and do not chase earlier\n  classify anomalies or observations unless they share the same entity and\n  expose a named evidence gap.\n- Do not call backend-only collectors or private helper commands directly.\n- Do not re-check a PID, cgroup, file, limit, or event that SysOM already named\n  in `summary` or `detail`.\n- After a SysOM deep command returns `category=root_cause` with the required\n  entities visible, answer from that envelope. Raw Linux checks are only for\n  contradictions, command errors, or a clearly missing entity.\n- In the final answer, do not turn already-closed entities into extra raw Linux\n  verification commands. Express remediation as dependency-aware action targets\n  and change-window plans unless the envelope itself provides an executable safe\n  next step.\n- Avoid executable shell snippets in the final answer. If a command is useful\n  only for post-change verification, name the SysOM check or metric to re-run\n  instead of raw Linux commands.\n- This includes inline command names for module inspection\u002Fremoval, memory\n  summary commands, cgroup file writes, cache-drop controls, sysctl changes, and\n  process-kill actions; describe the dependency gate and operational action\n  target in prose.\n- Pivot across domains when the current envelope does not explain the reported\n  symptom and another SysOM domain names a stronger root cause.\n- During diagnosis, do not execute remediation commands that change target\n  state, such as killing processes, removing files, changing sysctl values, or\n  writing to cache-drop controls. Present those as recommendations unless the\n  user explicitly asks you to perform the repair.\n- For non-memory findings, keep the same rule: one focused deep command, then\n  answer when the required entities are visible.\n\n## Error Handling\n\n| `error.code` | Action |\n|--------------|--------|\n| `Sysom.TargetRequired` | Ask for instance ID and region, or explain ECS metadata auto-detection requirements |\n| `Sysom.FallbackClassify` | Present the local classify result and continue only if a focused next step is available |\n| `Sysom.PermissionDenied` | Use `references\u002Fram-policies.md` to explain required RAM permissions |\n| `Sysom.AuthenticationFailure` | Ask the user to configure credentials outside this session |\n| `Sysom.InvalidParameter` | Ask the user to correct the instance, region, or command parameter |\n| `Sysom.DiagnosisVersionNotSupported` | Explain that the target instance diagnosis components need an update |\n| `Sysom.DiagnosisJsonParseFailed` | Retry once only when the user still needs the same evidence |\n| `Sysom.PollError` | Retry the same focused action once when the missing evidence is still required |\n\n## References\n\n| Reference | Use when |\n|-----------|----------|\n| `references\u002Fclassify-output-guide.md` | Reading local memory classify output |\n| `references\u002Fmemory-triage.md` | Choosing a memory deep action or checking memory entity completeness |\n| `references\u002Fnon-memory-triage.md` | Routing IO, load\u002FCPU, network, and Java diagnosis |\n| `references\u002Fdeep-actions.md` | Looking up SysOM commands by domain |\n| `references\u002Fparameter-guide.md` | Validating command parameters |\n| `references\u002Freport-interpretation.md` | Interpreting envelope fields and answer shape |\n| `references\u002Fram-policies.md` | Explaining RAM permissions |\n| `references\u002Fsupported-environments.md` | Checking OS, architecture, and region support |\n",{"name":5,"license":15,"metadata":45,"description":54,"allowed-tools":55,"compatibility":56},{"owner":46,"domain":47,"contact":48,"product":49,"supported_domains":50},"sysom-team","aiops","sysom-team@alibaba-inc.com","sysom",[51,27,39,52,53],"cpu","network","java","Use when troubleshooting Linux server performance or stability issues — CPU saturation, high load, scheduling delay, memory pressure, OOM events, high RSS, page cache \u002F shared memory growth, memory cgroup residue, Java heap issues, disk IO saturation or latency, packet loss, network jitter, or a server that is slow, stuck, or unstable. Performs diagnosis and surfaces recommendations; does not apply fixes automatically.\n","Bash Read","Requires sysom-osops CLI. Remote diagnosis requires Alibaba Cloud credentials through AK\u002FSK or an ECS RAM Role, an online Cloud Assistant on the target ECS, and a supported China Mainland or Hong Kong region.\n","main","d2c8a75e03a304c97d2b049d59f85c2ef0b08519","src\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add agentic-os-org\u002FANOLISA --skill alibabacloud-sysom-diagnosis",{"tool":71,"command":72},"bunx","bunx skills add agentic-os-org\u002FANOLISA --skill alibabacloud-sysom-diagnosis",{"tool":74,"command":75},"pnpm","pnpm dlx skills add agentic-os-org\u002FANOLISA --skill alibabacloud-sysom-diagnosis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002FSKILL.md",true,[79,85,89,93,97,101,105,109],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fclassify-output-guide.md","REFERENCE","参考文档",1517,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fclassify-output-guide.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdeep-actions.md",3212,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fdeep-actions.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fmemory-triage.md",5398,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fmemory-triage.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fnon-memory-triage.md",1975,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fnon-memory-triage.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fparameter-guide.md",2848,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fparameter-guide.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fram-policies.md",1221,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fram-policies.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Freport-interpretation.md",2346,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Freport-interpretation.md",{"path":110,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fsupported-environments.md",1051,"https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fdevops\u002Fsysom-diagnosis\u002Freferences\u002Fsupported-environments.md",[114,129,162,179,197,210],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":40},"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",[],[121,122,123,124,125,126,127,128],"ws ckpt","linux","commit","git","branch","reset","定时","文件",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":140,"publishedAt":40},"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",[135],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156,157,158,159,22,160,161],"skillfs mount","mount","virtual","get","local","existing skill","up","use","view","filesystem","toml","configure","skill usage","SET","analyzing","openclaw","machine","usage","for","running","directory",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":172,"publishedAt":40},"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",[168,171],{"categoryNo":169,"categoryName":170,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},[173,174,175,176,177,178],"test","Test Skill","true","integration tests","integration","tests",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":40},"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",[],[186,187,188,122,189,190,191,192,193,128,194,195,196],"storage resize","storage","system","cloud","operations","btrfs","ecs","aliyun","rpm","alibaba","数据",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":40},"01M6K2ZJEGANYH9TGGG25H7WVF","ktuner","内核参数自动调优。分析系统配置，输出调优建议并可一键应用，支持自动回滚。使用场景：系统性能优化、安全加固、内核参数诊断。","https:\u002F\u002Fgithub.com\u002Fagentic-os-org\u002FANOLISA\u002Fblob\u002Fmain\u002Fsrc\u002Fos-skills\u002Fsystem-admin\u002Fktuner\u002FSKILL.md",[],[199,204,205,206,207,208,209],"core","run","Production","shell","安全","command",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":40},"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",[],[217,218,219,189,220,221,222,194,195,223,196,224,225,122,193],"backup restore","backup","restore","beta","release","lvm","runtime","maintenance","dotfiles"]