Mission control capture reconstruction
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.
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-capture-reconstructionAssembled 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 capture, reconstruction, and spatial-ingest workflows through Mission Control with explicit data quality, reconstruction, and evidence boundaries.
SKILL.md
2.1 KB, as published. Nobody here has run it
Mission Control Capture And Reconstruction
Purpose
Use Mission Control to plan capture and reconstruction workflows with explicit ingest, QA, reconstruction, and validation boundaries instead of treating drone footage and splat outputs like they teleport into production.
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 image/video capture, photogrammetry, neural reconstruction, or cloud processing.
- The user wants drone, mobile, or cloud reconstruction help.
- The pipeline needs quality gates before reconstruction results are trusted.
Workflow
- Confirm the repo has capture or reconstruction signals.
- Use the spatial feature catalog to pick the relevant capture, cloud-reconstruction, or dataset-quality bundle.
- Keep ingestion, QA, reconstruction, and downstream validation separate.
- Make evidence targets explicit before claiming the lane is usable.
Mission Control calls
Tools:
mission_control_get_spatial_feature_catalogmission_control_get_spatial_feature_bundlemission_control_get_workspace_tooling
Resources:
mission-control://projects/{project_id}/spatial/featuresmission-control://projects/{project_id}/spatial/features/{feature_id}mission-control://projects/{project_id}/workspace-tooling
Never do
- Do not collapse capture QA and reconstruction into one step.
- Do not imply cloud or mobile capture tooling exists if the workspace only contains downstream assets.
Failure and fallback
- If capture or reconstruction tooling is missing, state the blockers and the exact bundle that would apply once the runtime exists.
- If the repo is only consuming prebuilt assets, switch to the asset-pipeline or validation bundle instead.
Example invocation
Use Mission Control to review the capture and reconstruction workflow for this spatial project.