skills.rest
oci-ai-incubations
oci-ai-incubationsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

diagnosing-stack

Analyze job logs, cluster state, pod events, and Helm releases to diagnose failed ORM stack deployments.

3|2|Updated Sep 25, 2025
Search Tags:#logs#kubernetes#orm#diagnostics#helm#oci
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill diagnosing-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-stack
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/diagnosing-stack
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill diagnosing-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate failed ORM stack deployments by analyzing job logs, cluster state, pod events, and Helm releases. This skill maps errors to known patterns with specific recommended fixes. Reports only, never acts autonomously.

Core Features & Use Cases

  • Investigates ORM stack failures by inspecting stack details, logs, cluster state, pod events, and Helm releases.
  • Maps errors to known patterns and provides recommended fixes without performing any actions.
  • Suitable for failed stack applies or user questions like "why did this fail" or "diagnose this stack" to produce a read-only diagnostic report.

Quick Start

Provide the ORM stack OCID or display name to initiate a diagnostic analysis and receive a read-only report.

Frequently Asked Questions about diagnosing-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a failed ORM stack deployment on Kubernetes?▼

To diagnose a failed ORM stack deployment, you provide the stack OCID or display name. The skill analyzes job logs, cluster state, pod events, and Helm releases to map errors to known patterns and generate a read-only diagnostic report with recommended fixes.

What is the best way to find out why my Helm release failed to deploy?▼

The best way to find out why your Helm release failed is to run a diagnostic analysis. This investigates stack details, cluster state, and pod events to map errors to known patterns and provide specific recommended fixes without performing any actions.

Can I use this diagnostic tool to automatically fix failed stack applies?▼

No, you cannot use this diagnostic tool to automatically fix failed stack applies. It maintains a strict read-only stance and focuses on mapping errors to known patterns with suggested fixes, never taking mutating actions autonomously.

What Kubernetes logs and events do I need to diagnose ORM stack failures?▼

You need to provide the ORM stack OCID or display name to start. The diagnostic process then automatically gathers and analyzes the necessary job logs, cluster state, pod events, and Helm releases to produce a comprehensive diagnostic report.

Does the diagnostic report explain what causes my ORM stack apply to fail?▼

Yes, the diagnostic report explains what causes your ORM stack apply to fail. It investigates failed deployments by inspecting logs, cluster state, and Helm releases, mapping the discovered errors to known patterns with specific recommended fixes.

Related Skills

Explore More Software Engineering Skills→
eveldeveld
10

k8s-query

Query Kubernetes resources to determine cluster state and resource health.

Community
Intermediate
cajiascajias

infrastructure-gap-analysis

Analyzes infrastructure and CDK implementations for deployment, runtime, integration, and compliance gaps.

Community
Advanced
ankraioankraio
26

ankra-stacks-addons

Coordinate deployment order of Ankra Stacks with Helm addons, manifests, and variables.

Official
Advanced
dmzoneilldmzoneill
2

investigate-alert

Investigate firing Prometheus alerts by gathering pod health, events, and Kibana logs.

Community
Advanced