Individual skill
medbridge-sales-ops
Solve MedBridge Sales Ops API tasks that require account-ready JSON for quote pricing, freight comparisons, RFQs, opportunity milestone reconciliation, revenue recognition, invoice follow-up, events, and vouchers. Use when prompts mention MedBridge Sales Ops, quote/RFQ/opportunity IDs, product catalog tiers, freight quotes, policies, or returning JSON matching an answer_template.json.
experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/deepagents/fewshot_attempt_01/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 · 3,010 bytesSKILL.mdcore · 3,010 bytesSKILL.mdcore · 3,010 bytesSKILL.mdcore · 3,010 bytesreferences/derivation-rules.mddoc · 6,369 bytesscripts/collect_context.pyruns · 3,287 bytes
Read excerpt
# MedBridge Sales Ops
## Core Workflow
1. Read the user prompt and the provided `input/payloads/answer_template.json`. Treat the template as the output contract: preserve keys, arrays, enum spellings, date format, nullability, and numeric precision style.
2. Identify the task family:
- Quote or RFQ pricing: prompt mentions a quote/RFQ, products/modules, EXW pricing, freight, payment terms, or quote policies.
- Engagement reconciliation: prompt mentions an opportunity, milestones/phases, invoices, payments, revenue journals, events, vouchers, or follow-up actions.
3. Resolve the task API base URL from the prompt or runner-provided environment. Use only the MedBridge API records needed for the IDs in the prompt/template.
4. Gather linked records with direct endpoints and ID-specific search. Prefer exact IDs from the prompt. Avoid broad listing unless direct fetch/search cannot identify a required linked record.
5. Apply the derivation rules in [references/derivation-rules.md](references/derivation-rules.md).
6. Return only valid JSON. Do not include markdown, comments, provenance notes, or extra keys.
## API Gathering