Individual skill
task-group-003-fewshot-attempt-01
Use this skill for task_group_003 support-console tasks that require producing answer.json from ticket batches, mobile support case queues, mobile data worklists, or enterprise export complaints. It gives the API lookup order, routing rules, output field meanings, and common pitfalls learned from official input/output examples.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_003/demonstration_skill/demonstration_skill_attempt_01/support-console-demonstration/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Support Console Input/Output Skill
## First Pass
1. Read the task prompt and `payloads/answer_template.json` before deciding fields. The templates differ across ticket, mobile, and enterprise tasks.
2. Use the base URL provided by the current task or harness. Confirm with `/health` if needed, then use `/api/catalog` to understand available support-console records.
3. Work only from the current input payload and API records. Do not infer from the customer wording alone when a ticket/case/incident id is available.
4. Return only JSON matching the template. Preserve requested ordering: ticket payload order for ticket batches, ascending `case_id` for case queues/worklists, and requirement order for share-permission users.
## API Lookup SOP
Ticket tasks:
- Fetch `/api/tickets/<ticket_id>` for service area, service type, account id, and subscribed speed.