Menu

Individual skill

medbridge-sales-ops

0upvotes

Solve MedBridge Sales Ops API tasks that require account-ready JSON for quotes, RFQs, freight decisions, opportunities, invoices, payments, revenue journals, events, and vouchers. Use when the prompt asks Codex to query a shared MedBridge Sales Ops task API and return JSON matching an answer_template.json.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/codex/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

## Core Workflow

1. Read the user prompt and the local `input/payloads/answer_template.json` before querying records. Treat the template as the required output contract, including field names, array shapes, enum strings, number/date formats, and nullable fields.
2. Resolve the API base URL from the prompt, runner instructions, or environment access file. Use only the provided MedBridge Sales Ops API and its documented GET endpoints.
3. Extract every stable identifier and exact business name from the prompt: customer IDs, quote IDs, RFQ IDs, opportunity IDs, product codes, event IDs, voucher codes, contacts, dates, and quantities.
4. Query the API with those identifiers. Prefer direct endpoints for known IDs, use `/api/search?q=...` for names and relationship discovery, and fetch full records before deriving final values.
5. Cross-check relationships across records. Do not trust a matching name or search hit unless the customer, opportunity, quote/RFQ, product, milestone, event, or voucher linkage agrees with the prompt and related records.
6. Load [references/answering-rules.md](references/answering-rules.md) for pricing, freight, milestone, revenue-recognition, event, voucher, and action-routing rules.
7. Produce only valid JSON matching the template. Do not include markdown, commentary, extra keys, or omitted required keys.

## API Helper
Back to top