Individual skill
reflect-3_attempt_02
Not available
experiments/claude_code_opus_4_8_xhigh/reports/skills/task_group_003/reflect-3/reflect-3_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 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
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
SKILL.mdcore · 16,392 bytes
Read excerpt
# Support-Console Resolution Skill
## When to use
Use this skill for any task that hands you a small batch/queue of support records
(tickets, mobile cases, or an enterprise complaint) and asks you to classify or
resolve each item and emit a strict JSON answer. The work is always: (1) read the
payload list, (2) look up authoritative records from the shared support-console REST
API, (3) apply deterministic business rules, (4) emit ONLY JSON matching the task's
`answer_template.json`.
Never guess record contents from the customer's prose — the prose only hints at the
issue *type*. The decision is driven by the actual API record fields.
## API base URL and lookup habits
Base URL: `<remote-env-url>` (this overrides any `127.0.0.1:8057`