Menu

Individual skill

support-console-resolver

0upvotes

Resolve support-console ticket, queue, mobile, and enterprise incident prompts into exact JSON. Use this whenever a task provides support-console payload files plus an answer template and asks for classified decisions, action routing, summary counts, or incident response fields, even if it does not mention the support console explicitly.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/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
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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

Use this skill when the task is a support-console batch job: the prompt gives you payload files plus an answer template, and the final deliverable is strict JSON.

## Operating rule

Treat the answer template as the contract. Preserve the requested order, fill every required field, and return JSON only.

## Workflow

1. Read the prompt, the answer template, and every payload file together.
2. Identify the schema family by its top-level keys.
3. Use the support-console API to fetch only the records needed to resolve each item.
4. Cross-check the payload IDs against the records before deciding.
Back to top