Menu

Individual skill

support-console-operations

0upvotes

Use this skill for support-console tasks that ask you to resolve, classify, or route telecom/service tickets, contact-center mobile cases, mobile-data recovery worklists, or enterprise export incidents using TASK_ENV_BASE_URL plus local payloads/answer_template.json. It is especially relevant when the prompt says to use a shared support console API, preserve payload order, choose next support operations, classify blockers, assemble enterprise incident evidence, compute queue summaries, and return JSON only.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/cc/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
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 Operations

Use this workflow when the task is an evidence-backed support-console decision task. The correct answer comes from the current payload files and the live support-console API, not from general troubleshooting assumptions.

## First Pass

1. Read the user prompt, every file under `payloads/`, and especially `payloads/answer_template.json`.
2. Identify the task family from the template keys:
   - `ticket_decisions`: fixed service ticket resolution or queue-quality classification.
   - `case_decisions`: mobile/contact-center case operation selection.
   - Enterprise incident fields such as `incident_id`, `failure_window`, `sla_credit_percent`, and `share_permissions`: export incident response package.
3. Use the base URL exactly as supplied in the prompt. Strip a trailing slash when building paths.
4. Start with `GET /health` and `GET /api/catalog` if endpoint names are uncertain.
5. Prefer direct lookups by IDs from the payload. Use `GET /api/search?q=<id-or-client-token>` to find linked records, especially account, bill, outage, message, and enterprise evidence.
Back to top