Default Templates is installed in Codex CLI without an identifiable artifact-generation prerequisite

Default Templates 0.1.1 is installed and enabled in Codex CLI, but its document, spreadsheet and presentation workflows stop because the required artifact capability and its workflow cannot be identified in the current runtime. The skills handle this situation intentionally; the usability gap is that installation does not give an actionable supported-surface or prerequisite explanation.

Environment: macOS 26.6.2, Codex CLI 0.153.4, tested 6 September 2026 in a fresh visible Codex agent. Plugin: openai-templates@openai-curated-remote, version 0.1.1, INSTALLED_BY_DEFAULT, ON_USE. Refreshing with codex plugin add openai-templates@openai-curated-remote --json returned the same version and unchanged content hashes.

Reproduction:

1. In a runtime with this plugin installed, follow the packaged Minimal Letterhead skill and request a new DOCX containing a short synthetic letter.
2. Repeat with Project Tracker for a new XLSX containing three synthetic tasks, then Team Alignment for a short synthetic PPTX.
3. Read each skill's metadata and attempt to identify the prerequisite creation capability and reference-import/rendering workflow.

All three stop at workflow step 2. The shared instruction says: “If no such capability can be identified and read, say it is unavailable and stop; do not recreate or install it.”

No DOCX creation workflow was advertised. The available Codex Document Control tools describe connected-session control, not general artifact creation. Discovery for excel, for powerpoint, and independently across all supported surfaces each returned executors: []. No file was created, rendered or verified. Empty discovery responses succeeded; they were not tool exceptions.

The 20 retained references passed the bundled packaging test and independent ZIP CRC, XML, relationship and preview-decoding checks. Scoped global configuration inspection found no explicit overrides for the relevant artifact apps/skills or this plugin. These checks do not prove application-level fidelity, account provisioning or backend health.

Expected improvement: identify the exact supported creation capability and resolvable workflow target, and state the supported product surface and missing prerequisite before users attempt generation. If this plugin is intentionally usable only outside Codex CLI, make that boundary explicit. No claim is made that disconnected Document Control sessions are a backend failure or that the plugin's app binding is incorrectly implemented.

Duplicate check: no exact match found in five openai/codex issue searches on the audit date. Related https://github.com/openai/codex/issues/32513 concerns removal/admin labeling; https://github.com/openai/codex/issues/37313 concerns Windows Chat availability. This report concerns the specific artifact prerequisite in the installed CLI template workflows.

Start by reproducing the Minimal Letterhead, Project Tracker, and Team Alignment workflows, then inspect their metadata and the Codex CLI plugin installation and capability-discovery entry points. Check how empty discovery results are surfaced before generation. Done means the CLI identifies the supported artifact surface and prerequisite, or clearly states that the workflows are unsupported outside another product surface.