Individual skill

support-console-resolver

Resolve telco support tickets, cases, and enterprise incidents by querying a shared REST API and mapping evidence to structured JSON decisions. Use when the task involves a support console API, ticket/case input payloads, and an answer template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/naive/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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 5,527 bytes
api_reference.mddoc · 4,285 bytes
decision_trees.mddoc · 7,548 bytes

Read excerpt


# Support Console Resolver

## Overview

This skill solves tasks that require querying a telco support console REST API to diagnose issues and produce structured JSON decisions. The API exposes customer, account, line, bill, plan, device, outage, diagnostic, troubleshooting, and enterprise records. Every task follows the same loop: read the input payload, fetch all relevant records from the API, apply decision rules to classify each item, fill the answer template, and emit only valid JSON.

## Workflow

### Step 1: Orient from the workspace

Read `prompt.txt` first. It tells you the analyst role, which payload file(s) to use, and where the API lives. Then read `payloads/answer_template.json` so you know the exact output schema before you touch the API. Finally, read every payload file listed in the prompt.

The API base URL is always given as `<TASK_ENV_BASE_URL>`. Substitute the actual value before making any request.