Menu

Individual skill

self_attempt_03

0upvotes

Not available

experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_003/self/self_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: CRM Support-Console Decision Tasks

## When to use
Use this when a task asks you to act as a support analyst/lead over a **CRM support-console REST API** and emit a structured JSON decision package. Symptoms: a `prompt.txt` plus a `payloads/` folder containing an `answer_template.json` and one input file (CSV ticket/queue batch, JSON case/work queue, or a complaint email + requirements). The work is always: read input rows -> look up live records in the API -> apply deterministic business rules -> emit JSON that exactly matches the template.

There are four task families seen so far:
1. **Offline ticket batch resolution** (CSV of tickets -> `ticket_decisions` + `batch_summary`).
2. **Queue-quality classification before SLA handoff** (CSV of tickets -> `ticket_decisions` with `key_blocker` + `queue_summary`).
3. **Contact-center / mobile case triage** (JSON of cases -> `case_decisions` with device/line/bill actions + `queue_summary`).
4. **Mobile-data recovery worklist** (JSON of cases -> `case_decisions` with refuel/charge + `worklist_summary`).
5. **Enterprise export-complaint response package** (email + requirements -> one flat object).

## API usage habits
Base URL is given in `environment_access.md` and **overrides** any `http://127.0.0.1:8057` in the prompt. Call with `curl -s <base>/<endpoint>`. The API is read-only; it never exposes answers. Confirm reachability with `GET /health` and use `GET /api/catalog` for record counts.
Back to top