Menu

Individual skill

support-console-resolution

0upvotes

Solve support-console ticket, mobile case, and enterprise export response tasks that require payload parsing plus read-only API evidence.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/naive/fewshot_attempt_02/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

# Support Console Resolution Skill

Use this skill when the task asks for JSON decisions based on local payloads and the shared support console API. The payload is only the worklist; the authoritative facts usually come from the API.

## Operating Rules

- Return only JSON matching the provided `payloads/answer_template.json`.
- Preserve the ordering required by the template: usually payload order for tickets and ascending `case_id` order for mobile cases.
- Use `<TASK_ENV_BASE_URL>` from the prompt or environment note. Check `GET /api/catalog` if endpoint names differ; use read-only business endpoints only.
- Do not infer customer/account state from prose when an API record exists. Query by the IDs in the payload, then follow related IDs.
- Prefer `GET /api/search?q=<id-or-client-name>` when a direct account endpoint is unavailable or when you need related records.
- Fill empty strings, `false`, `0.0`, and `NO_ACTION` exactly as the template specifies when a field is not applicable.
- Compute summary counts from your final per-item decisions, not separately from the payload.