agentsclimarketplace

Mission control onboarding tour

Skill MN755/Codex-Mission_Control/.codex/plugins/mission-control/skills/mission-control-onboarding-tour

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-onboarding-tour

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

Generate a guided onboarding tour for a codebase using Mission Control's project map, domains, commands, risks, and recommended reading order.

SKILL.md

1.7 KB, as published. Nobody here has run it

Mission Control Onboarding Tour

Purpose

Produce an ordered learning path through a repo instead of dumping a file tree and calling it help.

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

Use when

  • A user is new to a repo.
  • The team needs onboarding docs.
  • A handoff should include how to understand the system.

Workflow

  1. Ask Mission Control for codebase map, commands, architecture, and domain notes.
  2. Build a reading order by dependency and concept difficulty.
  3. Include setup, run/test commands, key files, common workflows, and risks.
  4. Mark unknown or unverified sections clearly.

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}/handoff
  • mission-control://projects/{project_id}/validation-summary

User-facing output

  • Return a guided tour with stages, files to read, concepts learned, and next tasks.

Approval behavior

Ask before writing onboarding docs into the repo.

Never do

  • Do not create onboarding docs from stale scans.
  • Do not hide setup gaps.
  • Do not overexplain obvious files while skipping architecture seams.

Failure and fallback

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

Example invocation

Use Mission Control to create a new-engineer onboarding tour for this repo.

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.