agentsclimarketplace

Mission control release prep

Skill MN755/Codex-Mission_Control/apps/mcp-server/src/mission_control_mcp_server/_bundled/skills/mission-control-release-prep

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-release-prep

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

Prepare a project for release through Mission Control. Use when validation, docs, versioning, changelog, limitations, evidence, deployment readiness, and security concerns need one coordinated release-prep review.

SKILL.md

2.1 KB, as published. Nobody here has run it

Mission Control Release Prep

Purpose

Coordinate release-prep review through Mission Control without skipping evidence or approvals.

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 if the project is ready to ship.
  • A release candidate needs a final checklist.
  • Docs, validation, and security all need coordinated review.

Workflow

  1. Review handoff, validation, risk, and status resources.
  2. Ask Mission Control for a release-prep pass if needed.
  3. Summarize validation, docs, versioning, changelog, limitations, evidence, deployment readiness, and security concerns.
  4. Surface any remaining approvals or blockers.

Mission Control calls

Tools:

  • mission_control_start_task
  • mission_control_get_handoff_summary
  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/handoff
  • mission-control://projects/{project_id}/validation-summary
  • mission-control://projects/{project_id}/risk-register
  • mission-control://projects/{project_id}/status

User-facing output

  • Give a release-readiness summary and list unresolved blockers.
  • Be specific about whether versioning, changelog, docs, and security are complete or still thin.

Approval behavior

If release-prep implies deployments, publishing, or policy shifts, keep those actions behind explicit approvals.

Never do

  • Do not announce release readiness without evidence.
  • Do not skip limitations or unresolved risks.
  • Do not publish anything from chat directly.

Failure and fallback

If release-prep is not a dedicated workflow yet, synthesize the checklist from the available resources and clearly mark missing evidence.

Example invocation

Use Mission Control to do a release-prep review for this project.

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.