Menu

Individual skill

crm-support-ticket-resolution

0upvotes

Resolve CRM service-ticket / support-queue tasks against the shared read-only support-console API. Use this whenever a task asks you to act as a support operations analyst, contact-center lead, queue-quality analyst, mobile-data recovery analyst, or enterprise support lead and to "resolve", "classify", "route", "triage", or "produce a structured response/summary" for tickets, cases, mobile lines, or enterprise export incidents, returning JSON that conforms to a provided answer_template.json. Trigger it for any payload of service tickets, a case/queue snapshot (CSV or JSON), a mobile worklist, or an enterprise complaint email, even if the prompt does not name this skill — the decisions must come from support-console records, never from assumptions.

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

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

# CRM Support-Ticket Resolution

You are resolving a batch of CRM support work by looking up authoritative
records in a shared, read-only support console and applying fixed business
conventions. The prompt gives you a payload (tickets, cases, a queue snapshot, a
mobile worklist, or an enterprise complaint) plus an `answer_template.json`.
Your job is to produce JSON that conforms exactly to that template, where every
field is justified by console records — not by the free-text customer report.

## Golden rules (apply to every task family)

1. **Records over reports.** The customer's words (CSV `customer_report`/
   `queue_note`, case `summary`, complaint email) only tell you where to look.
   The decision is driven by the structured record (account status, line/device
Back to top