Individual skill
reflect-3-crm-support-console
Resolve CRM support-console tasks (SCN_003) — ticket-batch classification, mobile-data triage, and enterprise export-complaint response packages — against a remote support-console API. Use when a task asks to classify service tickets / queue snapshots, triage mobile data cases, or build an enterprise export-failure response package and references a support console API.
experiments/claude_code_glm_5_2_max/reports/skills/task_group_003/reflect-3/reflect-3_attempt_03/SKILL.md
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.
Read excerpt
# SCN_003 CRM Support Console — Resolution Skill
Reusable rules for three task families driven by a shared support-console API.
**Base URL**: use the base URL supplied by the harness/environment (the prompts mention a 127.0.0.1 address — ALWAYS substitute the provided base URL). Records are the source of truth; never assume field values — fetch them.
## API MAP (substitute real ids)
| Endpoint | Use |
|---|---|
| `GET /health` | liveness |
| `GET /api/catalog` | endpoint + record-count catalog (public) |
| `GET /api/accounts`, `GET /api/accounts/<account_id>` | account status, authentication, service_area, tier |
| `GET /api/tickets`, `GET /api/tickets/<ticket_id>` | ticket: account_id, service_area, service_type, subscribed_mbps |
| `GET /api/outages?service_area=<area>` | outages: active, service_area, service_types[], outage_id |