Individual skill
support-console-resolver
Use this skill whenever a task asks you to resolve support-console work from a shared API and local payloads, including offline service tickets, queue-quality SLA handoff classifications, mobile/contact-center case decisions, mobile-data recovery worklists, or enterprise export/SLA complaint response packages. It guides API evidence gathering, support decision precedence, charge/SLA calculations, summary counts, and strict answer-template JSON output.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_003/fewshot/cc/fewshot_attempt_01/SKILL.md
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
- Instructions only
- 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
- data 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 Resolver
Use this skill for support-console tasks where the prompt provides local payload files plus a `<TASK_ENV_BASE_URL>` API. The task is usually graded by exact JSON structure, so treat the answer template and API records as the source of truth.
## Output Discipline
1. Read the prompt, `payloads/answer_template.json`, and every payload file.
2. Return only JSON, with no Markdown, comments, or explanatory text.
3. Match the template exactly: keep required keys, enum spelling, empty strings for missing IDs, `0.0`/`0.00`-style numeric values as JSON numbers, and no extra fields.
4. Preserve the order the template/prompt requests. Ticket CSV tasks usually preserve payload order; mobile case tasks often request ascending `case_id`.
5. Count summaries from the decisions you actually output. Do not count API records that are not in the payload.
6. Prefer direct API evidence over issue wording. Use the issue text only to disambiguate between evidence-supported actions.
## API Collection Pattern