destroy-stack

Destroy OCI Resource Manager stacks via OCI CLI and monitor job status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Destroy and tear down OCI Resource Manager stacks to reclaim resources and avoid ongoing costs.

Core Features & Use Cases

  • Destroy ORM stack infrastructure via OCI CLI
  • Discover active stacks when stack ID not provided
  • Validate before destruction and monitor job status

Quick Start

Provide the stack OCID to destroy, or list active stacks and select one.

Frequently Asked Questions about destroy-stack

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

FAQPage Schema
How do I destroy an OCI Resource Manager stack using the CLI?

You can destroy an OCI Resource Manager stack by providing its OCID or selecting from discovered active stacks, then executing and monitoring the destroy workflow via OCI CLI to reclaim resources and avoid ongoing costs.

What happens when I tear down an ORM stack in Oracle Cloud?

Tearing down an ORM stack reclaims provisioned resources and stops ongoing compute charges. The destroy workflow creates a job in OCI Resource Manager that systematically removes infrastructure defined in the stack configuration.

Can I list and discover active OCI stacks before destroying them?

Yes, if the stack ID is not provided, the Skill discovers active OCI stacks in your compartments so you can select a target and validate it before executing the destroy workflow.

Do I need special permissions to run a destroy job on OCI Resource Manager?

Yes, running a destroy job requires OCI CLI access, the correct compartment, the target stack ID, and specific IAM permissions to create and monitor destroy jobs in OCI Resource Manager.

What is the safest way to destroy OCI stack infrastructure and avoid ongoing costs?

The safest way to destroy OCI stack infrastructure is to validate the target stack before destruction and monitor the OCI Resource Manager job status throughout the workflow to ensure only intended resources are reclaimed.