Menu

Individual skill

medbridge-sales-ops-json

0upvotes

Prepare JSON-only MedBridge Sales Ops quote and engagement reconciliation packages from the task API.

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

Use this skill when a task asks for an account-ready MedBridge Sales Ops response involving quotes, RFQs, freight options, product catalog tiers, policies, opportunities, milestone invoices, payments, revenue journals, events, or vouchers.

## First Steps

1. Read the user prompt and every file under `input/payloads/`. If an `answer_template.json` or schema file is present, treat it as authoritative for top-level keys, nested field names, field order, null handling, and controlled values.
2. Resolve the API base URL from the runner placeholder, environment variable, or prompt wording. Use only the MedBridge business API endpoints exposed by the task environment.
3. Extract stable identifiers and constraints from the prompt: quote/RFQ/opportunity/customer/event/voucher IDs, product codes, quantities, business date, destination/freight requirements, named contact, and any instruction to exclude freight or avoid component expansion.
4. Query exact record endpoints first. If a record is not directly named, use `/api/search?q=<text>` and relevant collection lists. Collection responses are wrapped as `{"collection": ..., "count": ..., "records": [...]}`.
5. Return only valid JSON. Do not include markdown, prose, citations, or calculation notes outside the JSON object.

## API Records To Join
Back to top