Menu

Individual skill

self_attempt_01

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_006/self/self_attempt_01/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
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.

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 Solver — SOP

## Environment
- **API base URL**: `http://34.46.77.124:8006` (from environment_access.md; overrides any localhost references 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`.
- Never start a local env or run setup scripts. Use the remote API directly.

## Source Precedence (critical)
1. **ProcureOps API is always the system of record.** Local memos name targets and give business rules but never override live API data.
2. **Local payloads** (memos, JSON packets) provide: target IDs, business rules, date parameters, chargeback registers, release notes.
3. **answer_template.json** in each task's `input/payloads/` defines the exact output schema. Match it precisely — every key, every type, every allowed value.

## Workflow for Any Task
1. Read `input/payloads/answer_template.json` first — know the output shape before querying.
2. Read the memo/packet payload to extract: target IDs, as-of date, business rules, control parameters.
Back to top