Individual skill
medbridge-sales-ops-solver
Solve MedBridge Sales Ops API tasks that require quote/freight decisions or account, invoice, revenue, event, and voucher reconciliations.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/naive/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
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,379 bytesSKILL.mdcore · 10,379 bytesSKILL.mdcore · 10,379 bytesSKILL.mdcore · 10,379 bytestools/fetch_medbridge.pyruns · 3,188 bytes
Read excerpt
# MedBridge Sales Ops Solver
Use this skill when a task references the MedBridge Sales Ops API and asks for an account-ready JSON package for quotes, RFQs, freight options, opportunity milestones, invoices, payments, revenue recognition, events, or vouchers.
## Operating Rules
- Return only valid JSON matching the supplied `input/payloads/answer_template.json`; do not add markdown, comments, or explanatory text.
- Treat the answer template as the output contract. Preserve its object shape, field names, controlled enum values, array intent, date format, and nullability.
- Use the task runner's API base URL as the business source of truth. Do not infer customer, catalog, quote, freight, policy, invoice, payment, revenue, event, or voucher values from memory.
- Extract identifiers, names, quantities, quote dates, current business dates, contacts, event IDs, and voucher codes from the prompt, then verify them through the API.
- Keep product/RFQ outputs at the requested item level. If the API exposes component composition for a module but the prompt asks for module-level quoting, do not expand components unless the template explicitly requires them.
- Use cent-level arithmetic for money. JSON numbers may omit trailing zeroes, but calculations should be exact to cents.
- Prefer stable record IDs from the API. Do not invent IDs, customer names, status values, payment terms, policy codes, or warning text facts.
