Individual skill

support-console-resolver

Resolve telecom support-console tickets, cases, and enterprise incidents by querying a shared REST API and producing structured JSON decisions from an answer template. Use this skill whenever the task involves a support console base URL (paths like /api/tickets, /api/diagnostics, /api/outages, /api/cases, /api/enterprise/incidents), resolving service tickets from CSV or JSON batches, triaging contact-center or mobile-data cases, investigating enterprise export failures, auditing queue quality before SLA handoff, or any workflow that requires looking up support-console API records and filling out a provided decision template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/opencode/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 Resolver

How to navigate a telecom support console API, resolve tickets, cases, and
enterprise incidents from records rather than assumptions, and produce decisions
that conform to a provided answer template.

## Core Principles

**Every decision is an API lookup, never a guess.** The reported issue text in
a payload gives you a starting point, but the resolution must come from the API
records. When you see a ticket, case, or incident identifier, fetch its full
record. Then follow every cross-reference it contains.

**Parallelize all independent fetches.** When you have a batch of N items,
Back to top