Menu

Individual skill

medbridge-sales-ops-json

0upvotes

Use this skill for MedBridge Sales Ops API tasks that require strict account-ready JSON for quotes, RFQs, EXW catalog pricing, freight comparisons, customer payment terms, milestone invoice/payment/revenue recognition reconciliation, or event and voucher follow-up. Trigger whenever the prompt mentions the MedBridge Sales Ops API, an answer_template.json file, quote/RFQ IDs, opportunities, invoices, payments, revenue journals, freight quotes, policies, events, vouchers, or asks for JSON-only business reconciliation.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_002/fewshot/cc/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 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 solve MedBridge Sales Ops tasks by collecting API evidence, applying the business rules, and returning only JSON that matches the provided template.

## Required Workflow

1. Read the user prompt and `input/payloads/answer_template.json` first. Treat the template as the output contract: same top-level keys, nested keys, array shapes, enum spelling, dates, nulls, and number types.
2. Use the task's supplied API base URL. Do not hardcode a host. Confirm the service with `GET /api`, then fetch only records needed for identifiers in the prompt and their direct links.
3. Collect source records from these endpoints as needed: `customers`, `products`, `rfqs`, `quotes`, `freight-quotes`, `policies`, `opportunities`, `invoices`, `payments`, `revenue-journals`, `events`, and `vouchers`.
4. Prefer direct endpoint fetches for exact IDs. Use `GET /api/search?q=<exact id or exact account text>` to find linked records such as freight for a quote, invoices/payments/journals for an opportunity, or event/voucher records. Keep searches narrow to identifiers or names in the task.
5. Compute values from API records and policy records. Do not paste raw source records or explain the result. Final output must be valid JSON only.

Optional helper:
Back to top