diagnostic-workflow
GitHub提供应用与容器故障的逐层诊断工作流,涵盖部署历史、构建日志、容器状态及HTTP探针检查。用于快速定位部署失败或运行时问题的根因,并按层级逐步排查直至找到根本原因。
Trigger Scenarios
Install
npx skills add nixopus/nixopus --skill diagnostic-workflow -g -y
SKILL.md
Frontmatter
{
"name": "diagnostic-workflow",
"metadata": {
"version": "1.0"
},
"description": "Layer-by-layer diagnostic workflow for application and container issues — deployment logs, container state, HTTP probes. Load when investigating a deployment failure or runtime issue."
}
Diagnostic Workflow
All tools below are runtime tools. Use search_tools / load_tool to find and load them — do NOT use skill_read or skill_search.
Diagnostic Layers (IN ORDER, stop on root cause)
get_application_deployments— check deployment history and statusget_deployment_logs— read build and deploy logs for errorslist_containers→search_tools("container logs")→load_tool(...)→ load needed toolsget_container_logs— check container runtime outputsearch_tools("http probe")→load_tool("http_probe")→ probe public URL
If the issue appears application-level, check logs layer by layer. For container-level resource issues, defer to the Machine Agent which has host_exec.
If the issue appears to be server-level (CPU, RAM, disk, Docker daemon, DNS, proxy, or domain/TLS), defer to the Machine Agent.
Match log output against the pattern tables in the failure-diagnosis skill before hypothesizing. Tool 404 → skip layer. Root cause: bold summary, evidence in code block, fix in 1-2 sentences.
Version History
- cf05d97 Current 2026-08-20 14:51


