Menu

Individual skill

medbridge-sales-ops-json

0upvotes

Use this skill whenever a task asks for MedBridge Sales Ops API work, account-ready quote packages, RFQ pricing, freight comparisons, invoice/payment/revenue reconciliation, event or voucher follow-up routing, or any response that must match an answer_template.json from the task payload. It is especially relevant when the prompt mentions a shared task environment base URL, Sales Ops API records, JSON-only output, quote/RFQ IDs, opportunity IDs, milestone invoices, freight quotes, policies, or CRM/accounting follow-ups.

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

Use this skill to turn MedBridge Sales Ops API records into the exact JSON object requested by the current task template. The API data, prompt, and `input/payloads/answer_template.json` are the sources of truth. Do not reuse values from prior examples; derive every customer, amount, date, ID, status, and action from the current prompt and API records.

## Required Workflow

1. Read the user prompt and `input/payloads/answer_template.json`.
2. Resolve the API base URL from the prompt, runner context, or environment variable. Normalize it by removing a trailing slash before appending paths.
3. Fetch `GET /api` to confirm the service is reachable.
4. Retrieve records by explicit IDs from the prompt, then use `GET /api/search?q=<id-or-name>` to find linked records.
5. Read [references/medbridge-workflows.md](references/medbridge-workflows.md) before deriving values. It contains the quote, RFQ, freight, policy, and reconciliation rules.
6. Populate only the keys present in the current answer template. Preserve the template's nesting, array names, controlled enum labels, and date/number formatting expectations.
7. Validate the output as JSON and compare its shape to the template. You may run:
Back to top