Menu

Individual skill

medbridge-sales-ops

Prepare MedBridge Sales Ops quote, freight, RFQ module, and account reconciliation JSON using the task environment API. Use when the prompt mentions the MedBridge Sales Ops API, quote or RFQ decision packages, EXW pricing, freight comparison, catalog tiers, policies, opportunity milestones, invoices, payments, revenue journals, events, vouchers, or an answer_template JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/codex/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
Network or broad shell
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.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

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.

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

## Workflow

1. Read the user prompt and `input/payloads/answer_template.json` first. The final response must be valid JSON only and must match the template's keys, nesting, array expansion pattern, enum values, date format, and number style.
2. Get the task API base URL from the runner or from `environment_access.md` in the task workspace. Do not hardcode a training URL into the answer.
3. Query the API before calculating. Use exact IDs from the prompt when present; otherwise use `/api/search?q=<text>` and then verify by customer, product, opportunity, quote/RFQ date, status, and linked record IDs.
4. Use the API records as the source of truth over prompt prose when names or old quantities conflict. Treat prompt quantities, dates, event IDs, voucher codes, and contact names as constraints to verify against API records.
5. For quote, RFQ, freight, policy, invoice, payment, revenue, event, and voucher calculations, follow [decision_rules.md](references/decision_rules.md).
6. Return only the completed JSON object. Do not include markdown, citations, comments, or explanation outside the JSON.

## API Collection Helper

Use the helper when it is faster than manual `curl` calls: