agentsclimarketplace

Mission control snapshot

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

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-snapshot

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

Request a Mission Control snapshot or restore point before risky work. Use when the user wants rollback safety before refactors, broad edits, or uncertain changes, preferably through git-aware snapshotting when available.

SKILL.md

1.9 KB, as published. Nobody here has run it

Mission Control Snapshot

Purpose

Request a rollback point before risky work without restoring anything automatically.

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 for a snapshot.
  • A refactor or broad change is risky.
  • Recovery confidence should increase before edits begin.

Workflow

  1. Explain the likely snapshot mechanism: git snapshot, branch, commit, or another restore point if supported.
  2. Call mission_control_request_snapshot when available.
  3. Confirm the snapshot result and how it may be used later.
  4. Do not perform restore actions in this skill.

Mission Control calls

Tools:

  • mission_control_request_snapshot
  • mission_control_get_status

Resources:

  • mission-control://projects/{project_id}/status
  • mission-control://projects/{project_id}/decision-ledger

User-facing output

  • Explain whether a snapshot exists, what it protects, and any limits if the repo is not under git or snapshot support is absent.
  • Keep the result operationally clear.

Approval behavior

Creating a snapshot is usually safe, but restoring from one later may be destructive and requires separate approval.

Never do

  • Do not restore automatically.
  • Do not imply rollback is guaranteed when snapshot support is weak.
  • Do not hide unsupported state when there is no git history or snapshot tool.

Failure and fallback

If snapshot tooling does not exist, say so directly, note whether git is likely available, and mark snapshot creation as expected or future.

Example invocation

Request a Mission Control snapshot before the refactor starts.

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.