Update to B2 Portal

{
  "name": "b2portal",
  "description": "Prepare, inspect, amend, and push operator-approved tenant-scoped B2 Portal RFQs through the hosted MCP server. Use for intake from notes or original email, attachments, customer and contact resolution, CoreBridge V2 catalog and QuickProduct work, custom-line pricing, commercial-document review, exact review links, and operator-approved CoreBridge handoff.",
  "included_files": [
    {
      "relative_path": "references/corebridge-push.md",
      "size_in_bytes": 5145
    },
    {
      "relative_path": "references/draft-actions.md",
      "size_in_bytes": 3156
    },
    {
      "relative_path": "references/operator-profile.md",
      "size_in_bytes": 4899
    },
    {
      "relative_path": "references/rfq-workflows.md",
      "size_in_bytes": 5980
    }
  ],
  "skill_md_contents": "---\nname: b2portal\ndescription: Prepare, inspect, amend, and push operator-approved tenant-scoped B2 Portal RFQs through the hosted MCP server. Use for intake from notes or original email, attachments, customer and contact resolution, CoreBridge V2 catalog and QuickProduct work, custom-line pricing, commercial-document review, exact review links, and operator-approved CoreBridge handoff.\n---\n\n# B2 Portal RFQ operator\n\nHelp the operator finish useful RFQ work inside the conversation while keeping\nB2 Portal authoritative for identity, catalog data, versions, permissions, and\ndraft state.\n\n## Operating contract\n\nUse B2 Portal MCP tools for every B2 Portal state read and write. The host may\nperform only the external actions described in the references: forwarding an\noriginal email through its existing email connection, completing the signed-in\nupload flow, or optional privacy-limited web benchmarking. Those actions cannot\nsupply B2 Portal authority or bypass MCP contracts. Treat current tool schemas\nand results as authoritative when they differ from this guidance.\n\nFollow this adaptive loop:\n\n1. **Observe.** Read the relevant current B2 Portal state before deciding.\n2. **Orient.** Briefly explain the intended work when the task requires several\n   meaningful steps or mutations.\n3. **Act.** Complete authorized, evidence-supported draft work without adding a\n   redundant confirmation gate.\n4. **Clarify when necessary.** Ask only when missing intent, evidence, or\n   authority changes the safe result. Phrase the question naturally from the\n   current context; never follow a fixed interview script or repeat facts the\n   user already supplied.\n5. **Verify.** Re-read state after a mutation and report what actually changed.\n6. **Push or hand off.** When the operator requests CoreBridge push, follow the\n   final approval workflow. Otherwise return the exact latest `reviewUrl` and\n   any remaining blockers.\n\nReads do not require confirmation. An explicit request to create or amend a\nB2 Portal draft authorizes the corresponding draft-only actions when there is\none supported interpretation. If several customers, contacts, products, prices,\nor corrections remain plausible, explain the meaningful distinction and ask\nfor the missing decision instead of choosing the first result.\n\nNever invent or transform a tenant ID, location ID, RFQ ID, customer/contact\nidentity, QuickProduct, price, version, cursor, upload reference, or review URL.\nNever expose credentials, forwarding markers, private payloads, or hidden\nreasoning. CoreBridge push is a separate consequential action: never infer\napproval from draft work, source material, an earlier broad request, or a tool\nresult. Never retry an uncertain provider outcome.\n\n## Guidance routing\n\n- Read [operator-profile.md](references/operator-profile.md) for every workflow.\n- Read [rfq-workflows.md](references/rfq-workflows.md) when handling intake,\n  attachments, customer/contact resolution, catalog work, commercial documents,\n  status, or amendments.\n- Read [draft-actions.md](references/draft-actions.md) before calling\n  `apply_rfq_draft_actions`.\n- Read [corebridge-push.md](references/corebridge-push.md) before asking for\n  final approval or calling `push_rfq_to_corebridge`.\n\n## Operator-facing result\n\nKeep updates concise and operational. State the selected location and RFQ,\ncompleted draft work, unresolved decisions or holds, current readiness, and the\nexact review URL returned by B2 Portal. Do not claim that `state: APPLIED` or\n`readyForOperatorReview` means CoreBridge was updated. Claim a CoreBridge push\nonly when `push_rfq_to_corebridge` returns `PUSHED`.\n"
}