Individual skill
reflect-3_attempt_01
SCN_003 CRM support-console analyst. Resolve same-day ticket batches, mobile triage queues, mobile-data recovery worklists, and enterprise export-complaint response packages by querying the shared support-console API and applying fixed diagnostic thresholds, gating order, root-cause routing, and per-family decision trees.
experiments/claude_code_glm_5_2_max/reports/skills/task_group_003/reflect-3/reflect-3_attempt_01/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
- 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.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
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 · 18,590 bytes
Read excerpt
# SCN_003 CRM Support Operations Analyst
Reusable rules for working a support-console workload across four task families. All evidence comes from the remote support-console API; never assume field values — fetch the records. Prompts may reference `127.0.0.1:8057`; always substitute the real base URL provided by the harness.
## 1. API Map
Base URL: use the harness-provided base URL (e.g. `<remote-env-url>`). Health: `GET /health`.
Public catalog: `GET /api/catalog` (endpoints + record counts only).
- `GET /api/accounts` and `/api/accounts/<account_id>` — broadband/enterprise accounts. Fields: `account_id`, `name`, `service_area`, `status` (`Active`/`Suspended`), `tier`, `authentication{last_login_status, account_recovery_status, last_login_at}`. A missing account returns `{"error":"not_found"}`.
- `GET /api/tickets` and `/api/tickets/<ticket_id>` — tickets. Fields: `ticket_id`, `account_id`, `service_type` (`internet`/`video`/`voice`), `service_area`, `subscribed_mbps`, `status`, `issue_summary`.
- `GET /api/outages?service_area=<area>` — outages for an area. Each: `outage_id`, `service_area`, `active` (bool), `service_types` (array), `eta_hours`, `impact_score`, `started_at`.
- `GET /api/diagnostics/<ticket_id>` — pre-troubleshoot snapshot. Fields: `bandwidth_mbps`, `latency_ms`, `jitter_ms`, `root_causes` (array), `started_at`/`completed_at`.