Individual skill

support-console

Resolve telecom support-console decision tasks where the user provides a batch or queue payload (CSV/JSON), a strict JSON answer template, and a shared REST API at the TASK_ENV_BASE_URL for gathering evidence. Use this skill whenever the task involves service tickets, mobile support cases, enterprise incident investigations, or queue-quality classification that references a support-console API, even if the user does not explicitly name the console.

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

This skill covers the shared support-console REST API and the structured decision
workflows for resolving service tickets, mobile contact-center cases, enterprise
incident investigations, and queue-quality classification tasks.

## High-level workflow

Each task follows the same four-phase pattern:

1. **Read the payload** -- the input file (CSV, JSON, or plain text) listing the
   items that need decisions.
2. **Read the answer template** -- the JSON schema you must conform to. Every
   field, enum, and structure constraint in it is binding.