Individual skill

medbridge-sales-ops-reconcile

Reconcile MedBridge Sales Ops CRM tasks (B2B medical wholesale + implementation-services) against the remote Sales Ops API and emit the account-ready JSON answer. Covers QUOTE decision packages (EXW pricing, freight options, route risk, recommended mode, payment terms) and milestone RECONCILIATION packages (invoice/payment state, outstanding balance, revenue-recognition coverage, CRM follow-up routing, event/voucher linkage). Use whenever a task references MedBridge, quotes like Q-TR-*, RFQ-TR-*, opportunities like OPP-TR-*, milestones MS1/MS2/MS3, freight-quotes, revenue-journals, or the shared Sales Ops API base URL.

experiments/claude_code_glm_5_2_max/reports/skills/task_group_002/fewshot/fewshot_attempt_03/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 — Reconciliation & Quote Decision Skill

Executable rules for producing the single `answer.json` that matches `input/payloads/answer_template.json` exactly. Source of truth is the **remote Sales Ops HTTP API** (base URL supplied by the runner; treat `http://127.0.0.1:${PORT}` / `API_BASE_URL` placeholders in prompts as that same remote base). Trust API records over narrative wording for IDs and attributes, **except echo the customer name exactly as the task prompt states it** (see §7).

## 1. API access contract

- Base URL: the runner-provided `API_BASE_URL` (a remote host such as `<remote-env-url>`). Never start a local server; never read any `env/` directory.
- `GET /health` — sanity check.
- `GET /api` — lists `collections` and `endpoints`.
- `GET /api/<collection>` — list all records (`{collection, count, records}`).
- `GET /api/<collection>?<key>=<value>` — filter (case-insensitive, matches nested keys, numeric tolerance 2dp; multiple filters AND). Filter invoices/payments/revenue-journals/events/vouchers by `opportunity_id`; freight-quotes by `quote_id`.
- `GET /api/<collection>/<id>` — detail by id. **Detail-by-id works ONLY for:** `customers`, `products`, `rfqs`, `quotes`, `freight-quotes`, `opportunities`. For `invoices`, `payments`, `revenue-journals`, `events`, `vouchers`, `policies` use listing/filter (or `/api/search?q=...` which returns full records tagged with collection+id).
- `GET /api/search?q=<text>` — substring search across ALL collections (up to 100 hits). Use to resolve events/vouchers by code or id.
- Money = USD 2 decimals. Dates = ISO `YYYY-MM-DD`. Use stable record IDs verbatim.