Individual skill
medbridge-sales-ops
Prepare JSON-only MedBridge Sales Ops API decision packages. Use for tasks that ask Codex to verify customers, RFQs, quotes, product catalog tiers, freight quotes, policies, opportunities, invoices, payments, revenue journals, events, or vouchers from a provided task environment base URL and return an account-ready quote, transport, finance, reconciliation, or follow-up JSON matching a supplied answer template.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/deepagents/fewshot_attempt_03/SKILL.md
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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- finance Derived category
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# MedBridge Sales Ops
## Core Workflow
1. Read the prompt and `input/payloads/answer_template.json` before calling the API.
2. Extract all explicit identifiers, dates, customer names, product codes, quantities, contacts, event IDs, voucher codes, and quote basis instructions from the prompt.
3. Use the base URL supplied by the runner or prompt. Fetch `/api` first when route shapes or field names are unclear.
4. Retrieve records from the relevant endpoint families: customers, products, RFQs, quotes, freight quotes, policies, opportunities, invoices, payments, revenue journals, events, and vouchers.
5. Cross-check linked IDs rather than trusting a single record. Match customers to quotes/RFQs/opportunities, products to requested lines, freight to quote or destination context, invoices/payments/revenue journals to milestone or opportunity IDs, and events to vouchers.
6. Fill the exact template shape. Preserve key names, controlled enum spelling, required ordering hints, nullability, and JSON-only output.
Do not use memorized example values. Derive every final value from the current prompt, current template, and current API records.
## API Retrieval