Individual skill

support-console-ops

Resolve support-console tasks that classify tickets, queue cases, mobile recovery actions, or enterprise export complaints into strict JSON from a provided answer template. Use when the prompt references the shared support console API, ticket/case/export payloads, or asks for ordered decision rows, summaries, owners, routing, or response packages.

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

Use this skill for any task that turns support-console records into exact JSON.

## Workflow

1. Read the prompt, payload files, and answer template together.
2. Identify the task family: service tickets, queue or mobile cases, enterprise export response, or queue-quality review.
3. Use `/api/search?q=...` first when the prompt gives a name, incident code, ticket code, or symptom instead of a direct ID.
4. Open the direct record endpoints and all linked records. Load [support-console-map.md](references/support-console-map.md) for the endpoint map and field cues.
5. Fill only the template keys. Preserve input order or any ordering rule stated in the template.
6. Keep enum values exact, use the requested numeric precision, and use empty strings or zeros only where the template allows them.
7. Derive summaries by counting the finalized rows, not by guessing.
8. Return JSON only.
Back to top