ERDA Runtime

• prerequisites and fallback rules:

  references/prerequisites.md

• operational reference:

  references/operations.md

• deterministic prerequisite check:

  scripts/doctor.sh

• validation prompts: see

  references/operations.md

Use This Skill For

• checking runtime health and status
• guiding deploy, restart, scale, and log-inspection workflows
• diagnosing runtime failures after deployment
• mapping service symptoms to ERDA runtime actions

Workflow

1. Verify CLI availability with the skill-local doctor script or direct probing from

   references/prerequisites.md

   .
2. If the request comes right after a pipeline run, first recover

   runtimeID

   from pipeline output or from

   runtime list

   before giving runtime commands.
3. Identify the org, project, application, environment, and runtime scope.
4. Distinguish between deployment problems, application problems, and infrastructure symptoms.
5. Prefer reversible and low-risk operational guidance first.
6. Use precise runtime language and concrete

   erda-cli

   commands where appropriate.
7. Call out missing context before suggesting destructive operations.
8. When validating the skill itself, use the command playbooks and validation prompts from the reference file.

Operational Priorities

• status and recent deployment state
• runtime logs and failing services
• resource pressure or bad scaling assumptions
• config drift between expected and actual environment

References

• Prerequisites and fallback:

  references/prerequisites.md

• Operations reference:

  references/operations.md