Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_003/reflect-3/reflect-3_attempt_02/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
# Support Console Solver — SKILL.md

## Overview

This skill covers the task_group_003 support-console API used to resolve service tickets, mobile cases, enterprise incidents, and queue-quality reviews. The API is read-only and returns all evidence needed to construct structured JSON answer payloads.

## API Usage Habits

### Base URL & Discovery
- Use the remote URL provided by the harness (override any localhost references in task prompts).
- Start with `/health` to confirm connectivity, then `/api/catalog` for the full endpoint list and record counts.
- Endpoint list: `/api/accounts[/<id>]`, `/api/tickets[/<id>]`, `/api/outages?service_area=<area>`, `/api/diagnostics/<ticket_id>`, `/api/troubleshooting/<ticket_id>`, `/api/cases[/<id>]`, `/api/customers`, `/api/lines[/<id>]`, `/api/devices[/<id>]`, `/api/plans[/<id>]`, `/api/bills`, `/api/enterprise/incidents[/<id>]`, `/api/enterprise/export-runs?incident_id=<id>`, `/api/enterprise/messages?query=<text>`, `/api/enterprise/sla/<enterprise_account_id>`.

### Data Fetching Pattern
- For batch tasks, fetch tickets/cases first to get IDs (account_id, line_id, device_id, service_area), then fan out to accounts, diagnostics, outages, lines, devices in parallel.