agentsclimarketplace

Mission control generate runbook

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-generate-runbook

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-generate-runbook

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 an operational runbook through Mission Control. Use when the user wants RUNBOOK.md or a chat-native runbook covering startup, tests, build, debugging, local reset, logs, and deployment notes.

SKILL.md

1.8 KB, as published. Nobody here has run it

Mission Control Generate Runbook

Purpose

Generate or summarize a runbook grounded in Mission Control evidence and repo understanding.

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 wants a runbook.
  • A handoff should include stronger operational guidance.
  • Support or onboarding documentation is needed.

Workflow

  1. Read codebase map and handoff resources.
  2. Ask Mission Control to generate a runbook or prepare a runbook summary.
  3. Present the proposed sections and ask before writing any file.

Mission Control calls

Tools:

  • mission_control_get_handoff_summary
  • mission_control_start_task

Resources:

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

User-facing output

  • Cover start dev server, run tests, build, debug common failures, reset local state, logs, and deployment if configured.
  • Tell the user whether the result is chat-only or ready to write to RUNBOOK.md.

Approval behavior

Ask before writing or overwriting runbook files.

Never do

  • Do not invent commands that are not backed by the repo or handoff.
  • Do not write files silently.
  • Do not expose raw logs.

Failure and fallback

If runbook generation is not exposed yet, use handoff and codebase understanding to produce a chat-native runbook and mark file generation as expected or future.

Example invocation

Use Mission Control to generate a runbook 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.