Mission control understand chat

Skill MN755/Codex-Mission_Control/.codex/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.

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.

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.

Gives 0 of the 12 instructions most architecture codebase skills give in 335 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

Ask the user which candidate to explorein 45 of 811, across 15 files
Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
Read any relevant architecture decision records firstin 31 of 811, across 8 files
Use exact glossary terms in every suggestionin 30 of 811, across 10 files
Accept dependencies instead of creating themin 24 of 811, across 5 files
Include before and after visualisations for each candidatein 24 of 811, across 5 files
Read the domain glossary before exploringin 24 of 811, across 6 files
Return results instead of producing side effectsin 23 of 811, across 4 files
Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
Introduce seams only where things varyin 22 of 811, across 3 files
Reduce the number of methodsin 21 of 811, across 2 files
Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

ask mission control to answer the question
offer follow-up drilldowns or a task
cite files or resources in the answer
list uncertainty in the answer
ask to import or scan the codebase if no map exists

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.