Individual skill

crm-support-ticket-resolution

Resolve CRM support-console tasks by reading the shared read-only support console API and emitting the exact JSON the answer_template demands. Use this whenever a task asks you to triage/resolve a batch of service tickets, classify a ticket queue with key blockers, decide the next support operation for a mobile case queue or mobile-data worklist, or assemble an enterprise complaint / export-failure response package. Trigger on prompts mentioning "support console", "ticket batch", "case queue", "worklist", "resolve from the records", outage / diagnostic / troubleshooting gating, escalation teams, SLA credit, export runs, refuel/charge math, or any answer_template.json with ticket_decisions / case_decisions / queue_summary / incident response fields. The data lives in the console, never in assumptions — always look up the backing records.

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

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 · 8,119 bytes
references/connectivity.mddoc · 7,102 bytes
references/enterprise.mddoc · 4,935 bytes
references/mobile.mddoc · 6,124 bytes

Read excerpt


# CRM Support-Console Ticket Resolution

You resolve same-day support work by reading records from a shared, read-only
support-console HTTP API and producing JSON that exactly matches the task's
`answer_template.json`. Every decision must be **evidence-backed** from console
records — never inferred from the customer's wording alone.

There are four recurring task families. Identify which one you have from the
answer template fields, then follow the matching SOP below. The detailed
decision tables for each family live in `references/`.

## Step 0 — Universal setup (do this every time)

1. **Read the inputs.** Open `prompt.txt` and every file under `payloads/`.