OpenParable
Skip to content
← Back to skills

Diagnostic Workflow

Testing & Quality
diagnostic-workflow

Diagnostic Workflow is an Agent Skill for testing & quality published in the nixopus/nixopus repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/nixopus/nixopus/blob/HEAD/api/skills/diagnostic-workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/diagnostic-workflow, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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)

  1. get_application_deployments — check deployment history and status
  2. get_deployment_logs — read build and deploy logs for errors
  3. list_containers → search_tools("container logs") → load_tool(...) → load needed tools
  4. get_container_logs — check container runtime output
  5. search_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.