Support Console JSON Resolver
Use this skill to turn local support-operation payloads plus support-console API evidence into the exact JSON requested by an answer_template.json.
Workflow
Read the user prompt and every file under the task's
payloads/directory, especiallyanswer_template.json.Determine the support-console base URL from the prompt, environment, or task access note. Do not invent records from payload text.
Collect linked API evidence with the bundled helper:
python scripts/collect_support_console.py payloads --base-url "$TASK_ENV_BASE_URL" --output /tmp/support_console_evidence.jsonRun that from the skill root, or substitute the installed skill path if the files live elsewhere. Adjust
payloadsand the base URL path to the actual locations in the current workspace. IfTASK_ENV_BASE_URLis not set, pass the literal base URL from the task.Read
/tmp/support_console_evidence.json, then read decision-rules.md for the relevant task family.Fill the template exactly. Preserve required item ordering, enum spelling, empty-string conventions, and numeric/boolean types.
Recompute summary counts from the completed decisions.
Validate that the final response parses as JSON and has no extra prose. Return only the JSON object.
Task Family Detection
ticket_batch.csvorqueue_snapshot.csv: fixed-service ticket routing. Use ticket, account, outage, diagnostic, and troubleshooting evidence.case_queue.jsonormobile_data_worklist.json: contact-center or mobile-data case routing. Use case, customer, line, bill, plan, and device evidence.client_complaint_email.txtwithresponse_requirements.json: enterprise export response package. Use incident, enterprise account, export-run, SLA, and message evidence.
API Notes
- Start with
/api/catalogif endpoint names are unclear. - Ticket tasks commonly use
/api/tickets/{ticket_id},/api/accounts/{account_id},/api/outages,/api/diagnostics/{ticket_id}, and/api/troubleshooting/{ticket_id}. - Mobile/contact-center tasks commonly use
/api/cases/{case_id}or/api/contact-center/cases/{case_id}, then/api/customers/{customer_id},/api/lines/{line_id},/api/devices/{device_id},/api/plans/{plan_id}, and/api/bills. - Enterprise tasks commonly use
/api/search,/api/enterprise/incidents/{incident_id},/api/enterprise/accounts/{account_id},/api/enterprise/export-runs,/api/enterprise/messages, and/api/enterprise/sla/{account_id}.
When API evidence and payload wording conflict, trust the API unless the prompt explicitly says the payload overrides it.