Menu

Individual skill

task-group-003-fewshot-attempt-03

0upvotes

Use this for task_group_003 support-console tasks involving wireline service tickets, mobile support cases, or enterprise export incidents. It gives API lookup steps, routing rules, output-field meanings, and pitfalls learned from training inputs and answers.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_003/demonstration_skill/demonstration_skill_attempt_03/demonstration-skill/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

## Operating Rules

Use the base URL supplied by the task or harness. Check `/health` and `/api/catalog` if unsure. Do not answer from the prompt text alone: for every ticket, case, line, device, plan, outage, incident, export run, SLA, or message, query the support-console API and let the records decide.

Always start from `payloads/answer_template.json` and return only JSON in that shape. Preserve the ordering requested by the template: ticket payload order, case ascending order, and share-permission user order from the requirements file. Summaries are simple counts/totals over the decisions you output.

## Wireline Ticket Workflow

For each ticket from a CSV:

1. Fetch `/api/tickets/<ticket_id>`.
2. If the account looks invalid or unmatched, mark `FAILED`, no diagnostic, no team, blocker/route `INVALID_ACCOUNT`.
Back to top