Menu

Individual skill

reflect-3

0upvotes

Use this skill for CRM/support-console service-ticket tasks that require reading staged payloads, querying support records, choosing operational actions/statuses, and returning strict JSON. Trigger for offline service-ticket batches, mobile support queues, enterprise export complaints, queue-quality or SLA handoff reviews, mobile-data recovery worklists, and any task asking for routing/status/action decisions from customer, line, bill, plan, device, outage, diagnostic, troubleshooting, export-run, incident, SLA, or owner records.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_003/reflect-3/reflect-3_attempt_03/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
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.

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 Service-Ticket SOP

## Core Workflow

1. Read the task prompt, every staged payload named by the prompt, and the answer template before querying records. Treat the payload as the source of item IDs, order, and required output fields.
2. Use the support-console base URL provided by the harness or access note when it differs from a default localhost URL in the prompt. Do not inspect environment source code.
3. Build a private evidence matrix for each payload item:
   - item ID and payload facts
   - console records consulted
   - blocker checks
   - selected operation/status
   - follow-up operation
   - summary bucket/count impact
4. Query by exact IDs first. When a list endpoint omits related collections, use the console search endpoint with the exact ticket, case, incident, or account ID to reveal diagnostics, troubleshooting, messages, export runs, contracts, or other linked evidence.
Back to top