Menu

Individual skill

support-console-solver

0upvotes

Inspect the live support-console API, follow IDs from payload files, and return only JSON that matches the supplied answer template. Use when a prompt references the shared support console, offline ticket batches, contact-center case queues, mobile-data recovery, queue-quality review, or enterprise export complaints and asks for evidence-based JSON instead of assumptions.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/deepagents/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
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 Solver

## Workflow

1. Read the prompt, payload files, and answer template first.
2. Call `/api/catalog` and trust the live catalog over any stale endpoint list in the prompt.
3. Search every payload identifier with `search?q=ID`, then fetch exact linked records for any IDs returned.
4. Ignore unrelated generated records or other matches that do not belong to the current payload.
5. Preserve payload order and fill only the fields that exist in the current template.

## Evidence Graphs

- Ticket batches: `ticket -> account -> outage -> diagnostics -> troubleshooting`
- Contact-center cases: `case -> customer -> line -> device -> bill -> plan`
Back to top