Package and install VidXP agent skills across supported hosts

[SaadBazaz]

VidXP should distribute reusable agent workflows across supported hosts without maintaining behaviorally divergent copies.

Codex is the first implemented host. VidXP now publishes a Codex plugin through this repository's Git marketplace, and Desktop can configure it explicitly. The underlying MCP workflows remain portable, but Codex, ChatGPT, Claude Code, hosted Claude skills, and other hosts have distinct packaging, registration, lifecycle, and validation requirements.

Expected direction

• Maintain one authoritative source for the shared ingest and evidence workflows.
• Assemble host-specific packages and metadata from that source without maintaining divergent workflow prose.
• Add and validate supported hosts individually rather than claiming universal compatibility.
• Keep installation opt-in and independent from Python package installation.
• Preserve user-modified local skills, or report a conflict before explicit replacement.
• Use host-native discovery, installation, update, status, and removal operations where they provide the required lifecycle safely.
• Keep direct CLI, HTTP, and MCP use independent of skill installation.
• Keep host-specific bootstrap instructions and metadata separate from portable VidXP workflow guidance.
• Keep skills focused on practical workflows rather than duplicating MCP tool descriptions or application behavior.

Implementation status

• Add canonical ingest and evidence workflow content.
• Publish the first supported adapter as a Codex plugin through the repository Git marketplace.
• Provide explicit Codex setup from VidXP Desktop.
• Include the current plugin bundle in Python release artifacts.
• Refuse to replace an unmanaged local marketplace during Desktop-managed export.
• Define the host-neutral canonical workflow source boundary.
• Separate shared workflows from host-specific bootstrap skills and metadata during package assembly.
• Add cross-host consistency checks so generated or assembled packages cannot drift from the canonical workflows.
• Complete and validate the supported ChatGPT distribution and remote registration path.
• Add and validate a Claude Code skill/plugin distribution path.
• Define and validate hosted Claude skill packaging where its runtime constraints fit VidXP's MCP workflows.
• Document lifecycle and conflict behavior for every supported host adapter.

Scope notes

One universal manifest, filesystem layout, or configuration format is not required. A better host-native mechanism may replace an originally proposed VidXP-owned command as long as the resulting behavior remains explicit, safe, version-aware, and documented.

Public marketplace submission, signing, review metadata, screenshots, and remote service registration are release concerns built on the shared workflows; they do not redefine the portable MCP application contract.

Packaging the authoritative workflow source for host adapters is tracked in #81.