Individual skill

support-console-resolution

Resolve structured support-console API tasks that ask Codex to classify service tickets, choose contact-center or mobile-data recovery operations, or prepare enterprise export-incident response JSON. Use for prompts with a shared support console base URL, payloads/answer_template.json, ticket batches, queue snapshots, mobile case worklists, diagnostics, outages, customer/line/device/bill/plan records, enterprise export runs, SLA credits, or response packages.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/opencode/fewshot_attempt_03/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
No
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 Resolution

Use this skill to produce the exact JSON object requested by a support-console task. The tasks are evidence reconciliation problems: payload files identify the work items, the API contains the authoritative records, and `answer_template.json` defines the required schema and enum vocabulary.

## Required Workflow

1. Read the prompt, every file in `payloads/`, and the current task's environment access note. Use only the listed base URL and allowed endpoints.
2. Read `payloads/answer_template.json` first. Preserve required item order from the payload unless the template explicitly says to sort.
3. Gather records from the API before deciding. Prefer exact ID lookups; use `/api/search?q=<id-or-client-name>` when an account or contact-center case does not have a direct allowed endpoint.
4. Optionally run the bundled collector:

   ```bash
   python skill/scripts/collect_support_console_evidence.py \
     --base-url "$TASK_ENV_BASE_URL" \