Menu

Individual skill

medbridge-sales-ops-json

0upvotes

Solve MedBridge Sales Ops API tasks that require account-ready JSON for quote/RFQ pricing, freight decisions, opportunity reconciliation, invoice/payment/revenue-recognition status, and event or voucher follow-up actions using a provided answer template.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/naive/fewshot_attempt_02/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.

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 JSON

Use this skill when a task asks for a MedBridge Sales Ops API response and a final JSON object matching `input/payloads/answer_template.json`.

## Workflow

1. Read the user prompt and the local `input/payloads/answer_template.json`.
2. Extract requested record identifiers, named customer/contact, quote or as-of date, product codes, quantities, event IDs, voucher codes, and any explicit output constraints.
3. Query the runner-provided API base URL. If useful, use `scripts/medbridge_fetch.py` to fetch records by ID, product code, voucher code, collection, or search term.
4. Read `references/medbridge_rules.md` before deriving totals, status flags, recommended transport modes, reconciliation state, or action values.
5. Produce only valid JSON matching the template. Preserve the template's object shape and controlled enum values; expand placeholder arrays when the API shows multiple applicable records.

## API Use
Back to top