Individual skill
support-console-operations
Solve support-console operations tasks that require API-backed JSON decisions for service tickets, mobile cases, and enterprise export incidents.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/naive/fewshot_attempt_01/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
- operations 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 Operations Skill
Use this skill when a task asks for support-console evidence from `<TASK_ENV_BASE_URL>` and requires JSON conforming to a provided `payloads/answer_template.json`.
## Ground Rules
- Read the prompt, every payload file, and the answer template first.
- Return only valid JSON matching the template shape, field names, enum spelling, ordering requirements, and numeric precision.
- Use the support-console API as the source of truth. Do not infer from customer wording alone when API records exist.
- Use only read-only business endpoints. Do not call any judge/evaluator endpoint.
- Preserve payload order for ticket lists. Sort case decisions by ascending `case_id` when the template says so.
- Leave string IDs empty only when the template says an empty string means "not applicable".
- Compute all summary counts from the emitted decisions, not separately.
