Menu

Individual skill

medbridge-sales-ops

0upvotes

Use this skill for MedBridge Sales Ops API tasks that ask for account-ready JSON quote packages, RFQ pricing, freight comparisons, CRM opportunity reconciliation, milestone invoices, revenue recognition, event/voucher follow-up, or strict answer_template.json output. Use it whenever the prompt mentions the MedBridge Sales Ops API, Sales Ops records, catalog tiers, EXW/freight quote decisions, customer payment policies, invoices, payments, revenue journals, opportunities, events, vouchers, or a request to return only JSON matching an input payload template.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/opencode/fewshot_attempt_01/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
Yes
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 Reconciler

Use this skill to solve MedBridge Sales Ops tasks by fetching the business records from the task-provided API, reconciling them, and returning only JSON that conforms to the provided template. The evaluator cares about exact values, exact schema shape, and whether the answer is derived from the current API records rather than from assumptions.

## First Pass

1. Read the user prompt and `input/payloads/answer_template.json`.
2. Identify the task-provided API base URL. Prompts may name it as `<TASK_ENV_BASE_URL>`, `BASE_URL`, or similar. Use the actual URL available in the runner/session, not the literal placeholder text.
3. Query `GET /api` to confirm available collections, then fetch records with detail endpoints and `GET /api/search?q=<id-or-name>` as needed.
4. Build the answer from API records and policy records. Do not rely on IDs, amounts, names, dates, or statuses from prior examples.
5. Return only valid JSON. Do not include markdown, comments, explanations, trailing commas, or extra keys.

Useful collections are usually:
Back to top