Mission control understand chat

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-understand-chat

Ask questions against Mission Control's codebase understanding. Use for architecture questions, where-is-this-handled, why-does-this-exist, and codebase Q&A grounded in the project map.From its SKILL.md

Install

npx -y skills add MN755/Codex-Mission_Control --skill mission-control-understand-chat

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

3 things to look at

skips confirmationTells the agent to proceed without asking first, 1 time: "No approval is needed for read-only Q&A".
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.
fetches URLsInstructs the agent to fetch 3 URLs, including mission-control://projects/{project_id}/codebase-map and 2 more.

SKILL.md

1.8 KB, 335 tokens by cl100k_base, as published. Nobody here has run it

Mission Control Understand Chat

Purpose

Answer codebase questions from Mission Control's project understanding instead of making the chat agent free-associate from filenames.

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 user asks how part of the repo works.
The user asks where behavior is implemented.
A previous codebase import or graph exists.

Workflow

Read the codebase map and current status.
Ask Mission Control to answer the user question with cited files and confidence levels.
Separate confirmed facts from likely inferences.
Offer follow-up drilldowns or a task if the answer implies code changes.

Mission Control calls

Tools:

mission_control_get_status
mission_control_start_task

Resources:

mission-control://projects/{project_id}/codebase-map
mission-control://projects/{project_id}/diagnostics
mission-control://projects/{project_id}/status

User-facing output

Answer the question directly, cite files or resources, and list uncertainty.

Approval behavior

No approval is needed for read-only Q&A, but changes discovered from Q&A still go through Mission Control approvals.

Never do

Do not answer as if guesses are facts.
Do not ignore stale codebase maps.
Do not perform unrelated repo archaeology after Mission Control has a map.

Failure and fallback

If no map exists, ask to import or scan the codebase first.

Example invocation

Ask Mission Control where authentication is handled and what files matter.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.