Individual skill

support-console

Resolve telecom support tasks using a shared support-console REST API. Use when the task involves service-ticket classification, mobile contact-center case resolution, enterprise incident investigation, queue-quality triage, mobile-data recovery, or any support-console record lookups. The skill covers accounts, tickets, diagnostics, troubleshooting, outages, customers, lines, devices, plans, bills, contact-center cases, enterprise accounts, incidents, export runs, messages, and SLA contracts.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/codex/fewshot_attempt_01/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

# Support Console

## Overview

Resolve telecom support tasks against a shared REST API. Every task includes a `<TASK_ENV_BASE_URL>` placeholder that points to the running support-console instance (typically `http://task-env:9003/`). All data must come from API responses, never from assumptions.

## Essential Rules

1. Replace `<TASK_ENV_BASE_URL>` with the actual base URL provided in the task prompt.
2. Call the API for every record the task references; do not guess values.
3. Preserve payload ordering in output arrays unless the task explicitly says otherwise.
4. Output only JSON that conforms to the provided answer template.

## API Navigation
Back to top