Menu

Individual skill

support-console-resolver

0upvotes

Resolve batches of support records by querying a shared REST API support console. Use when the task assigns a support operator role, provides a TASK_ENV_BASE_URL or similar API base URL, and includes payload files with records to resolve plus an answer_template.json that defines the output schema. Triggers for ticket resolution, case triage, enterprise incident response, mobile data recovery, SLA classification, and any batch-support workflow where API lookups against a support console drive structured JSON decisions. Even when the prompt is brief, trigger if it mentions a support console API, batch resolution, payloads, or enum-constrained answer templates.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/opencode/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 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 Resolver

Resolve batches of support records — tickets, cases, worklists, incidents — by querying a shared REST API support console. The solver must read the task inputs, discover the API surface, fetch the real state for each record, map that state to template decisions, and output structured JSON.

## Workflow

### 1. Orient

Read every file the task provides:

- **The prompt** — identifies the role, the API base URL (look for `<TASK_ENV_BASE_URL>` or similar), and any domain-specific requirements.
- **Payload files** — the records to resolve. These are CSV or JSON lists with entity identifiers (ticket_id, account_id, case_id, customer references, etc.) plus contextual notes.
- **Answer template** (`answer_template.json`) — the exact output schema: field names, enum values for each field, and the summary structure. Every enum value listed in the template is a valid decision; choose among them based solely on API evidence.
- **Requirements files** — if the prompt references additional requirements files (naming conventions, permission lists, required fields), read those too.
Back to top