Individual skill

support-console-resolver

Resolve support-console tasks that require using a shared support console API to classify service tickets, mobile/contact-center cases, mobile-data recovery worklists, or enterprise export incidents and return strict JSON answers matching a provided answer_template.json. Use when prompts mention support operations, support-console records, same-day ticket batches, queue-quality handoff, mobile support queues, mobile data recovery, or enterprise export complaint response packages.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/codex/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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

## Workflow

1. Read the prompt, every payload file, and `answer_template.json` before calling the API.
2. Use the task's base URL exactly as provided. Confirm `/health` and `/api/catalog`, then fetch authoritative support-console records; never decide from payload wording alone.
3. Preserve the output shape, key names, enums, item ordering, numeric precision, and "return only JSON" requirement from the template.
4. For lookup and joins, use [references/support_console_rules.md](references/support_console_rules.md). For faster evidence gathering, run `scripts/fetch_support_console.py` with the task base URL and the IDs from the payload.
5. Build a small evidence table per item, apply the priority rules, compute summaries from the final decisions, and validate the JSON before answering.

## Evidence Fetching

Use the helper when several related records are needed: