Menu

Individual skill

reflect-3_attempt_03

0upvotes

Not available

experiments/claude_code_opus_4_8_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
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.

Declared tags are partial or unavailable.

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
# SKILL: Support-Console Case & Ticket Resolution Packages

## When to use
Use this skill whenever a task asks you to act as a support/operations analyst and
produce a **structured JSON decision** for a batch of records pulled from the shared
CRM support-console REST API. It covers four recurring task families:

1. **Offline ticket batch resolution** (internet/voice/video service tickets).
2. **Queue-quality ticket triage** (classify + route tickets, key blocker per ticket).
3. **Contact-center / mobile case triage** (pick device/billing/carrier action per case).
4. **Enterprise export-complaint response packages** (incident write-up + ownership +
   SLA credit + sharing artifacts).

The golden rule across all of them: **derive every field from the live API records, never
from the customer's prose or your assumptions.** The free-text "reported issue" is only a