Files

root 99352395af Forbid local artifact generation as MCP fallback

Observed behavior: when the MCP returns Auth required, Codex fell
through to "let me generate the .pptx/.xlsx myself" — probing for
python-pptx/openpyxl/xlsxwriter and then PowerPoint/Excel COM
automation. Any artifact produced that way has fabricated SKUs,
prices, and templates — worse than no artifact.

Previous guardrails forbade reconstructing the KB locally and
inventing SKUs, but did not explicitly forbid local artifact
generation. Add that rule: if the MCP is unreachable, no artifacts
are produced, full stop.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-20 14:09:18 -03:00

4.1 KiB

Raw Permalink Blame History

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 catalog
kb://patterns/index — reference patterns
kb://well-architected/index — WA review criteria
kb://competitive/index — competitor comparisons
kb://field-knowledge/pricing — pricing model, BYOL rules, free tiers

Workspace boundary

All methodology guidance and knowledge-base content lives in MCP resources served by the remote server (skill://*, kb://*). This plugin ships no local KB files.

Do NOT read from the working directory to satisfy methodology steps — pre-flight checks, changelog banners, KB lookups, YAML catalogs, pricing files, and similar do not exist locally. Whatever directory Codex was invoked in, it is not the skill repo. Any read_file, ls, or grep targeting kb/, docs/, templates/, prompts/, or similar paths to support the methodology wastes context and returns nothing useful.

The working directory matters only when the user explicitly asks about files in it (e.g. "resumí este README"). Everything else flows through MCP resources and tools.

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-accelerator in 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;
generate artifacts locally as a fallback. Do not spawn python-pptx, openpyxl, xlsxwriter, PowerPoint/Excel COM automation, LaTeX, pandoc, or any other local tooling to produce .pptx, .xlsx, .pdf, .docx, .png, or .svg files. All artifact generation flows through MCP tools (generate_deck, generate_bom, generate_diagram, etc.). If the MCP is unreachable, no artifacts — only surface the fix command 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.

4.1 KiB Raw Permalink Blame History