agentsclimarketplace

Mission control spatial asset pipeline

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-spatial-asset-pipeline

An Open Source Platform For Building Projects With OpenAI's Codex, Claude CLI, And Other Coding LLMs Using Multi-Agent Swarms And Customizable Workflows. Runs On Windows, MacOS, And Linux.

Install
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-spatial-asset-pipeline

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route spatial and 3D asset-pipeline work through Mission Control with explicit ingest, conversion, validation, and evidence boundaries.

SKILL.md

2.1 KB, as published. Nobody here has run it

Mission Control Spatial Asset Pipeline

Purpose

Use Mission Control to plan or repair a spatial or 3D asset pipeline without pretending that splats, USD scenes, textures, captures, and validation artifacts are all the same thing.

The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.

Use when

  • The repo handles spatial assets, Gaussian splats, point clouds, meshes, or scene packages.
  • The user wants a starter lane for ingest, conversion, authoring, or validation.
  • The workspace needs a real pipeline shape instead of another folder full of random scripts.

Workflow

  1. Confirm the repo actually has spatial or 3D signals.
  2. Load the spatial feature catalog and workspace-tooling posture first.
  3. Select the feature bundle that matches the requested asset pipeline lane.
  4. Keep conversion, render validation, and evidence capture explicit.

Mission Control calls

Tools:

  • mission_control_get_spatial_feature_catalog
  • mission_control_get_spatial_feature_bundle
  • mission_control_get_workspace_tooling

Resources:

  • mission-control://projects/{project_id}/spatial/features
  • mission-control://projects/{project_id}/spatial/features/{feature_id}
  • mission-control://projects/{project_id}/workspace-tooling

Never do

  • Do not claim a Blender, USD, or capture pipeline is ready without checking runtime/tooling posture.
  • Do not flatten asset ingest, conversion, and validation into one vague “graphics” step.

Failure and fallback

  • If the spatial catalog is unavailable, fall back to mission-control://projects/{project_id}/workspace-tooling and explain the missing bridge surface plainly.
  • If required external tools are missing, surface blockers and evidence gaps instead of inventing green validation.

Example invocation

Use Mission Control to map the spatial asset pipeline in this repo and recommend the right starter lane.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.