Menu

Individual skill

reflect-3_attempt_01

0upvotes

Not available

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_002/reflect-3/reflect-3_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
# MedBridge Sales Ops Task Skill

Use the task-provided API base URL as the source of truth. Start with `GET /api` when unsure, then query only the records needed: `/api/search?q=...`, `/api/customers/<id>`, `/api/products/<code>`, `/api/rfqs/<id>`, `/api/quotes/<id>`, `/api/freight-quotes`, `/api/policies`, `/api/opportunities/<id>`, `/api/invoices`, `/api/payments`, `/api/revenue-journals`, `/api/events`, and `/api/vouchers`.

## Source Precedence

- Obey the staged prompt for confirmed IDs, quantities, dates, as-of dates, and requested output shape.
- Use API records for customer names, product tiers, freight status, invoice/payment/journal state, events, and vouchers.
- Use policy records for payment, EXW scope, quote validity, freight reconfirmation, module granularity, and revenue-recognition rules.
- Treat older RFQs, prior quote quantities/prices, component tables, wrong shipment-size freight, stale benchmarks, and distractor routes as distractors unless the prompt explicitly asks to report source-validity concerns.
- Preserve the answer template's field names, enum casing, and literal conventions; do not expand a template literal into a policy terms code unless the template asks for that code.

## Quote And RFQ Rules

- For quote revisions, use the quote's confirmed quantity and product code. Ignore prior line-item quantity and prior unit price when the catalog tier now differs.
Back to top