Menu

Individual skill

support-console-operations-solver

0upvotes

Solve support-console ticket, mobile case, and enterprise export response tasks by querying the read-only task API and filling the provided JSON template.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/naive/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 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 Operations Solver

Use this skill when a task asks you to resolve support tickets, mobile support cases, mobile-data worklists, or enterprise export complaints using a shared support-console API.

Always produce only the JSON requested by the task's provided answer template.

## Required Workflow

1. Read the task prompt, every payload file, and the answer template.
2. Read the task's environment access note for `<TASK_ENV_BASE_URL>` and allowed endpoints. Use only read-only business endpoints; never call a judge endpoint.
3. Query the API for every target record. Do not infer IDs, customer records, lines, plans, bills, diagnostics, or enterprise data from naming patterns alone.
4. Build one output object that exactly matches the answer template: same top-level keys, exact enum spellings, JSON booleans, strings for inapplicable IDs as `""`, and numeric zeros as `0.0` when a numeric amount field is present.
5. Recompute every summary count from the decisions immediately before returning.
Back to top