Individual skill

crm-support-ticket-resolution

Resolve CRM support-console tasks against the shared read-only support API and emit JSON that conforms to the task's answer_template.json. Use this skill whenever a task asks you to act as a support analyst / contact-center lead / queue-quality analyst / enterprise support lead and to classify, route, or decide outcomes for service tickets, mobile cases, mobile-data worklists, or enterprise export incidents from support-console records. Triggers include: resolving a batch of offline/service tickets, choosing the next support operation for mobile/line cases, classifying a queue before SLA handoff, computing data-refuel charges, or preparing an enterprise export-complaint response package (root cause, failure window, SLA credit, owners, channel, evidence folder, report title, share permissions). Apply it even when the prompt does not name "support console" explicitly but references tickets, accounts, outages, diagnostics, lines, devices, plans, bills, cases, or enterprise incidents/export-runs and wants a structured decision.

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_003/demonstration_skill/demonstration_skill_attempt_01/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: No
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.

agent Repository topic
ai Repository topic
benchmark Repository topic
llm Repository topic
self-evolving Repository topic
self-learning Repository topic
skills Repository topic
sales Derived category
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 6,605 bytes
SKILL.mdcore · 6,605 bytes
references/enterprise_incident.mddoc · 6,645 bytes
references/mobile_cases.mddoc · 7,549 bytes
references/ticket_resolution.mddoc · 9,188 bytes

Read excerpt


# CRM Support-Console Ticket Resolution

You resolve support-console tasks by reading live records from a shared,
read-only HTTP API and producing JSON that exactly matches the task's
`answer_template.json`. Every decision must be backed by a record you actually
fetched — never assume a value, and never carry over an answer from a previous
task. The data changes per task; the **rules** below are what transfer.

## 0. Orient before you act

1. Read `prompt.txt` and every file under `payloads/`. The `answer_template.json`
   is the contract: it tells you the exact output keys, enum values, ordering
   rule, and number formatting. Mirror it precisely.
2. Confirm the API base URL. The harness may override the prompt's URL via an