Individual skill

telecom-support-analyst

Resolve telecom support-console tasks that involve cross-referencing tickets, accounts, outages, diagnostics, customers, lines, devices, plans, bills, contact-center cases, enterprise incidents, export runs, messages, and SLA contracts through a shared REST API. Use this skill whenever the user asks you to process a batch of support tickets, triage a contact-center case queue, prepare an enterprise incident response, classify a ticket queue for SLA handoff, resolve mobile-data recovery cases, or any task that mentions a support-console API with telecom entities.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/cc/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
Yes
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

# Telecom Support Console Analyst

## Overview

This skill covers the shared support-console REST API used across telecom operations tasks. Every task follows the same core pattern: a payload worklist identifies items to resolve, the API provides evidence for each item, and the answer template defines the exact output schema. Your job is to connect evidence to decisions without guessing.

The API is documented in [references/api-reference.md](references/api-reference.md). Read it when you need specific endpoint shapes, response fields, or entity relationships.

## The universal workflow

Every task, regardless of domain, follows these phases in order.

### Phase 1: Ingest
Back to top