Individual skill
crm-service-ticket-sop
Resolve CRM support-console service tickets, mobile cases, fixed-service queue quality reviews, and enterprise export complaints into strict JSON answer templates using staged payloads plus support-console evidence.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_003/self/self_attempt_02/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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
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 · 9,453 bytes
Read excerpt
# CRM Service-Ticket SOP
Use this skill for tasks that provide a support-console base URL, payload files, and an `answer_template.json` requiring ticket/case decisions, queue summaries, or enterprise response fields.
## Source Discipline
- Use only the prompt payloads, the answer template, `environment_access.md` when present, and the remote support-console records. Do not inspect answer files, judge endpoints, evaluator notes, local environment source, or other attempt folders.
- Prefer the harness/prompt base URL. If it gives a localhost default but `environment_access.md` gives a remote URL, use the remote URL.
- Return only JSON conforming to the template. No Markdown, comments, extra fields, or omitted required fields.
## Console Lookup Pattern
Start with `GET /health`. Useful console routes: