Individual skill
self_attempt_03
Not available
experiments/claude_code_glm_5_2_max/reports/skills/task_group_022/self/self_attempt_03/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- 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.
- 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 · 11,269 bytesSKILL.mdcore · 11,269 bytesSKILL.mdcore · 11,269 bytesSKILL.mdcore · 11,269 bytesSKILL.mdcore · 11,269 bytesreferences/output_contract.mddoc · 3,879 bytesreferences/pipeline.mddoc · 6,675 bytes
Read excerpt
# Atlas Commerce Operations: Reusable Operating Rules
This is a self-contained operating skill for solving Atlas Commerce Operations
analytics tasks served from the `environment_access.md` workplace API. Each task
gives you a business request JSON, an output template JSON, and a free-text prompt;
the API exposes a relational database, a data dictionary, and (sometimes) a
controlled correction transaction. The five train tasks all share one shape, so
these rules are written once and reused per task.
This file is the entry point. It contains no task-specific final values, table names
beyond the documented schema, query results, or answers from any individual task.
Two supporting files live alongside it:
- `references/pipeline.md` — the end-to-end execution pipeline, step by step.
- `references/output_contract.md` — how to read a template and emit a conformant JSON.