Previous fallback was too soft: "discover intent, pick the best tool, confirm assumptions" was interpreted by Codex as "search the local workspace for kb:// material" — which never exists locally and burns context on fruitless exploration. New fallback makes the recovery path explicit: - STOP on Auth required / server unreachable - surface the exact fix command (`codex mcp login oci-deal-accelerator`) to the user - never reconstruct the KB from local files (server-side only) - never invent SKUs, pricing, or service quantities - never generate partial artifacts with inferred data Scoped: applies only when the entire MCP session is unreachable. Per-tool failures still follow the methodology's guidance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2.9 KiB
name, description
| name | description |
|---|---|
| oci-deal-accelerator | Compresses the OCI Solutions Architect's cycle from customer discovery to architecture proposal and delivery handover. Aligned with Oracle ECAL framework (Define, Design, Deliver). Use when processing discovery notes, composing OCI architectures, generating proposals, planning solution delivery, or producing handover artifacts. |
OCI Deal Accelerator
This skill bundles a pointer, not the full methodology. The canonical guide is served live from the MCP server so updates propagate without requiring users to reinstall the plugin.
Load the full methodology
Before using any tool, read this MCP resource:
skill://methodology
It contains the complete workflow (Define → Design → Deliver), welcome flow, tool selection rules, guardrails, SKU cookbooks, and the full ECAL-aligned playbook. The skill://guardrails resource is also available when context budget is tight.
Additional knowledge-base resources exposed by the same MCP server:
kb://services/index— OCI services catalogkb://patterns/index— reference patternskb://well-architected/index— WA review criteriakb://competitive/index— competitor comparisonskb://field-knowledge/pricing— pricing model, BYOL rules, free tiers
Tool surface (14)
| Category | Tools |
|---|---|
| Architecture & design | search_reference_architectures, generate_diagram, generate_deck, run_wa_review |
| Costing & proposal | generate_cost_estimate, generate_bom, generate_bom_appca, generate_business_case, generate_full_proposal |
| Competitive & compatibility | compare_competitive, check_feature_compatibility |
| Field knowledge | search_field_findings, report_field_finding, score_ecal_readiness |
Fallback behavior
If any MCP call returns Auth required (or the server is unreachable), STOP immediately. Surface a single clear message to the user:
The OCI Deal Accelerator MCP session is not authenticated. Run
codex mcp login oci-deal-acceleratorin a separate terminal, then restart Codex. I will retry once you confirm.
Do NOT:
- attempt to reconstruct
kb://*resources by searching the local workspace — the knowledge base lives server-side only and is never present in any cloned repo, plugin cache, or skill directory; - invent SKUs, pricing, service names, or quantities to fill the gap;
- generate partial artifacts (deck, BOM, diagram) using inferred data;
- retry the same tool call more than once before surfacing the fix to the user.
Exploration of the local filesystem on auth failure wastes context and produces wrong answers. Fail fast, surface the command, wait for the user.
If the resource skill://methodology IS readable but a specific downstream tool fails, continue the conversation using the methodology's guidance — the guardrail above applies only to blanket MCP connectivity/auth failures.