Menu

Individual skill

medbridge-sales-ops-json

0upvotes

Use this skill for MedBridge Sales Ops API tasks that require account-ready JSON for quotes, RFQs, catalog pricing, freight comparisons, opportunity milestone reconciliation, invoices, payments, revenue journals, events, or vouchers. Use it whenever the prompt mentions the MedBridge Sales Ops API, `<TASK_ENV_BASE_URL>`, BASE_URL, quote decision packages, EXW pricing, freight validity, revenue recognition, or CRM/accounting follow-up JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/opencode/fewshot_attempt_03/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 to answer MedBridge Sales Ops tasks that require a final JSON object matching an `input/payloads/answer_template.json` file.

The target task is data reconciliation, not prose generation. Read the prompt and template first, gather the source records from the API, derive only the fields the template asks for, validate the JSON shape, and return JSON only.

## Core Workflow

1. Read the user prompt and the local `input/payloads/answer_template.json`.
2. Resolve the API base URL from the prompt, environment, or an environment access note if one is staged with the task. Treat placeholders such as `<TASK_ENV_BASE_URL>` and `BASE_URL` as the runner-provided base URL.
3. Query the API for the exact business identifiers named in the prompt, such as customer IDs, RFQ IDs, quote IDs, product codes, opportunity IDs, event IDs, and voucher codes.
4. Use `/api/search?q=<identifier>` as the main discovery tool. It returns linked records across collections. Then fetch direct product, customer, quote, RFQ, opportunity, event, or voucher records when needed.
5. Build the answer from the template outward. Preserve key names, nesting, arrays, booleans, nulls, controlled enum strings, ISO dates, and numeric types required by the template.
6. Return only valid JSON. Do not include markdown, comments, code fences, or explanatory text.
Back to top