Individual skill

medbridge-sales-ops

Use for MedBridge Sales Ops API tasks that ask for account-ready JSON quote packages, RFQ/module quotes, freight comparisons, customer policy flags, opportunity milestone reconciliation, invoice/payment/revenue recognition status, or linked event/voucher follow-up actions.

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

Use this skill when a task references the MedBridge Sales Ops API and asks for a JSON-only quote, freight, policy, or opportunity reconciliation answer.

## Required Workflow

1. Read the task prompt and `input/payloads/answer_template.json`.
2. Use the API base URL supplied by the task runner or prompt. Do not reuse any creator-time URL.
3. Extract explicit record IDs, customer names, product codes, dates, quantities, event IDs, and voucher codes from the prompt.
4. Fetch API records before calculating. Start with exact endpoints for explicit IDs, then fetch collection lists when relationships need filtering.
5. Fill the output to match the template exactly: same top-level keys, nested shapes, controlled enum spellings, date format, nulls, arrays, and money precision.
6. Return only valid JSON. Do not include markdown or explanatory text.

For detailed derivation rules, read [references/medbridge-rules.md](references/medbridge-rules.md).
Back to top