Individual skill

fewshot_attempt_03

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_006/fewshot/fewshot_attempt_03/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 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
# ProcureOps Task Group Skill — Sourcing, Receiving, AP, and Change Control

## 1. Environment

- **API base URL**: Use the URL from `environment_access.md` (overrides any `localhost`/`127.0.0.1` in task text).
- **Public endpoints**: `/programs`, `/suppliers`, `/items`, `/contracts`, `/purchase_requisitions`, `/purchase_orders`, `/receipts`, `/ap/invoices`, `/ap/payments`, `/approval_events`, `/budget_snapshots`, `/vendor_risk_events`.
- Query with query parameters for filtering (e.g., `?program_id=PRG-AX17`, `?supplier_id=SUP-LUMA`).

## 2. Source Precedence

1. **ProcureOps API** — system of record for all operational data (POs, receipts, invoices, contracts, suppliers, approvals, budgets, risk events).
2. **Local chargeback register** — authoritative for chargeback statuses and amounts (train_005 pattern). When it exists, use its `status`, `reason_code`, `basis_quantity`, and `unit_cost` over API-derived values.
3. **Task payloads** (memos, packets, templates) — provide target IDs, business parameters (tax rates, as-of dates), and context; do NOT use them to override API facts.
4. When the API and a memo disagree, the API wins. When a chargeback register and the API disagree on chargeback details, the register wins.