Individual skill

support-console-ops

Telecom support console operations — resolve offline service tickets, contact-center mobile cases, enterprise export incidents, queue quality reviews, and mobile data recovery worklists by querying the support console REST API and applying domain-specific decision frameworks. Use when the task provides a batch JSON/CSV of tickets, cases, or work items against the support console and asks for structured resolution JSON.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/deepagents/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Support Console Operations

Resolve telecom support tasks by querying the support console API and applying
domain decision logic. Always fetch live records — never guess from ticket
summaries alone.

## Quick Start

1. **Get the catalog first:** `GET <BASE_URL>/api/catalog` confirms available
   endpoints and gives context on the data shape.
2. **Read the payload** (CSV or JSON) to understand the task type and how
   many items need resolution.
3. **Read the answer template** from the payload's `answer_template.json` —
   every field in that template must be populated exactly.