teardown

Deletes Webex Calling resources in dependency-safe order using the wxcli CLI.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/achobgood/wxops --skill teardown-achobgood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: teardown
Source: https://github.com/achobgood/wxops/tree/main/.claude/skills/teardown
Command: npx skills add https://github.com/achobgood/wxops --skill teardown-achobgood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deleting Webex Calling resources fails with confusing 409 errors when dependencies are removed in the wrong order, leaving orphaned locations, blocked phone numbers, and half-cleaned orgs that operators mistakenly believe require manual Control Hub intervention. ## Core Features & Use Cases - Automated batch cleanup: Runs wxcli cleanup with dry-run support to inventory and delete resources across a 13-layer dependency order, scoped to one location, multiple locations, or an entire org. - Manual teardown procedure: Provides a seven-layer deletion sequence (features, routing, supporting resources, users, workspaces, phone numbers, locations) with exact command syntax and argument ordering. - 409 troubleshooting guide: Diagnoses eight known causes of location-delete failures, including hidden CX Essentials queues, workspaces, and calling-enabled locations resolvable via the CLI. - Use Case: After a migration test, an admin needs to reset a sandbox org. The skill runs a dry-run cleanup, excludes admin domains, then deletes all resources while protecting service accounts. ## Quick Start Ask the agent to tear down the location named "DP-HQ-Phones" with a dry run first, then execute the cleanup while excluding your admin domain.

Frequently Asked Questions about teardown

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

FAQPage Schema
How do I delete a Webex Calling location and all its resources?

Run `wxcli cleanup run --scope "Location Name" --dry-run` first to preview deletions, then re-run with `--force`. The tool deletes resources in a 13-layer dependency order, including phone number removal before location deletion.

How do I delete everything in a Webex Calling org?

Use `wxcli cleanup run --all --include-users --include-locations --force`. Always add `--exclude-user-domains` with your admin and service account domains so those accounts are preserved during the org-wide teardown.

Why does my Webex location delete return 409 being referenced?

Common causes include remaining phone numbers, hidden CX Essentials queues, workspaces, or the location still being calling-enabled. Disable calling via `wxcli location-settings create-delete-calling-location`, poll the job until COMPLETED, then retry the delete.

Can I disable Webex Calling on a location without Control Hub?

Yes. Run `wxcli location-settings create-delete-calling-location --location-id ID --location-name "NAME"`, poll the async job with `show-delete-calling-location` until COMPLETED, then `wxcli locations delete --force ID` succeeds.

How do I delete only call features and routing but keep users and devices?

Do not use `wxcli cleanup`, since it deletes devices and workspaces with no exclusion flag. Follow the manual procedure and delete only Layers 1-2: hunt groups, call queues, auto attendants, dial plans, route lists, route groups, and trunks.

Why do routing delete commands fail with unknown command errors?

Routing deletes use plural subcommand names such as `delete-route-groups` and `delete-trunks`, not singular forms. Always verify with `wxcli call-routing --help` before constructing delete commands.