Individual skill
support-console-analyst
Resolve offline support tickets, contact-center cases, enterprise incidents, queue-quality reviews, and mobile-data recovery from a telecom support console API. Covers ticket triage, mobile-device troubleshooting, billing recovery, enterprise export incident response, and queue classification.
experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_003/fewshot/naive/fewshot_attempt_02/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.
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
- 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 · 19,172 bytesapi_schemas.mddoc · 5,444 bytes
Read excerpt
# Support Console Analyst
Resolve support operations tasks using a shared telecom support-console REST API at
the base URL provided in `<TASK_ENV_BASE_URL>`. Every task follows the same
pattern: read the payload files, fetch live evidence from the API, apply the
decision rules below, and return JSON conforming to the answer template.
**Core rule**: decisions must be grounded in API evidence, never in assumption.
When an API result provides a value, prefer it over payload hints.
## API Quick Reference
All endpoints are GET and return JSON arrays or single objects. Key endpoints by
task family: