Individual skill
fewshot_attempt_02
Not available
experiments/claude_code_glm_5_2_max/reports/skills/task_group_022/fewshot/fewshot_attempt_02/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 · 12,951 bytesSKILL.mdcore · 12,951 bytesSKILL.mdcore · 12,951 bytesSKILL.mdcore · 12,951 bytesSKILL.mdcore · 12,951 bytesSKILL.mdcore · 12,951 bytesSKILL.mdcore · 12,951 bytesenvironment_api.mddoc · 4,328 bytesoutput_contract_checklist.mddoc · 3,413 bytes
Read excerpt
# Atlas Commerce Operations Reconciliation
Reuse this skill for any task that asks you to compute a business scorecard, reconciliation, quality review, productivity summary, or support-health review from the **Atlas Commerce Operations** workplace service and write a single JSON object to `answer.json`.
Every task in this family has the same anatomy:
1. **A business request** at `input/payloads/*_request.json` — defines scope, time windows, business definitions, classification/risk rules, rounding, and tie-breaks.
2. **An answer template** at `input/payloads/answer_template.json` — a JSON Schema that is the exact output contract (required fields, types, enums, min/max array lengths, ordering, precision).
3. **A prompt** at `input/prompt.txt` — names the stakeholder, the scenario, and the output file.
4. **A live workplace service** described in `environment_access.md` — reach it over the network with the documented endpoints and bearer token.
The work is the same every time: read the contract, map the business definitions onto real schema columns, run precise read-only SQL (and, only for correction tasks, one minimal guarded transaction), compute the metrics exactly as defined, and emit one JSON object that conforms to the template to the letter.
## When to use this skill