Menu

Individual skill

reflect-3_attempt_02

0upvotes

Not available

experiments/claude_code_glm_5_2_max/reports/skills/task_group_005/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
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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
# ERP Finance Expense-Control Skill (task_group_005)

Reusable workflow rules for solving ERP finance expense-control tasks against the shared remote ERP API. Distilled from reflect-loop practice on train tasks. These are workflow rules, not per-task answers.

## 0. Ground rules
- Use ONLY the remote ERP Web API (system of record). Do NOT read local `env/` source files or test fixtures.
- Report all currency in USD to 2 decimals unless a task explicitly says otherwise. Follow the `answer_template.json` `unit`/`precision` fields (they override ambiguous prose). Example: a template that says `unit: USD, precision: 2` means dollars with 2 decimals — do NOT convert to cents even if prose says "cents".
- Sort every ID list exactly as the template specifies (usually ascending by ID; digits sort before uppercase letters, so `CLM-2025-00xx` < `CLM-2025-FIN-xx` < `CLM-2025-OPS-xx`; `PPD-2025-*` < `PPD-AUR-*`).
- Preserve list orders that the template says must match an input payload order (e.g. `selected_invoice_ids` "same order as scope file").
- Query specific records by exact-match params (claim_id, bill_id, business_id, account, period, prepaid_invoice_id, vendor_id). Do not pull whole collections.

## 1. API contract
- Base URL + `GET /endpoints` lists all paths and the filtering contract.
- Health: `GET /health`, `GET /api/health`.
- Resources (namespaced `/api/...` preferred; bare aliases also exist): `/api/claims`, `/api/ap/bills`, `/api/ap/payments`, `/api/vendors`, `/api/close/logs`, `/api/prepaids/invoices`, `/api/prepaids/gl-balances`, `/api/compliance/objects`.
Back to top