Menu

Individual skill

task-group-003-fewshot-attempt-02

0upvotes

Use this skill when solving task_group_003 support-console tasks involving residential service tickets, mobile support cases, mobile-data recovery worklists, or enterprise export-complaint response packages. It gives the learned fewshot rules, API lookup sequence, JSON field definitions, summary counting rules, and common pitfalls for this task group.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_003/demonstration_skill/demonstration_skill_attempt_02/task-group-003-support-console-io/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

# Task Group 003 Support Console SOP

Return only JSON matching the task's `payloads/answer_template.json`. Preserve any order required by the template: ticket payload order for ticket lists, ascending `case_id` for case lists, and requirement-listed order for permission users.

Use the harness-provided base URL when present; otherwise use the support-console API base URL from the task prompt. The useful endpoints are:

- `/api/tickets` and `/api/tickets/<ticket_id>`
- `/api/outages?service_area=<area>`
- `/api/diagnostics/<ticket_id>`
- `/api/troubleshooting/<ticket_id>`
- `/api/cases` and `/api/cases/<case_id>`
- `/api/lines/<line_id>`, `/api/devices/<device_id>`, `/api/plans/<plan_id>`
- `/api/enterprise/incidents/<incident_id>`
- `/api/enterprise/export-runs?incident_id=<incident_id>`
Back to top