wxc-calling-debug

Diagnose failing Webex Calling API calls and wxcli command errors through systematic verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Webex Calling API call fails, a configuration does not apply, or a wxcli command returns an error, this Skill walks through a structured diagnostic workflow instead of guessing at causes, preventing wasted hours chasing the wrong subsystem. ## Core Features & Use Cases - Auth-first diagnosis: Verifies token validity and OAuth scopes before anything else, since auth and scope issues cause the majority of failures. - Symptom-to-fix mapping: Matches HTTP error codes (401, 403, 404, 409, 429, 400) and SDK behaviors to likely causes and concrete fixes. - Verified root-cause reporting: Enforces a verification gate so conclusions are drawn only from observed command output, never from hypotheses. - Use Case: A wxcli call-queue show command returns a 400 error. The Skill checks the token with wxcli whoami, re-runs the command with --debug, identifies an id-kind mismatch, and confirms the fix by reading the resource back. ## Quick Start Ask the agent to debug why your failing wxcli command or Webex Calling API call is returning an error, providing the symptom or error message.

Frequently Asked Questions about wxc-calling-debug

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

FAQPage Schema
How do I debug a failing Webex Calling API call?

Start by running wxcli whoami to verify the token is valid, then re-run the failing command with the --debug flag to capture the full HTTP request and response. Auth and scope issues cause the majority of failures, so check them before investigating anything else.

Why does the Webex API return 403 Forbidden with my token?

A 403 means the token lacks the required scope for that endpoint. Admin endpoints need spark-admin scopes and a full org admin account, service apps must be authorized in Control Hub, and bot tokens cannot access admin-scoped endpoints at all.

Why do call-controls endpoints return 'Target user not authorized'?

The /telephony/calls/* endpoints require user-level OAuth, not admin or service-app tokens. The authenticated user must be a specific calling-licensed person, so authenticate with a personal or OAuth token for that user.

What does a 404 error 4008 on /people/me/ endpoints mean?

Error 4008 on my-settings endpoints means the authenticated user does not have a Webex Calling license. Test with a calling-licensed user's token rather than an admin-only token.

How do I handle 429 rate limit errors in wxcli?

wxcli does not auto-retry 429 errors in normal CLI mode. For bulk operations, use the migration engine's async pattern with a semaphore and Retry-After handling, or add sleep delays between commands in shell loops.

When should I not use this debugging skill?

Do not use it for building or configuring resources, which belongs to the appropriate config skill, or for querying current state when nothing is failing, which belongs to the query-live skill. It is strictly for diagnosing errors and unexpected behavior.