Menu

Individual skill

self_attempt_03

0upvotes

Not available

experiments/claude_code_kimi2_6_enabled/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
# CRM Support Console Task Group Skill

## Environment
- **Base URL**: `GDPEVO_ENV_BASE_URL=http://34.46.77.124:8003` (overrides any local references in prompts).
- **Server**: SupportConsole/1.0 (Python/3.11.2).
- **Caution**: Standard REST paths (`/tickets`, `/cases`, `/agents`, `/customers`, `/sla`, `/refund`, etc.) consistently return `{"error": "not_found"}`. Endpoint discovery via common naming conventions is unreliable for this console. If an endpoint is not stated explicitly in the prompt or `environment_access.md`, treat it as unknown and follow payload-driven reasoning rather than guessing.

## General Workflow
1. Read `prompt.txt` in the task directory to identify the analyst persona and objective.
2. Read all files under `input/payloads/`. There may be multiple payloads (e.g., a data file plus `response_requirements.json`).
3. Read `input/payloads/answer_template.json` before reasoning. The template defines the exact output schema, field names, types, and ordering rules.
4. Resolve each item using **support-console records** referenced in the prompt, not assumptions. If the remote API does not expose the expected resource, rely on the local payload data and any explicit rules or enums in the template.
5. Return **only** JSON that conforms to the answer template. No markdown fences, no extra commentary.

## Task Type Guidance
Back to top